Date: Fri, 28 Apr 2000 11:17:50 +0200 From: Alexander Strauss <strauss@ti.com> To: freebsd-isdn@freebsd.org Subject: NetBSD RAW-IP Problem Message-ID: <3909573E.6475E22B@ti.com>
next in thread | raw e-mail | index | archive | help
Hi, I've setup a HDLC RAW-IP connection from a NetBSD/i386 1.4.2 System to a isdn4linux system. The same configuration with a 2nd Linux system worked well for years. Now I've replaced one Linux system with the above NetBSD system. The configuration is ok, the connection establishes without any errors, ISDND and Interface debugging say nothing special. If I ping the remote system, it seems to work. Also an rlogin works the first time, but at any point the rlogin sessions hangs and won't come back. Same with FTP: ftp> get pt_lab.tar.gz local: pt_lab.tar.gz remote: pt_lab.tar.gz 200 PORT command successful. 150 Binary data connection for pt_lab.tar.gz (137.167.205.26,1294) (2108886 bytes). ##### receive aborted waiting for remote to finish abort 426 Transfer aborted. Data connection closed. 226 Abort successful 5840 bytes received in 55.3 secs (0.1 Kbytes/sec) ftp> The first few packets are going through, then the transfer stops and doesn't come back - I'll have to terminate it. Same with tftp, http .... A ping I sent during the FTP transfer did not show up any packet loss. 64 bytes from 137.167.204.135: icmp_seq=18 ttl=252 time=33.1 ms 64 bytes from 137.167.204.135: icmp_seq=19 ttl=252 time=32.7 ms 64 bytes from 137.167.204.135: icmp_seq=20 ttl=252 time=32.0 ms 64 bytes from 137.167.204.135: icmp_seq=21 ttl=252 time=41.7 ms 64 bytes from 137.167.204.135: icmp_seq=22 ttl=252 time=258.1 ms 64 bytes from 137.167.204.135: icmp_seq=23 ttl=252 time=152.2 ms 64 bytes from 137.167.204.135: icmp_seq=24 ttl=252 time=32.2 ms 64 bytes from 137.167.204.135: icmp_seq=25 ttl=252 time=39.7 ms 64 bytes from 137.167.204.135: icmp_seq=26 ttl=252 time=39.2 ms 64 bytes from 137.167.204.135: icmp_seq=27 ttl=252 time=38.8 ms The interface statistics on both NetBSD and Linux do not show up any errors. I tried to find out something with tcpdump, but I didn't see anything special there - the remote system seems not to answer anymore, but only for the specified connection. Really strange thing. Any suggestions are welcome. Thank you, Alex -- Alexander Strauss - Email: strauss@ti.com - TI-MSG: ALST System Administrator - Mixed Signal & Logic Products Europe Texas Instruments Deutschland GmbH, 85350 Freising, Germany Phone: +49 8161 80-3606 - Fax: +49 8161 80-4477 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3909573E.6475E22B>