On 2022-10-06 15:11, Ondrej Zajicek wrote:
On Thu, Oct 06, 2022 at 11:37:18AM +0200, Bernd Naumann via Bird-users wrote:
I may should have had a look at the log before :/
``` Thu Oct 6 09:32:51 2022 daemon.err bird: KRT: Received route ::/0 with strange next-hop fe80::f6cc:55ff:fe42:1a94 ```
But why is this a strange a next-hop? Routes with via Link-Local next-hop just work fine with OSPF and BGP, whats the issue here?
Hi
That error message means the next hop was not found in interface address ranges. I do not see why link-local next hops should not work. What is your output from command 'show interfaces'?
Hey Ondreh, Thanks for having a look. ``` root@cpe:~# ip -6 addr show dev pppoe-wan 35: pppoe-wan: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc fq_codel state UNKNOWN group default qlen 3 inet6 2003:e4:bfff:XXXX:6c2f:796c:6521:7f54/64 scope global dynamic noprefixroute valid_lft 13960sec preferred_lft 1360sec inet6 fe80::6c2f:796c:6521:7f54/128 scope link valid_lft forever preferred_lft forever root@cpe:~# birdc show interfaces ... pppoe-wan up (index=35) PtP Multicast AdminUp LinkUp MTU=1492 93.206.5.X/32 (Preferred, opposite 62.155.247.65, scope univ) 2003:e4:bfff:XXXX:6c2f:796c:6521:7f54/64 (Preferred, scope univ) fe80::6c2f:796c:6521:7f54/128 (Preferred, scope link) ... ``` I assume you are only interested in the pppoe-wan interface right? I have to admit I have no clear knowledge about pppoe, but maybe this is related to my issue here. Because I do not have LLA with `/64` on pppoe-wan, but only `/128`. My LLA, and the GW LLA, is present as a host-route (`/128`). Thanks again. Bernd