Hello misc,

I'm currently advertising my prefix with "network $mynet", so as
redistributing connected networks with "network (inet6) connected".
However, loopback prefixes are not announced.

They are seen as local instead of connected:

$ route -n get 2001:db8:3cc:10:1000::1/128
   route to: 2001:db8:3cc:10:1000::1
destination: 2001:db8:3cc:10:1000::1
       mask: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
  interface: lo0
 if address: 2001:db8:3cc:10:1000::1
   priority: 1 (local)
      flags: <UP,HOST,DONE,LOCAL>
     use       mtu    expire
       0     32768         0

true connected/interface prefix:
$ route -n get 2001:db8:3cc:201::/64
   route to: 2001:db8:3cc:201::
destination: 2001:db8:3cc:201::
       mask: ffff:ffff:ffff:ffff::
  interface: em0
 if address: 2001:db8:3cc:201::2
   priority: 4 (connected)
      flags: <UP,DONE,CLONING,CONNECTED>
     use       mtu    expire
      16         0         0

$ bgpctl show net
flags: S = Static
flags destination
*S       0 2001:db8:3cc::/48    ::  (truly static w/ "network $mynet")
*S       0 2001:db8:3cc:200::/64 :: (actually connected instead of static)
*S       0 2001:db8:3cc:201::/64 :: (same)

Is there a good way to redistribute those local prefixes? like what
"network local" would do. I currently use "bgpctl network add", but I
have to remember to do (or net del) it every time I add a service
prefix on the loopback interface...

thanks.

Reply via email to