Re: issue with bird next hop

Is this behaviour expected? Can we replace the next hop to remove the need of a nat?


------- Original Message -------
On Friday, June 16th, 2023 at 12:24, Benoit Chesneau <benoitc@enki-multimedia.eu> wrote:


> After doing more testing onf Freebsd 13.2 , bird 2.13:
> 
> When 1.1.1.1/31 and 1.1.1.2/31 are set on the vlan interface, bird correctly announce them as the next hop.
> 
> However when 1.1.1.1/32 and 1.1.1.2/32 are set on the loopback interface of each instances then the local ip address of the vlan is used.
> 
> However when 1.1.1.1/31 and 1.1.1.2/31 are set on the loopback interface of each instances then nothing happen. On each nodes 1.1.1.1/31 and 1.1.1.2/31 resolve to the loopback interface instead of the remote node.
> 
> 
> Is the behaviour expected ?
> 
> 
> 
> Benoît
> 
> ------- Original Message -------
> On Thursday, June 15th, 2023 at 14:48, Benoit Chesneau benoitc@enki-multimedia.eu wrote:
> 
> 
> 
> > I see. This may indeed be related...
> > 
> > The current route is learnt using OSPF. This is weird to not have it using the source address configured in bird though:/
> > 
> > Benoît Chesneau, Enki Multimedia
> > —
> > t. +33608655490
> > 
> > Sent with Proton Mail secure email.
> > 
> > ------- Original Message -------
> > On Thursday, June 15th, 2023 at 14:42, Stephane Rochoy stephane.rochoy@stormshield.eu wrote:
> > 
> > > Benoit Chesneau benoitc@enki-multimedia.eu writes:
> > > 
> > > > Thanks for the hint. Unfortunately when I am setting it to /30
> > > > the machine stop to be advertised :/ Most probably because /30
> > > > will be routed locally?
> > > > 
> > > > Why would setting it to /30 fix the issue ? What does it solves
> > > > when we do it?
> > > 
> > > I just reacted to the fact that, IMHO, `route get` is correct when
> > > responding that 1.1.1.2 is not reachable via lo1.
> > > 
> > > Regards,
> > > --
> > > Stéphane Rochoy
> > > O: Stormshield