Re: openbgpd puts wrong nexthop in FIB

2016-01-21 Thread Stuart Henderson 
On 2016-01-20, Tony Sarendal  wrote:
> network inet connected is broken in 5.6, 5.8 and -current.
> Restarting bgpd is required when making interface changes.

Ah, so it was fixed in 5.7 and broken again? Now the previous mail
(http://permalink.gmane.org/gmane.os.openbsd.misc/227597) makes more
sense.

Re: openbgpd puts wrong nexthop in FIB

2016-01-21 Thread Denis Fondras 
> network inet connected is broken in 5.6, 5.8 and -current.
> Restarting bgpd is required when making interface changes.
> 

Thank you very much Tony.

Re: openbgpd puts wrong nexthop in FIB

2016-01-21 Thread Tony Sarendal 
2016-01-21 11:16 GMT+01:00 Stuart Henderson :

> On 2016-01-20, Tony Sarendal  wrote:
> > network inet connected is broken in 5.6, 5.8 and -current.
> > Restarting bgpd is required when making interface changes.
>
> Ah, so it was fixed in 5.7 and broken again? Now the previous mail
> (http://permalink.gmane.org/gmane.os.openbsd.misc/227597) makes more
> sense.
>
>
That sums is up well. Serious a bug in a piece of routing software.

/T

openbgpd puts wrong nexthop in FIB

2016-01-20 Thread Denis Fondras 
Hello,

I'm using -current as a BGP router and "sometimes" it won't put the right
nexthop in FIB. The only thing I played with is the interface that support IP
185.1.2.12 (ifconfig up/down/delete ip /add ip). Anybody can reproduce ?

# bgpctl sh rib 185.22.131.1   
flags: * = Valid, > = Selected, I = via IBGP, A = Announced, S = Stale
origin: i = IGP, e = EGP, ? = Incomplete

flags destination  gateway  lpref   med aspath origin
*>185.22.131.0/24  185.1.2.10 100 0 199881 i

# bgpctl sh fib 185.22.131.1 
flags: * = valid, B = BGP, C = Connected, S = Static, D = Dynamic
   N = BGP Nexthop reachable via this route R = redistributed
   r = reject route, b = blackhole route

flags prio destination  gateway
*B  48 185.22.131.0/24  185.1.2.12

Denis

Re: openbgpd puts wrong nexthop in FIB

2016-01-20 Thread Tony Sarendal 
network inet connected is broken in 5.6, 5.8 and -current.
Restarting bgpd is required when making interface changes.

/T

2016-01-20 20:36 GMT+01:00 Denis Fondras :

> Hello,
>
> I'm using -current as a BGP router and "sometimes" it won't put the right
> nexthop in FIB. The only thing I played with is the interface that support
> IP
> 185.1.2.12 (ifconfig up/down/delete ip /add ip). Anybody can reproduce ?
>
> # bgpctl sh rib 185.22.131.1
> flags: * = Valid, > = Selected, I = via IBGP, A = Announced, S = Stale
> origin: i = IGP, e = EGP, ? = Incomplete
>
> flags destination  gateway  lpref   med aspath origin
> *>185.22.131.0/24  185.1.2.10 100 0 199881 i
>
> # bgpctl sh fib 185.22.131.1
> flags: * = valid, B = BGP, C = Connected, S = Static, D = Dynamic
>N = BGP Nexthop reachable via this route R = redistributed
>r = reject route, b = blackhole route
>
> flags prio destination  gateway
> *B  48 185.22.131.0/24  185.1.2.12
>
> Denis