Date: Fri, 21 Sep 2007 16:59:16 +0200 From: "Petr Holub" <hopet@ics.muni.cz> To: "Jeremy Chadwick" <koitsu@FreeBSD.org> Cc: current@FreeBSD.org Subject: RE: TCP socket problem on Sept. -CURRENT snapshot Message-ID: <004901c7fc5f$fb269190$5317fb93@KLOBOUCEK> In-Reply-To: <20070921133316.GA63294@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > It occurred from several different addresses and results in being > > unable event to ping that IP until reboot. > > This is "normal" for the current time being, as the output in question > is being used to help track down a TCP-related bug in -CURRENT: Thank you! Actually, the more painful problem is that it made some IP addresses unreachable afterwards: I was unable to ping them, to make any TCP connection, etc. Though I was unable to ping (almost all) other IPs and I was also able to ping/connect those ``stuck'' IPs from another host siting on the same network. So it looks like the problem is actually some per-IP bug... Any reports of this behavior reported before before I start looking into this deeper? Just for reference, I'm using 200709 snapshot of 7.0-CURRENT for amd64, running on Core2 Duo with a custom kernes with WITNESS turned off. Thanks, Petr
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004901c7fc5f$fb269190$5317fb93>