Hi Ondrej, Not sure I undersand, these are the IPs of this router itself:
``` root@gw0:~ # ifconfig vlan600 vlan600: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 9000 description: backbone options=1c680703<RXCSUM,TXCSUM,TSO4,TSO6,LRO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6,MEXTPG,TXTLS4,TXTLS6> ether fa:9b:80:06:d7:f9 inet 198.19.4.33 netmask 0xffffffe0 broadcast 198.19.4.63 inet6 fe80::f89b:80ff:fe06:d7f9%vlan600 prefixlen 64 scopeid 0x5 inet6 2001:7f8::2:103::1 prefixlen 64 groups: vlan vlan: 600 vlanproto: 802.1q vlanpcp: 0 parent interface: mce0 media: Ethernet 25GBase-SR <full-duplex,txpause> status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> ``` I didn't find equivalent router id on the network. I also tried to uniquely change the ID but the same error appears. Is there anything I could do to debug this issue ? OSPF configuration (I edited IPV6 address): ``` define ospf_v4_routes = [ 198.19.0.0/16 ]; define ospf_v6_routes = [ 2001:7f8:2:100::/56 ]; filter ospf_export { if (net.type = NET_IP4 && net ~ [ 0.0.0.0/0 ]) then accept; if (net.type = NET_IP6 && net ~ [ ::0/0 ]) then accept; ospf_metric1 = 200; unset(ospf_metric2); reject; } filter ospf_import { if (net.type = NET_IP4 && net ~ ospf_v4_routes) then accept; if (net.type = NET_IP6 && net ~ ospf_v6_routes) then accept; reject; } protocol ospf v2 ospfv4 { debug all; ipv4 { import filter ospf_import; export filter ospf_export; }; area 0.0.0.0 { interface "lo1" { stub yes; }; interface "vlan600" { type ptp; cost 15; bfd on; }; }; } protocol ospf v3 ospfv6 { ipv6 { import filter ospf_import; export filter ospf_export; }; area 0 { interface "lo1" { stub yes; }; interface "vlan600" { type ptp; cost 15; bfd off; }; }; } ``` Benoit On Monday, April 15th, 2024 at 01:12, Benoit Chesneau <beno...@enki-multimedia.eu> wrote: > Hi, > > I have installed latest bird 2.15.1 with ntet link support on Freebsd and I > contunuously get the following messages: > > ``` > 2024-04-14 23:09:12.386 <RMT> ospfv6: Bad packet from > fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0)2024-04-14 > 23:09:12.386 <RMT> ospfv4: Bad packet from 198.19.4.33 via vlan600 - my own > router ID (0) > 2024-04-14 23:09:12.386 <RMT> ospfv6: Bad packet from > fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) > 2024-04-14 23:09:12.386 <RMT> ospfv4: Bad packet from 198.19.4.33 via vlan600 > - my own router ID (0) > 2024-04-14 23:09:18.155 <TRACE> ospfv4: HELLO packet received from nbr > 198.19.0.2 on vlan600 > 2024-04-14 23:09:22.382 <TRACE> ospfv4: HELLO packet sent via vlan600 > 2024-04-14 23:09:22.383 <RMT> ospfv6: Bad packet from > fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) > 2024-04-14 23:09:22.383 <RMT> ospfv4: Bad packet from 198.19.4.33 via vlan600 > - my own router ID (0) > 2024-04-14 23:09:22.383 <RMT> ospfv6: Bad packet from > fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) > 2024-04-14 23:09:22.383 <RMT> ospfv4: Bad packet from 198.19.4.33 via vlan600 > - my own router ID > ``` > > What could be the reason for such error? MTU looks fine, and I can retrieve > the route via osf. > > > Benoît