hi My system is Ubuntu 13.04, kernel version is 3.8.0-21-generic, bird version is 1.3.10. I want to achieve lo: 0 (eg: 192.168.1.1/32) address as the route-id of the device, while learning through ospf routing protocol ip address to manage the device through this ip address. Configured as follows: 1: I'm on a device configured lo:0 interface address: ifconfig lo:0 192.168.1.1/32 root @ sr1 :/ usr / local / bird # ifconfig lo:0 lo: 0 Link encap: Local Loopback inet addr: 192.168.1.1 Mask: 0.0.0.0 UP LOOPBACK RUNNING MTU: 65536 Metric: 1 2: The bird in the configuration is as follows: In direct proto configured lo: 0 Interface protocol direct { interface "eth1", 192.168.1.1/32; } In the kernel configuration is as follows: protocol kernel { # Learn; # Learn all alien routes from the kernel # Persist; # Don't remove routes on bird shutdown device routes; scan time 15; # Scan kernel routing table every 15 seconds import none; # Default is import all export all; # Default is export none # Kernel table 5; # Kernel table to synchronize with (default: main) } The problem is found in bird default route pointing to the interface, and the interface address lo not found in the routing table, and why? bird> show interfaces 1001-lo up (index = 1) 1004 - MultiAccess AdminUp LinkUp Loopback Ignored MTU = 65536 1003 - 192.168.1.1 / 0 (Primary, scope univ) 127.0.0.1 / 8 (Unselected, scope host) root @ sr1 :/ usr / local / bird # birdc-v 0001 BIRD 1.3.10 ready. bird> show route 1007-0.0.0.0 / 0 dev lo [direct1 16:55] * (240) thanks.
On Thu, Jun 19, 2014 at 05:24:45PM +0800, ?????? wrote:
hi
My system is Ubuntu 13.04, kernel version is 3.8.0-21-generic, bird version is 1.3.10.
I want to achieve lo: 0 (eg: 192.168.1.1/32) address as the route-id of the device, while learning through ospf routing protocol ip address to manage the device through this ip address.
Hello First, I would generally suggest to use newer BIRD. Second, there is no such thing as lo:0, that is an illusion for legacy tools like ifconfig. IP addresses (esp. in case of multiple IP addresses on one interface) should be set by 'ip' tool in Linux.
Configured as follows:
1: I'm on a device configured lo:0 interface address:
ifconfig lo:0 192.168.1.1/32
root @ sr1 :/ usr / local / bird # ifconfig lo:0 lo: 0 Link encap: Local Loopback inet addr: 192.168.1.1 Mask: 0.0.0.0 ^^^^^^^^^^^^^
Seems like the IP address was not set correctly, mask should be 255.255.255.255 . That is the source of your problems.
The problem is found in bird default route pointing to the interface, and the interface address lo not found in the routing table, and why?
Because the mask is 0.0.0.0, therefore prefix length is 0 and therefore directly attached network prefix is really 0.0.0.0/0, which is announced by Direct protocol.
bird> show interfaces 1001-lo up (index = 1) 1004 - MultiAccess AdminUp LinkUp Loopback Ignored MTU = 65536 1003 - 192.168.1.1 / 0 (Primary, scope univ) 127.0.0.1 / 8 (Unselected, scope host)
birdc in Ubuntu printed these message codes (100x)? They shouldn't be seen, that is probably some Ubuntu-specific bug. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (2)
-
Ondrej Zajicek -
曾小小