set interfaces ethernet eth1 ipv6 address no-default-link-local is the right command, yes
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Oct 30 2020
Oct 29 2020
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?
Hi @drac, good catch and nice reverse engineering of our code.
Driver will be included in next rolling ISO
Oct 22 2020
Besides the command proposal there is a common issue with how we build op-mode commands. The best example is the ping op-mode command where and artifical node.tag folder is created which links (ln -s) back to itself.
The current NTP config always binds to localhost and localhost is not a part of the mgmt VRF thus this error message.
Oct 19 2020
Unfortunately I can not reproduce this issue on my test system and also our smoketests (https://github.com/vyos/vyos-1x/blob/current/smoketest/scripts/cli/test_interfaces_openvpn.py) do not trigger the bug when run locally on the VyOS device by calling:
Do other vendors suppert highjacking/altering of DHCP options? I feel this kills the whole concept of DHCP.
There have been some deletion errors yesterday - are you running the latest rolling release? They should have been fixed in there. If noe please provide me some CLI samples to reproduce the issue.
Oct 18 2020
It seems that calling openvpn --mktun is what we need. Please try the next rolling ISO which will contain a fix for this.