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
>
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.1
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
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
