February 2020 - Bird-users

Disregard OSPF path
by Kees Meijs 17 Feb '20

17 Feb '20

Hi birdies, I'd like to disregard an (in the literal sense) expensive OSPF path. The preferred path is longer in terms of OSPF. All nodes in the network are running BIRD2 and are in our management so we're in full control. What would be the most elegant approach to do this? Thanks! Best regards, Kees -- https://nefos.nl/contact Nefos IT bv Ambachtsweg 25 (industrienummer 4217) 5627 BZ Eindhoven Nederland KvK 66494931 /Aanwezig op maandag, dinsdag, woensdag en vrijdag/

4 7

OSPF best route selection with same cost
by Patrik Rehuš 17 Feb '20

17 Feb '20

Hello, I have a topology with multiple parallel path to same destination. It also use same next-hop router and each of them use default cost (not specified in config). In "show route" I can see there is only one active route so it probably means that BIRD don't use balancing between these routes. I cannot see in documentation exact algorithm used for route selection. Can you please explain me how is the best route selected when multiple paths with same cost are available? Is name of interface or IP address next criterion for selection? My goal is not balance traffic but I only want to understand how path selection works on equal links. Thank you for your explanation and help. With best regards, Patrik Rehus

2 1

Fwd: Rip is not working
by preetamjain 17 Feb '20

17 Feb '20

-------- Original Message -------- SUBJECT: Rip is not working DATE: 2020-02-17 15:30 FROM: preetamjain <preetamjain(a)bel.co.in> TO: bird-users(a)network.cz Hi , I am new and exploring bird routing daemon. I am using bird 1.6.4 and updated to bird 2.0 as well. I have successfully installed bird on ubuntu 18.04 and configured the bird.conf with rip configuration # Router ID in IPv4 format router id 62.168.0.1; # Load device information from kernel. protocol device {} # Generate direct routes for interfaces. Useful on BSD. protocol direct { ipv4; disabled; } protocol direct { ipv6; disabled; } # Feed routes to kernel FIB protocol kernel { ipv4 { export all; import all; }; learn; # Learn all routes from the kernel # scan time 10; # Scan kernel tables every 10 seconds } protocol kernel { ipv6 { import all; }; learn; } protocol rip { ipv4{ interface "ensp011"; interface "ens025:; } } This has made my PC a switch with 2 interfaces , where i have connected to cisco switch with two ports in RIP configuration. The network in updating in my PC where bird is installed but rip is not getting updated on cisco because bird is not sending response packets If I enbale OSPF on the interface is it is fine, i.e RIP protocol works only if OSPF is enabled on the same interface as RIP interface Please guide

1 0

Bird 2.x / OSPF v3 over ptp tunnels
by Bastien Durel 12 Feb '20

12 Feb '20

Hello. I have some sites linked via wiregard tunnels, and exchanging route information with OSPF, using bird (mostly) One of my routers is running bird 2.0.7, while others runs 1.6.6 (due to different distributions) All OSPF v2 is running well, with configs like : interface "wg-*" { type ptp; }; OSPFv3 runs fine between bird 1.6 routers, but it does not with the bird 2.0 one. Here is its config : protocol ospf v3 ospfv3 { ipv6 {}; area 0 { interface "eth*" { stub; }; interface "wg*" { type ptp; cost 20; stub no; }; }; } Alas, it does not send any Hello packets on links. The remote routers do send their hellos, but they are ignored. It looks like bird put these interfaces in stub mode : linux3:/etc# birdc show ospf in ospfv3 BIRD 2.0.7 ready. ospfv3: Interface eth0 (IID 0) Type: broadcast Area: 0.0.0.0 (0) State: Waiting (stub) Priority: 1 Cost: 10 ECMP weight: 1 Hello timer: 10 Wait timer: 40 Dead timer: 40 Retransmit timer: 5 Designated router (ID): 0.0.0.0 Designated router (IP): :: Backup designated router (ID): 0.0.0.0 Backup designated router (IP): :: Interface wg4b (IID 0) Type: ptp Area: 0.0.0.0 (0) State: PtP (stub) Priority: 1 Cost: 20 ECMP weight: 1 Hello timer: 10 Wait timer: 40 Dead timer: 40 Retransmit timer: 5 Interface wg4a (IID 0) Type: ptp Area: 0.0.0.0 (0) State: PtP (stub) Priority: 1 Cost: 20 ECMP weight: 1 Hello timer: 10 Wait timer: 40 Dead timer: 40 Retransmit timer: 5 With OSPF v2, it does not : linux3:/etc# birdc show ospf in ospfv2 BIRD 2.0.7 ready. ospfv2: Interface wg4b (peer 172.16.101.21) Type: ptp Area: 0.0.0.0 (0) State: PtP Priority: 1 Cost: 200 ECMP weight: 1 Hello timer: 10 Wait timer: 40 Dead timer: 40 Retransmit timer: 5 Interface wg4a (peer 172.16.101.17) Type: ptp Area: 0.0.0.0 (0) State: PtP Priority: 1 Cost: 200 ECMP weight: 1 Hello timer: 10 Wait timer: 40 Dead timer: 40 Retransmit timer: 5 These interfaces have some IPv6 addresses, as it's needed for bird communications : 7: wg4b: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 state UNKNOWN qlen 1000 inet6 fe80::3/128 scope link valid_lft forever preferred_lft forever 8: wg4a: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 state UNKNOWN qlen 1000 inet6 fe80::3/128 scope link valid_lft forever preferred_lft forever Do you have tips on how to make them work ? Thanks, -- Bastien

4 5

BGP session closed after receipt of flowspec route without destination prefix
by Alex D. 05 Feb '20

05 Feb '20

Hi, i configured the following flowspec route on a Juniper router: route v6test { match { source 2a02:xxxx:xxxx:xxxx::1/128; } then discard; } The route was accepted on my Juniper router and blocked all traffic from src ip 2a02:xxxx:xxxx:xxxx::1 as expected. After advertising the route, BIRD closed the BGP session. Is this an expected behaviour, means does is it necessary, that a dst prefix for a flowspec route must exist ? Log: 2020-01-24 09:52:26.750 <RMT> vs_dis_r1_6838: No dst prefix at first pos 2020-01-24 09:52:26.750 <RMT> vs_dis_r1_6838: Error: Malformed attribute list 2020-01-24 09:52:26.750 <TRACE> vs_dis_r1_6838: BGP session closed BIRD accepted the route after changing to: route v6test { match { destination ::/0; source 2a02:xxxx:xxxx:xxxx::1/128; } then discard; } Regards, Alex

3 4

Misleading "Symbol already defined" error
by Martin Weinelt 04 Feb '20

04 Feb '20

Hi, i was debugging this on and off for the last 36 hours and found the error message quite misleading. [root@ganymede:/etc/bird]# cat bird2.conf router id 172.23.42.3; protocol device { scan time 10; }; [root@ganymede:/etc/bird]# bird -c bird2.conf -p bird: bird2.conf:1:1 Symbol already defined [root@ganymede:/etc/bird]# bird --version BIRD version 2.0.7 But the error is not due to birds config file, it is due to a duplicate entry in /etc/iproute2/rt_tables definitions. [root@ganymede:/etc/bird]# ltrace bird -c bird2.conf -p [...] strcmp("ipt_igpt", "ipt_igpt") = 0 strlen("Symbol already defined") = 22 [...] Took me quite some time to find this and I would appreciate if the error message could be improved. Best regards, Martin

2 2

GCC 10 build failures at BIRD 2.0.7
by Robert Scheck 04 Feb '20

04 Feb '20

Hello folks, trying to build BIRD 2.0.7 using GCC 10 (which landed in Fedora these days) leads to a build failure like this: /usr/bin/ld: obj/conf/cf-lex.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/conf/conf.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/filter/filter.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/filter/data.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/filter/f-util.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/filter/tree.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/filter/trie.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/filter/inst-gen.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/a-path.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/a-set.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/cmds.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/iface.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/neighbor.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/proto.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/rt-attr.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/rt-dev.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/rt-fib.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/rt-show.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/nest/rt-table.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/bfd/bfd.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/bfd/packets.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/babel/babel.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/babel/packets.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/bgp/attrs.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/bgp/bgp.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/bgp/packets.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/mrt/mrt.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/dbdes.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/hello.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/iface.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/lsack.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/lsalib.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/lsreq.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/lsupd.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/neighbor.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/ospf.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/packet.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/rt.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/ospf/topology.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/perf/perf.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/pipe/pipe.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/radv/packets.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/radv/radv.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/rip/packets.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/rip/rip.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/rpki/rpki.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/rpki/packets.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/rpki/tcp_transport.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/rpki/ssh_transport.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/rpki/transport.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/proto/static/static.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/sysdep/linux/netlink.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/sysdep/unix/krt.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here /usr/bin/ld: obj/sysdep/unix/main.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: multiple definition of `rta_dest_names'; obj/conf/cf-parse.tab.o:/builddir/build/BUILD/bird-2.0.7/./nest/route.h:461: first defined here collect2: error: ld returned 1 exit status https://gcc.gnu.org/gcc-10/porting_to.html gives a pointer that this is related to a common mistake in C related to missing "extern" to global variables in a header file. Any chance for a patch (rather to suggest -fno-common)? Thank you. Regards, Robert

3 4

(no subject)
by Anders Hansen 01 Feb '20

01 Feb '20

Hi list I'm having issues with a Debian 10 based router running BIRD 2.0.7. On the router I have several interfaces where OSPFv3 is active. All good. Besides those interfaces, i also have a dummy interface named loopback0. Config example: area 0 { interface "ens*" { type ptp; cost 1; hello 5; }; interface "loopback0" { stub; cost 1; }; }; The ens interfaces work just fine. However, the /128 I have configured on the loopback0 interfaces is constantly not being picked up by BIRD. It's like BIRD completely ignores the existence of that interface. It simply won't announce that /128 out to its peers connected through the ens interfaces. If i change the /128 to a /127 instead, the prefix is advertised by bird. Any clues as to what gives this kinda unexpected (to me) behavior? Why wouldn't BIRD recognize a /128? I'm used to both Cisco and Juniper and have not seen this behavior before. All I'm trying to do is use my loopback for establishing an iBGP mesh - basic use case, i believe :) Thanks! Best Regards Anders Hansen

2 4