Re: OSPF bad packet
OK I see thanks for the feedback. This may be related to the upgrade to freebsd 14 and latest bird 1.15.1 which is compiled now by default with netlink support instead of rtsock. I I will try the rtsock version to compare. Benoit On Monday, April 15th, 2024 at 16:37, Ondrej Zajicek wrote: > On Mon, Apr 15, 2024 at 02:22:01PM +, Benoit Chesneau wrote: > > > Hi Ondrej, > > > > Not sure I undersand, these are the IPs of this router itself: > > > > `root@gw0:~ # ifconfig vlan600 vlan600: > > flags=1008843 metric 0 mtu > > 9000 description: backbone > > options=1c680703 > > ether fa:9b:80:06:d7:f9 inet 198.19.4.33 netmask 0xffe0 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 > > status: active nd6 > > options=21` > > > > 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 ? > > > Hi > > It seems like the OSPF receives its own packets back. There is a check > that should make them to be silently ignored: > > /* We want just packets from sk->iface. Unfortunately, on BSD we cannot filter > > out other packets at kernel level and we receive all packets on all sockets */ > if (sk->lifindex != sk->iface->index) > > return 1; > > But for some reason it does not work in your case, AFAIK it worked in > older BSDs. It should be harmless outside of spanning your logs. > > -- > Elen sila lumenn' omentielvo > > Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) > "To err is human -- to blame it on a computer is even more so."
Re: OSPF bad packet
On Mon, Apr 15, 2024 at 02:22:01PM +, Benoit Chesneau wrote: > Hi Ondrej, > > Not sure I undersand, these are the IPs of this router itself: > > ``` > root@gw0:~ # ifconfig vlan600 > vlan600: flags=1008843 > metric 0 mtu 9000 > description: backbone > > options=1c680703 > ether fa:9b:80:06:d7:f9 > inet 198.19.4.33 netmask 0xffe0 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 > status: active > nd6 options=21 > ``` > > > 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 ? Hi It seems like the OSPF receives its own packets back. There is a check that should make them to be silently ignored: /* We want just packets from sk->iface. Unfortunately, on BSD we cannot filter out other packets at kernel level and we receive all packets on all sockets */ if (sk->lifindex != sk->iface->index) return 1; But for some reason it does not work in your case, AFAIK it worked in older BSDs. It should be harmless outside of spanning your logs. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) "To err is human -- to blame it on a computer is even more so."
Re: OSPF bad packet
Hi Ondrej,
Not sure I undersand, these are the IPs of this router itself:
```
root@gw0:~ # ifconfig vlan600
vlan600: flags=1008843 metric
0 mtu 9000
description: backbone
options=1c680703
ether fa:9b:80:06:d7:f9
inet 198.19.4.33 netmask 0xffe0 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
status: active
nd6 options=21
```
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
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 ospfv6: Bad packet from
> fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0)2024-04-14
> 23:09:12.386 ospfv4: Bad packet from 198.19.4.33 via vlan600 - my own
> router ID (0)
> 2024-04-14 23:09:12.386 ospfv6: Bad packet from
> fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0)
> 2024-04-14 23:09:12.386 ospfv4: Bad packet from 198.19.4.33 via vlan600
> - my own router ID (0)
> 2024-04-14 23:09:18.155 ospfv4: HELLO packet received from nbr
> 198.19.0.2 on vlan600
> 2024-04-14 23:09:22.382 ospfv4: HELLO packet sent via vlan600
> 2024-04-14 23:09:22.383 ospfv6: Bad packet from
> fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0)
> 2024-04-14 23:09:22.383 ospfv4: Bad packet from 198.19.4.33 via vlan600
> - my own router ID (0)
> 2024-04-14 23:09:22.383 ospfv6: Bad packet from
> fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0)
> 2024-04-14 23:09:22.383 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
Re: OSPF bad packet
On 15. 04. 24 1:12, Benoit Chesneau wrote: Hi, Hi! Well, as you can see in the log file, something (198.19.4.33, fe80::f89b:80ff:fe06:d7f9) is sending packets with the same Router ID as the router. Ondrej 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 ospfv6: Bad packet from fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) 2024-04-14 23:09:12.386 ospfv4: Bad packet from 198.19.4.33 via vlan600 - my own router ID (0) 2024-04-14 23:09:12.386 ospfv6: Bad packet from fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) 2024-04-14 23:09:12.386 ospfv4: Bad packet from 198.19.4.33 via vlan600 - my own router ID (0) 2024-04-14 23:09:18.155 ospfv4: HELLO packet received from nbr 198.19.0.2 on vlan600 2024-04-14 23:09:22.382 ospfv4: HELLO packet sent via vlan600 2024-04-14 23:09:22.383 ospfv6: Bad packet from fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) 2024-04-14 23:09:22.383 ospfv4: Bad packet from 198.19.4.33 via vlan600 - my own router ID (0) 2024-04-14 23:09:22.383 ospfv6: Bad packet from fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) 2024-04-14 23:09:22.383 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 OpenPGP_signature.asc Description: OpenPGP digital signature
OSPF bad packet
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 ospfv6: Bad packet from fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) 2024-04-14 23:09:12.386 ospfv4: Bad packet from 198.19.4.33 via vlan600 - my own router ID (0) 2024-04-14 23:09:12.386 ospfv6: Bad packet from fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) 2024-04-14 23:09:12.386 ospfv4: Bad packet from 198.19.4.33 via vlan600 - my own router ID (0) 2024-04-14 23:09:18.155 ospfv4: HELLO packet received from nbr 198.19.0.2 on vlan600 2024-04-14 23:09:22.382 ospfv4: HELLO packet sent via vlan600 2024-04-14 23:09:22.383 ospfv6: Bad packet from fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0) 2024-04-14 23:09:22.383 ospfv4: Bad packet from 198.19.4.33 via vlan600 - my own router ID (0) 2024-04-14 23:09:22.383 ospfv6: Bad packet from fe80::f89b:80ff:fe06:d7f9 via vlan600 - my own router ID (0)2024-04-14 23:09:22.383 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
