Problem is the constraint statement in https://github.com/vyos/vyos-1x/blob/current/interface-definitions/include/nat-address.xml.i where ipv4-range returns 0 instead of 1.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Nov 7 2020
Nov 6 2020
See T3051 "OpenVPN: multiple client routes do not work in server mode" for follow up
I want to have native-vlan and allowed-vlan
Nov 5 2020
Perfect! Then please share your full OpenVPN config so the issue can be recreated and fixed properly.
Can you please check if this used to work in older VyOS versions, e.g. https://downloads.vyos.io/rolling/current/amd64/vyos-1.3-rolling-202010151549-amd64.iso or share your config and a network diagram.
Nov 4 2020
Please try again with the next rolling release.
As I'm raised by A vendor starting with C and now switched to another vendor starting with A they both reference the function as native-vlan and allowed-vlan - this makes it easier for users which operate cross-platform.
I really like the idea of this interface and alwaysed watned to implement it - but I lacked of time, so first thank you @jack9603301 for picking this up.
I wonder what happens if I have a eth0.10 bridge member interface? Also what should happen when the user jas eth0 and eth1.10 bridge members? should this feature still work or is it exclusively only for native non vlan interfaces?
Nov 3 2020
Nov 1 2020
Oct 31 2020
which exact VyOS version are you using? Delegating from one interface to many should be doable and can be configured on the latest rolling version.
Oct 30 2020
Closing in favor of T2994 - please try tomorrows rolling release. If there are new bugs (which might always happen on rewrites) please file a new Bug report and I try to fix them ASAP.