Unnumbered interfaces and OSPF
Hi! I am trying to use unnumbered interfaces and OSPF. On one router: ip addr add 10.90.255.3/32 dev eth0 ip addr add 10.90.255.3/32 dev eth1 On the other: ip addr add 10.90.255.4/32 dev eth0 ip addr add 10.90.255.4/32 dev eth1 On both of them: protocol ospf INTERNAL { import all; export none; area 0.0.0.0 { networks { 10.90.255.3/32; 10.90.255.4/32; }; interface "eth0" { bfd yes; type ptp; }; interface "eth1" { bfd yes; type ptp; }; }; ecmp yes; } But: bird> show ospf INTERNAL: RFC1583 compatibility: disabled Stub router: No RT scheduler tick: 1 Number of areas: 1 Number of LSAs in DB: 2 Area: 0.0.0.0 (0) [BACKBONE] Stub: No NSSA: No Transit: No Number of interfaces: 2 Number of neighbors: 0 Number of adjacent neighbors: 0 Area networks: 10.90.255.4/32 Advertise Active 10.90.255.3/32 Advertise Active bird> show ospf interface INTERNAL: Interface eth0 (10.90.255.3/32) Type: ptp Area: 0.0.0.0 (0) State: ptp (stub) Priority: 1 Cost: 10 ECMP weight: 1 Hello timer: 10 Wait timer: 40 Dead timer: 40 Retransmit timer: 5 Interface eth1 (10.90.255.3/32) Type: ptp Area: 0.0.0.0 (0) State: ptp (stub) Priority: 1 Cost: 10 ECMP weight: 1 Hello timer: 10 Wait timer: 40 Dead timer: 40 Retransmit timer: 5 tcpdump shows me that no hello packets are tentatively transmitted. Why is the state of each interface marked as "stub"? I would expect each OSPF router to be able to discover itself through the PtP link. -- printk("What? oldfid != cii->c_fid. Call 911.\n"); 2.4.3 linux/fs/coda/cnode.c
On Thu, Jun 26, 2014 at 11:27:26AM +0200, Vincent Bernat wrote:
Hi!
I am trying to use unnumbered interfaces and OSPF.
Currently, you have to use peer addresses for unnumbered interfaces in OSPF: On one router: ip addr add 10.90.255.3 peer 10.90.255.4 dev eth0 On the other: ip addr add 10.90.255.4 peer 10.90.255.3 dev eth0 Although generally you could use the same pair on both interfaces, i don't know if i tested such case and if there are no hidden problems related to this. Also note that addresses of unnumbered interfaces are not propagated by default, So you would also need some regular or loopback/stub interface added to OSPF: ip addr add 10.90.255.3/32 dev lo -- 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."
❦ 26 juin 2014 12:39 +0200, Ondrej Zajicek <santiago@crfreenet.org> :
I am trying to use unnumbered interfaces and OSPF.
Currently, you have to use peer addresses for unnumbered interfaces in OSPF:
On one router:
ip addr add 10.90.255.3 peer 10.90.255.4 dev eth0
On the other:
ip addr add 10.90.255.4 peer 10.90.255.3 dev eth0
Although generally you could use the same pair on both interfaces, i don't know if i tested such case and if there are no hidden problems related to this.
Also note that addresses of unnumbered interfaces are not propagated by default, So you would also need some regular or loopback/stub interface added to OSPF:
ip addr add 10.90.255.3/32 dev lo
Thanks, it works fine. This removes one advantage of using unnumbered interfaces with OSPF which is not having to predeclare peer and let OSPF discover them, but that's not a real showstopper. -- panic("Attempted to kill the idle task!"); 2.2.16 /usr/src/linux/kernel/exit.c
participants (2)
-
Ondrej Zajicek -
Vincent Bernat