quagga ignoring RTM_DELETE messages?



Hi list, sorry for the noise here.

I'm experiencing a weird issue with the latest Quagga from ports, on a
8.0-RC1. It was configured to redistribute kernel routes to BGP, which
it does. However, when a route is deleted, it's still announced to the
BGP peer. RTM_DELETE was picked up by "route monitor"... This exact
same setup used to work before upgrading to RELENG_8. Am I missing
something?

Thanks,
Vlad
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Is this expected IBGP peer behaviour?
    ... I have a basic question and am just now learning BGP. ... -A specific route, 1.1.1.0/16, exists on the IBGP peer between RTR B ... If the EBGP peer between A and B is broken, ...
    (comp.dcom.sys.cisco)
  • Re: BGP & EIGRP Routing Issue
    ... EIGRP. ... accidentally advertise these routes back to me. ... The route is in the BGP table but not in the routing table. ...
    (comp.dcom.sys.cisco)
  • Re: Is this expected IBGP peer behaviour?
    ... > I have a basic question and am just now learning BGP. ... > -A specific route, 1.1.1.0/16, exists on the IBGP peer between RTR B ... so C shouldn't advertise to A. ...
    (comp.dcom.sys.cisco)
  • Re: BGP & EIGRP Routing Issue
    ... EIGRP. ... accidentally advertise these routes back to me. ... The route is in the BGP table but not in the routing table. ...
    (comp.dcom.sys.cisco)
  • Re: BGP
    ... This should work, except the null route ... source router, ... bgp log-neighbor-changes ... network 172.172.172.168 mask 255.255.255.255 ...
    (comp.dcom.sys.cisco)