Date: Thu, 10 Feb 2000 18:13:15 -0800 From: Adam Wiggins <wiggins@treyarch.com> To: freebsd-questions@freebsd.org Subject: network stall Message-ID: <200002101813.SM00233@adam>
next in thread | raw e-mail | index | archive | help
Hi, I'm getting a very strange problem with my fresh install of 3.4. I did not get this with 2.2.7 and an almost identical configuration. When someone connects to the machine, via ssh, telnet, http, or whatever, everything works as expected - *unless* they get a chunk of data larger than about 1K. That is to say, you can log in, do "ls" and whatnot, but if you bring up something that spits a lot of data to the screen (such as a man page, cating a decently large file, or running pine) the connection appears to lock on the client side and no further output is visible. The input is continuing to run as normal. (I tested this by typing 'echo > test.tmp' in a locked session.) This does not happen when I connect from my internal LAN. I tried switching around the ethernet cards, but the result was the same. The outgoing connection is DSL if that makes any difference. I plan to dive in and do some deeper testing (tcpdump logs, connecting my Linux box to the DSL to see if it's the line that is the problem), but in the meantime I was wondering if there are any known bugs with 3.4 that would cause a connection freeze when packets exceeding the MTU get sent to an internet host. Or for that matter, if someone can suggest a good place to start in debugging this - I'm not knoweldgable enough to even really know where to begin. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002101813.SM00233>