There is a bug when we use lowercase "cisco"
set service pppoe-server authentication radius rate-limit vendor 'cisco'
It doesn't work as vendor is Cisco not cisco
vyos@vyos-lns# sudo cat /usr/share/accel-ppp/radius/dictionary.cisco | grep -i vendor VENDOR Cisco
PR for 1.4 https://github.com/vyos/vyos-build/pull/451
Fix build PR https://github.com/vyos/vyos-build/pull/450
PR for 1.5 which will be backported to 1.4 https://github.com/vyos/vyos-1x/pull/2416
I don't see this fix having been backported to Equuleus.
I'm building 1.4 rolling with the ixgbe out-of-tree driver if anyone cares.
Instead of "deny all" if no allow-clients are configured then localhost is always allowed. Can be handy when using containers and other if needed to sync to localhost for whatever reason (if the use of RTC isnt enough).
This has been implemented in 1.5 and 1.4.
@Apachez this request stems from this issue: https://forum.vyos.io/t/evpn-vxlan-esi-lag-duplicate-packets/12581
Both single-active and all-active should be supported when it comes to EVPN Multihoming.
I believe it's probably generating this error because modem sends an empty hostname.
Logs from just dhclient.
I didn't update it since the initial report and I don't really understand how/why it's working again.
PR for 1.5 current https://github.com/vyos/vyos-1x/pull/2413 which will then also be backported to 1.4
I would still recommend you to try to test to put a L2-switch between your 5G-router and the VyOS box and see if that resolves the situation.
This functionality has also been backported to 1.4 so it will be in the next LTS release.
Original template /usr/share/vyos/templates/chrony/chrony.conf.j2 (just the allow and listen sections):
What kind of cleanup are you talking about?
Turns out that the output of bindaddress will be broken unless put in a loop even if a single entry the only allowed entry.
This task is regarding to add localhost by default as allowed source to speak to chronyd (the current NTP daemon in VyOS).
Since the root cause for this task have been identified and fixed by the reporting user (and the task is set to invalid) I have created another task for the spinoff regarding cleaning up of the template used by chronyd: