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.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
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.
Oct 29 2020
set interfaces ethernet eth1 ipv6 address no-default-link-local is the right command, yes
Bug ;) will be fixed soon
Oct 28 2020
You actually can when setting ipv6 disable-link-local addressing on the particular interface.
vyos@vyos# set interfaces ethernet eth2 mtu 16000 [edit] vyos@vyos# commit [ interfaces ethernet eth2 ] Interface MTU too high, maximum supported MTU is 9000!
The root cause for this is the sha256 checksum file itself. It contains the hash and the filename. When running sha256 --check during the upgrade it expects the "real" filename when calculating and verifying the hash. The real filename differs when using the vyos-rolling-latest.iso symlink on the webserver as it will tell the running VyOS installation a different filename and the validation fails. This is now fixed by not depending on the filename when verifying the has. We simply calculate the hash of the downloaded file and compare it to the hash we saved inside the checksum file and totally ignore the filename itself.
Oct 26 2020
Limit can and should be lifted. I have also some Mellanox or Myricom cards with an MTU up to 16k
Oct 25 2020
Thanks - hopefully T2994 will catch all this stuff! Please be patient, I'm currently in the testing phase.
Oct 24 2020
Hi @jingyun, can you share how you added it to your local installation?