Re: Openbgpd incorrectly sets TCP_MD5 on the listen socket, regardless of configuration
- From: Borja Marcos <borjam@xxxxxxxxxx>
- Date: Wed, 23 Nov 2011 13:43:03 +0100
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.
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- References:
- Prev by Date: Re: Openbgpd incorrectly sets TCP_MD5 on the listen socket, regardless of configuration
- Next by Date: Re: arprequest triggered panic
- Previous by thread: Re: Openbgpd incorrectly sets TCP_MD5 on the listen socket, regardless of configuration
- Next by thread: Re: Openbgpd incorrectly sets TCP_MD5 on the listen socket, regardless of configuration
- Index(es):
Relevant Pages
|
