Feature: allow to specify peer address for point-to-point links #62

New issue

Closed

opened 2024-10-22 00:48:04 +02:00 by marekm72 · 1 comment

marekm72 commented

2024-10-22 00:48:04 +02:00

Please handle the optional peer when configuring IP addresses on interfaces:

$ ip addr help 2>&1 | grep IFADDR
Usage: ip address {add|change|replace} IFADDR dev IFNAME [ LIFETIME ]
       ip address del IFADDR dev IFNAME [mngtmpaddr]
IFADDR := PREFIX | ADDR peer PREFIX

I found this needed for OSPF to work over unnumbered point-to-point links between BIRD and FRR (on the BIRD side, as FRR can find the peer address automagically). Without this the OSPF neighbor appears but remains stuck in Init state on the FRR side, and never appears on the BIRD side.

router1# ip addr add x.x.x.1 peer x.x.x.2/32 dev eth1  # need to declare this in ifstate
router2# ip addr add x.x.x.2/32 dev eth1  # this works with FRR but not with BIRD

If configured manually as router1 above, ifstatecli show only shows the peer address/prefix.

Please handle the optional peer when configuring IP addresses on interfaces: ``` $ ip addr help 2>&1 | grep IFADDR Usage: ip address {add|change|replace} IFADDR dev IFNAME [ LIFETIME ] ip address del IFADDR dev IFNAME [mngtmpaddr] IFADDR := PREFIX | ADDR peer PREFIX ``` I found this needed for OSPF to work over unnumbered point-to-point links between BIRD and FRR (on the BIRD side, as FRR can find the peer address automagically). Without this the OSPF neighbor appears but remains stuck in Init state on the FRR side, and never appears on the BIRD side. ``` router1# ip addr add x.x.x.1 peer x.x.x.2/32 dev eth1 # need to declare this in ifstate router2# ip addr add x.x.x.2/32 dev eth1 # this works with FRR but not with BIRD ``` If configured manually as router1 above, `ifstatecli show` only shows the peer address/prefix.