NAS-Identifier typically uses hostname in all network OS and devices that I have used. Since “VyOS - Open source router and firewall platform”, which refers to network OS or virtual routers, I think setting NAS-Identifier = hostname by default would be more native. As alternative making it possible to change the NAS-Identifier value via cli, something like that: set system login radius nas-identifier host-name
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Feb 18 2025
Small note, to reproduce it, you have to have at least one route not related to vpp interface, like the default route via eth0, but vpp interface eth1
delete vpp commit
Feb 17 2025
@neilmckee it can wait as long as necessary, thanks!
Hsflowd v2.1.11-5 has a working mod_vpp, but the master branch has a fix to the iftype and ifdirection fields that are exported in the sflow counters for vpp interfaces. We expect to tag a v2.1.12-1 release soon that will include this fix. Let me know if there is a deadline and you need it right away.
The prefixes are announced by radvd.service daemon, and keepalived knows nothing about this service.
You have to use scripts with your own logic to skip/stop prefixes or radvd service.
If you need it as a feature request, create a new task/feature.
Bump keepalived version to 2.3.2 https://github.com/vyos/vyos-build/pull/911
https://github.com/vyos/vyos.vyos/pull/395 for OSPFv2 fixes - both unit and integration
Feb 16 2025
Feb 15 2025
Feb 14 2025
hsflowd expects the agent-address to be chosen from addresses it can see in it's own namespace.
At least example is incorrect but the bug with interface still exists if if will fail for some another reason
Probably should use common `interface.py` https://github.com/vyos/vyos-1x/blob/c2238596f7994e51974e9a517fb7ab7e948e955f/src/op_mode/interfaces.py#L468C1-L474C38
I would prefer if both disabled, all, rx-only and tx-only setting could be applied.
same issue on 1.5-rolling-202502130006
vyos@vyos# run show interfaces wireguard wg0
wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
inet 10.10.0.1/24 brd 10.10.0.255 scope global wg0
valid_lft forever preferred_lft forever
inet6 fe80::f4d1:45ff:feb8:435/64 scope link
valid_lft forever preferred_lft forever
Description: hk wg over wssI've also confirmed this problem exists on these versions:
I'm also facing the same issue: interfaces named pod-XXX vanish from the zone-based firewall after a system reboot. Here's my configuration:
vyos@vyos# sudo ip netns list netns-3ea94443-cb81-9ea7-05a1-d1e08b1cafe8 (id: 0)
In T4733#177910, @rgwan wrote:DHCP server with VRF support works correctly in v1.4
Feb 13 2025
Test with gdb