Date: Sat, 5 Jun 1999 20:02:51 -0700 (PDT) From: Archie Cobbs <archie@whistle.com> To: dennis@etinc.com (Dennis) Cc: hackers@FreeBSD.ORG Subject: Re: Socket Problem in 3.2? Message-ID: <199906060302.UAA14094@bubba.whistle.com> In-Reply-To: <199906051457.KAA10189@etinc.com> from Dennis at "Jun 5, 99 09:53:29 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Dennis writes: > 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. I know that there were some changes/fixes to "ping" recently relating to this... you might want to check the CVS logs for clues. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com 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?199906060302.UAA14094>