BFD implementation in 1.4.0

[Ondrej Zajicek]

On Thu, Aug 28, 2014 at 03:39:32PM +0400, Mikhail A. Grishin wrote:
> Hi,
...
> Then we tried to migrate this BFD sessions to our production route servers
> and faced with issues related to our network infrastructure. We have two
> separate IP networks at the same VLAN. Each customer has 2 peering IP: from
> the first IP subnet, and from the second. One IP assigned as primary,
> another as secondary at the same interface on customer side.
> 
> Problem:
> Routers of our customers able to communicate in terms of BFD only with Route
> Server located in the same IP subnet with primary IP address on their
> interface. With the Route Server in another IP subnet they can't communicate
> in terms of BFD because SRC IP address for BFD packets is wrong, equal to
> primary IP, not secondary.

Hi

This should work automatically - BFD should use same src, dst IP
addresses as associated BGP session (assuming that BFD session was
requested by BGP and not explicitly configured using 'neighbor' in BFD
protcol).

There are several possible ways how it could be broken, so i need
some info:

1) What is BIRD version and OS (Linux/BSD)?

2) What local IP addresses are reported for BGP sessions?
   ('Source address' in 'show protocols all')
   Correct one or bad one?

3) Is BGP source address explicitly configured in BGP protocol?
   ('local IP as NUM' instead of 'local as NUM')
   If not, could you try to set it and see if anything changes?

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at 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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20140902/3ad94b23/attachment.asc>