On Thu, Jan 29, 2009 at 02:57:09AM -0500, Daniel Ouellet wrote: > Hi, > > I am curious as to if this is really normal. I would say not, but may be > I miss something, or miss understood something. All active and > configured interfaces does show up in the fib table as they should and > same for the standard loopback on as well as below: > > Loopback interface lo0 at 127.0.0.1/8 is present in the fib table: > > # ifconfig lo0 > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33160 > groups: lo > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > > # bgpctl s f 127.0.0.0 > flags: * = valid, B = BGP, C = Connected, S = Static > N = BGP Nexthop reachable via this route > r = reject route, b = blackhole route > > flags destination gateway > *S r 127.0.0.0/8 127.0.0.1 > > > So, I would assume that configuring and additional loopback interface in > hostname.lo2 for example should show up the same way on reboot just like > any other interfaces on the router specially if it is showing up in the > ipconfig as well no? Why is it not present in the fib table? > > Example: > > # ifconfig lo2 inet 10.0.0.1 netmask 255.255.255.0 > # ifconfig lo2 up > # > # ifconfig lo2 > lo2: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33160 > groups: lo > inet 10.0.0.1 netmask 0xffffff00 > > Should show up the same way in the fib table no? > > # bgpctl s f 10.0.0.0 > flags: * = valid, B = BGP, C = Connected, S = Static > N = BGP Nexthop reachable via this route > r = reject route, b = blackhole route > > flags destination gateway > *SN 0.0.0.0/0 66.63.0.145 > > > Is there something I am missing? > > This is on 4.4 >
It does but not when the interface is added during runtime. Bgpd is missing the necessary hooks to get new interface addresses during runtime. This is an item on my todolist. -- :wq Claudio
