Date: Sat, 05 Jun 1999 09:53:29 -0400 From: Dennis <dennis@etinc.com> To: hackers@FreeBSD.ORG Subject: Socket Problem in 3.2? Message-ID: <199906051457.KAA10189@etinc.com>
next in thread | raw e-mail | index | archive | help
I'm willing to investigate this, but I need some pointers on where to start. There seems to be a socket-level problem with 3.x...I havent tested it in 3.1 yet but I do see it in 3.2. 2 Freebsd boxes connected back to back with a serial line..it happens to be a T3 but the results are the same with any PTP line..one is 2.2.8 and the other is 3.2. The 2.2.8 machine is pinging the 3.2 machine...the link is brought down. The 2.2.8 machine starts printing "sendto: network down" messages until the 3.2 machine is brought back up, and then pinging resumes normally. However, when pinging from the 3.2 machine, the 2.2.8 machine is brought down and the 3.2 machine just stops (no messages as if it doesnt detect the link down)....then when the 2.2.8 machine is brought back up the ping does not resume. A new ping session from the 3.2 box works normally indicating the the link is working properly. It seems that something was done, perhaps to eliminate the "Sendto" messages that keeps applications from coming back up if the link goes down and comes back up. This is pretty bad if major network services exhibit the same behaviour. Anyone have any ideas? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906051457.KAA10189>