Date: Thu, 13 Mar 2008 07:13:00 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: Mike Silbersack <silby@silby.com> Cc: freebsd-net@freebsd.org, "d.s. al coda" <coda.trigger@gmail.com> Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some routers Message-ID: <20080313071242.Q50685@maildrop.int.zabbadoz.net> In-Reply-To: <20080312235523.I60219@odysseus.silby.com> References: <f90b44e40803111756h517b373ala8afdff9395b7fac@mail.gmail.com> <20080312144207.P50685@maildrop.int.zabbadoz.net> <20080312235523.I60219@odysseus.silby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Mar 2008, Mike Silbersack wrote: > > On Wed, 12 Mar 2008, Bjoern A. Zeeb wrote: > >> On Tue, 11 Mar 2008, d.s. al coda wrote: >> >>> - FreeBSD 7 has <mss 1412, sackOK, eol> (there is of course an aligning >>> nop >>> after the eol, which tcpdump skips) >> >> Which is a bug (the nop after the EOL) that I recently fixed in HEAD. >> I am still curious to know if it's only ordering or the invalid padding >> or both that keeps clients from connecting. The problem is getting >> hands on such a problematic "client". > > Bjoern, can you get that fix MFC'd ASAP? I'll do that the next hours. > I've e-mailed a tcpdump developer asking how we can enhance it so that it > prints out <..., eol, nop> so that we can detect such errors more easily in > the future. > > I wish I had paid more attention to that part of the previous thread on this > topic! > > -Mike > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080313071242.Q50685>