Weird behavior on Bird 2.0.8 with Wireguard PtP links and OSPFv3
Hi there, I'm not sure if anyone else has seen this issue but I have been getting this issue repeatably today, where OSPFv3 just stops working due to "bad DBDES packet from nbr", I haven't changed anything and it has been working fine for months. What's the best way to troubleshoot this? The neighbor starting with 193. is a Debian 10 machine, 185 and 192.168.2.1 are EdgeOS running Bird 2.0.8. 2021-08-31 17:23:53 <RMT> ospfv3_v4: Bad DBDES packet from nbr 192.168.2.1 on wg0 - I-bit mismatch (7) 2021-08-31 17:23:53 <RMT> ospfv3_v6: Bad DBDES packet from nbr 193.xxx.xxx.223 on wg1 - I-bit mismatch (7) 2021-08-31 20:38:41 <RMT> ospfv3_v6: Bad DBDES packet from nbr 185.xxx.xxx.130 on wg0 - too late for DD exchange (7) OSPF3 configuration: ------------------------------------------------------------------------------------------------- protocol ospf v3 ospfv3_v4 { ipv4 { import filter internel_prefixes; export filter internel_prefixes; #export where (source = RTS_STATIC) || (source = RTS_DEVICE); }; area 0.0.0.0 { interface "lo*" { stub; }; interface "tun0" { type ptp; cost 10; stub no; }; interface "wg0" { type ptp; cost 20; stub no; }; interface "wg1" { type ptp; cost 30; stub no; }; }; } protocol ospf v3 ospfv3_v6 { ipv6 { import filter internel_prefixes; export filter internel_prefixes; #export where (source = RTS_STATIC) || (source = RTS_DEVICE); }; area 0.0.0.0 { interface "lo*" { stub; }; interface "tun0" { type ptp; cost 10; stub no; }; interface "wg0" { type ptp; cost 20; stub no; }; interface "wg1" { type ptp; cost 30; stub no; }; }; } --------------------------------------------------------------------------------------------------------
participants (1)
-
Skyler Mäntysaari