User Details
- User Since
- Sep 4 2017, 4:30 PM (471 w, 6 d)
Aug 12 2026
So this mean we can close the bug, because it's looks like that I need to redistrubute KERNEL ones with some filtering or you see some other option?
Data below, but looks like different approach of FRR, could be issue there, but now I thinking how we can workaround it, just to somehow inject route into OSPFv3
vyos@r0-sto.e-utp.net:~$ ip -6 r s | grep -v tun7
2001:67c:21ec::1 dev lo proto kernel metric 256 pref medium
2001:67c:21ec:9999::8 dev lo proto kernel metric 256 pref medium
2a0f:5707:ba00::1 dev lo proto kernel metric 256 pref medium
2a0f:5707:ba0e:100:14ab:ba50:9291:6963 dev eth0 proto kernel metric 256 pref medium
2a0f:5707:ba0e:100::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev lo proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fe80::4f7:44ff:fe8f:a860 dev eth0 proto ra metric 1024 expires 1790sec hoplimit 255 pref medium
vyos@r0-sto.e-utp.net:~$
Aug 11 2026
There is no BGP on that box.
This box is IPv6 client, RA are send from upstream router, in that case is AWS.
vyos@r0-sto.e-utp.net:~$ uname -r
6.6.144-vyos
Doesn't see difference:
How this looks like on 1.4.4, same config, for clearnes: 51.21.99.1 is this Router ID.
I'll compare on the evening how this looks llike with 1.4.x
Hello, this is FRRouting (version 10.5.2).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
Aug 10 2026
Some input, I can't test it with IPv4.
Aug 9 2026
Ad.1/2 It's there
Aug 8 2026
Mar 29 2026
I'm unable to reproduce it, I've no env to make it, chaging status as "Invalid"
Feb 8 2026
Jan 28 2026
I need to double check, but could this part:
Any specific part?
I want to avoid to share full config.
Dec 25 2025
Nov 10 2025
Oct 16 2025
Thanks for analysis and confirmation.
Oct 10 2025
show configuration commands | grep 'set firewall ipv6 name'
Oct 9 2025
ip -6 maddr show dev tun2
Kernel IPv6 routing table Destination Next Hop Flag Met Ref Use If 2001:67c:21ec:4010::/64 :: U 256 1 0 tun2 2001:67c:21ec:41d0::/64 :: U 256 2 0 tun3 2001:67c:21ec:9999::9/128 :: !n 256 3 0 lo 2a0f:5707:ba01:1000::/64 :: U 256 2 0 eth1 fe80::/64 :: !n 256 1 0 lo fe80::/64 :: U 256 1 0 eth0 fe80::/64 :: U 256 2 0 eth1 fe80::/64 :: U 256 1 0 tun3 fe80::/64 :: U 256 1 0 tun2 ::/0 :: !n -1 1 0 lo ::1/128 :: Un 0 4 0 lo 2001:67c:21ec:4010::/128 :: Un 0 3 0 tun2 2001:67c:21ec:4010::1/128 :: Un 0 4 0 tun2 2001:67c:21ec:41d0::/128 :: Un 0 3 0 tun3 2001:67c:21ec:41d0::2/128 :: Un 0 5 0 tun3 2001:67c:21ec:9999::9/128 :: Un 0 4 0 lo 2a0f:5707:ba01:1000::/128 :: Un 0 3 0 eth1 2a0f:5707:ba01:1000::1/128 :: Un 0 4 0 eth1 fe80::/128 :: Un 0 3 0 lo fe80::/128 :: Un 0 3 0 eth0 fe80::/128 :: Un 0 3 0 tun3 fe80::/128 :: Un 0 3 0 tun2 fe80::/128 :: Un 0 3 0 eth1 fe80::200:ff:fe00:0/128 :: Un 0 6 0 lo fe80::20c:29ff:fe25:cfc1/128 :: Un 0 3 0 eth0 fe80::20c:29ff:fe25:cfcb/128 :: Un 0 3 0 eth1 fe80::f405:63ff:fef9:9799/128 :: Un 0 2 0 tun2 fe80::f88f:fcff:feb2:2d3d/128 :: Un 0 3 0 tun3 ff00::/8 :: U 256 1 0 eth0 ff00::/8 :: U 256 3 0 eth1 ::/0 :: !n -1 1 0 lo
Sep 1 2025
ip -6 r s ff00::/8
ff00::/8 nhid 19 proto static metric 20 pref medium
nexthop dev tun3 weight 1 nexthop dev tun2 weight 1
Finally VyOS-style static route help:
Both tunnel have multicast enabled:
Manually adding route:
ip -6 r a ff00::/8 dev tun2
Oct 15 2024
I've checked on 1.4.0 and BGP session is stable
Jan 24 2022
Sep 9 2017
I think that best way to implement it, will be use a "extends" in snmpd for BGP4-V2-MIB-JUNIPER and use a vtysh as backed.
Sep 4 2017
There is another problem. BGP4-MIB doen't cover IPv6 peers, the clue is implement a new MIB like https://iphostmonitor.com/mib/BGP4-V2-MIB-JUNIPER.html like Juniper did
I have access to to these routers, is VyOS like below will be ok?
vyos@vyos:~$ show version
Version: VyOS 1.1.7
Description: VyOS 1.1.7 (helium)
I'm also really intereseted to make it working, is there any chance to help?