- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 4 2024
May 3 2024
How was this configuration achieved? Or is it manually crafted?
I think the problem is similar to https://vyos.dev/T5611
May 2 2024
Upstream bug https://github.com/FRRouting/frr/issues/15912
May 1 2024
Apr 30 2024
Works as expected in VyOS 1.5-rolling-202404290019 and VyOS 1.4-stable-202404300309 and VyOS 1.3-stable-202404300508
vyos@r1-right:~$ cat /etc/resolv.conf ### Autogenerated by VyOS ### ### Do not edit, your changes will get overwritten ###
Apr 29 2024
Fixed in the commit https://github.com/vyos/vyos-1x/commit/b75e0ba0a297fd64307960f98f30c27a689deab7
Apr 28 2024
PR for 1.5:
https://github.com/vyos/vyos-1x/pull/3372
Combined PRs for backport to 1.4 of T5839, T5660, T6276 pending.
Apr 26 2024
Apr 25 2024
The group 224.0.0.0/24 is reserved
r4(config)# interface eth2 r4(config-if)# ip igmp join 224.0.0.0 224.0.0.10 % Configuration failed.
Apr 24 2024
Reopen to investigate.
I tested in the latest rolling version and the traceback error is not received anymore and the tunnel ip column shows n/a but with multiple entries.
It still shows the disconnected client and I assume it should not show disconnected clients