User Details
- User Since
- Oct 2 2019, 6:00 PM (370 w, 6 h)
- Roles
- Administrator
Tue, Nov 3
The PR has been merged and fix will be available in the next rolling release.
Appreciate if someone can do the final confirmation.
Mon, Nov 2
Fri, Oct 30
Side note: the vyos/vyos-build:current container has an APT source packages.vyos.net/repositories/current that answers 404 now
The actual container is vyos/vyos-build:rolling
I'd start with patches this time; this way, we can backport it to the LTS without additional changes or potential new risks.
Then, when we are ready, bump the KEA version for the rolling.
Thu, Oct 29
PR superseded by
It is expected for VPP as it does not add a gateway IP address on its own PPP interfaces
But forwarding traffic should work fine
Wed, Oct 28
Tue, Oct 27
Mon, Oct 26
We can always use the patched VPP version https://github.com/vyos/vyos-vpp-patches/tree/rolling/patches/vpp
Needs to check if we can apply it to our version (stable/2510).
Fri, Oct 23
RADIUS rate-limit silently does nothing when the vendor name has the wrong case (vendor mikrotik)
I think it is expected
What RFC says how to handle a wrong attribute if the vendor name is wrong?
Thu, Oct 22
What are the requirements?
Will it be enough to use a single VRF, or is the VRF received via a RADIUS attribute?
Wed, Oct 21
Tue, Oct 20
I think we are OK to use even pdns-recursor-5.4.6
Be sure that it fixes the issue, and feel free to add a PR with package build, you can find an example of build HAProxy