Honestly it's not anything I've ever used. But from asking around some people still use it (not specifically in VyOS, just in general)
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Oct 5 2020
@christophedc0 please check out any rolling release which is newer then vyos-1.3-rolling-202010050117-amd64.iso as I have found two bugs in the implementation (one for source nat logging) and the other for the warning you have posted.
There are 2 issues:
Works with Ethernet ports fine
How to name this function?
Oct 4 2020
Pull request: https://github.com/vyos/vyos-1x/pull/562
This was infact only a warning - but for whatever reason nftables is not logging to kernel log :/
@marekm I've reproduced your issue and fixed it for 1.2.7 - Thanks for reporting.
This also relates to https://phabricator.vyos.net/T2829#76815
Oct 3 2020
Fix in PR: https://github.com/vyos/vyos-1x/pull/561
Oct 2 2020
Note: New xl2tpd package does not work with the followings params in options.xl2tpd
crtscts lock
Behavior in FRR version 7.4
Reproduced the issue in the rolling release VyOS 1.3-rolling-202009300117 and the route-map configuration wiped out after the reboot with the error as mentioned in the problem description and happens only when the bridge address is added for src and not for other interface types.
We found one case when it does work (for both Crux and 1.3), which can lead to further investigation: when the policy is applied to a PPPoE client interface and the class traffic is matched with the command naming the subinterface (the first of the 3 options above).
At this stage, I can't realize the automatic configuration of NDP proxy. On the other hand, although I don't know what additional application scenarios will be in addition to nat66, I hope to give full play to the full potential of NDP proxy, so I don't want to bind it to nat66 artificially.
In T2829#73944, @c-po wrote:There can not be a config migrator, thus the setting will be changed to "prefer" (default) which will not break any client implementations
Oct 1 2020
Still wondering why ndp-proxy can not be part of the nat66 tree.
When a NAT66 translation is added we know the prefix (src and dst), the in/out-bound interface - so another CLI option (ndp-proxy) could probably be added to not open up an additional service node.
This PR should correct it. Fortunately it appears that that this node was the only place this existed.