Date: Wed, 23 Nov 2011 13:43:03 +0100 From: Borja Marcos <borjam@sarenet.es> To: Nikolay Denev <ndenev@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: Openbgpd incorrectly sets TCP_MD5 on the listen socket, regardless of configuration Message-ID: <F35D19C6-D560-4ED0-A2E3-140E64D0841C@sarenet.es> In-Reply-To: <25CAC0FC-ED0F-42D5-85DC-B7270EFD9814@gmail.com> References: <EE636279-E758-44EA-B5B7-23D66D799E20@sarenet.es> <25CAC0FC-ED0F-42D5-85DC-B7270EFD9814@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 23, 2011, at 9:30 AM, Nikolay Denev wrote: > I'm seeing exactly the same problem with Quagga. > Quagga's bgpd also seem to always set the TCP_MD5 socket option, and = newer freebsd 8.2 machines > don't seem to be able to establish bgp sessions, probably due to the = recent TCP_MD5 fixes that enabled > the TCP_MD5 checksum verification of incoming packets. Hmm. A confusion? ;) The traces I've just sent show Quagga and Bird working well, OpenBGPD = failing. Borja.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F35D19C6-D560-4ED0-A2E3-140E64D0841C>