Date: Sat, 26 Jan 2008 01:14:13 +0100 From: Andre Oppermann <andre@freebsd.org> To: Maxim Konovalov <maxim@macomnet.ru> Cc: freebsd-net@freebsd.org Subject: Re: cvs commit: src/sys/netinet tcp_syncache.c Message-ID: <479A7B55.6050302@freebsd.org> In-Reply-To: <20080125073623.F15031@mp2.macomnet.net> References: <200711200656.lAK6u4bc021279@repoman.freebsd.org> <4797B77E.2090605@freebsd.org> <20080124005006.D93697@odysseus.silby.com> <47986F27.10401@freebsd.org> <20080124145713.K15031@mp2.macomnet.net> <47988A2A.5010506@freebsd.org> <20080124164704.X15031@mp2.macomnet.net> <47989E3C.4030700@freebsd.org> <20080124171957.N15031@mp2.macomnet.net> <20080125073623.F15031@mp2.macomnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Konovalov wrote: > On Thu, 24 Jan 2008, 17:20+0300, Maxim Konovalov wrote: > >>>> The latter. Turning rfc1323 off solved the problem. >>>> >>>> It takes some time to obtain the dump -- I need to downgrade the >>>> system. >>> That is not necessary. A tcpdump from current is fine. >>> >> OK, later this evening (UTC+3). >> > http://maxim.int.ru/stuff/adsl.dmp.gz > > 192.168.1.1 -- adsl box > 192.168.1.250 -- FreeBSD The trace looks perfectly fine with regard to timestamps. They are sent and properly reflected by the adsl box. Everything else looks fine too. No anomalies seen. The syncache check for timestamps wouldn't be triggered anyway because it only applies to incoming connections. Not segments in general. Connections initiated by the FreeBSD box never go through syncache. To track down the problem you saw back then, which is very probably unrelated to the syncache issue, I would need a trace of a failed connection. For that you need to downgrade. If you can find time for the downgrade I'm happy to find the root cause. -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?479A7B55.6050302>