Hi, Check the attached patches. The first adds option to sockets to use nonlocal bind (IP_FREEBIND in Linux) and the second adds bgp option to use such sockets ("nonlocal bind yes|no"). Some additional thoughts: - probably the option could be implemented for any protocol, not only for bgp - I think it is better to check if this option is changed during reconfiguration, so to reload protocol in a hard way - did not check how it works with bfd enabled, maybe it will need to inherit this socket option from bgp somehow - it can be also considered to enable nonlocal bind for all bgp unconditionally, at least I see no obvious problems yet What do you think? On Sat, Jan 11, 2020 at 6:14 PM Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Thu, Jan 09, 2020 at 08:15:25PM +0100, Alexander Zubkov wrote:
Hi,
Ondrej, what do you think of adding some option to bind socket in Linux with IP_FREEBIND or IP_TRANSPARENT setsockopt?
Hi
Using IP_FREEBIND looks like an interesting way to fix this.
-- Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."