vyos@vyos# set interfaces ethernet eth2 mtu 16000 [edit] vyos@vyos# commit [ interfaces ethernet eth2 ] Interface MTU too high, maximum supported MTU is 9000!
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Oct 28 2020
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.
I have tested both SSTP and L2TP and it works as expected - thank you for this addition!
Oct 27 2020
Put in a PR to separate hello/hold timers for IPv4 and IPv6. Added IPv6 timers.
I will check it tomorrow and verify operation. Thank you!
Fixed
vyos@r4-roll# run show version
@klase Check these options in the next rolling release (after 20201027)
FRR doesn't delete isis configuration related "interfaces" with
delete protocols isis foo interface eth1
protocol "isisd" in the test was added here https://github.com/vyos/vyos-1x/pull/483/files#diff-060cdf269ea89160caa0deaebe8e323f0559aa6dfd19e5634a33634f3e38e461R72
@kroy What PR?
sounds good - would be good having some other options than just domain-name and email, but that's another story :). I'll follow the other task then!
It already fixed in the master branch.
https://github.com/hiroyuki-sato/vyos-documentation/commit/8587946d16aaae6f5495c1e591220f88005cd276
Resolved in T2985
@SrividyaA Thanks.
I have tested on this rolling release VyOS 1.3-rolling-202010231135 and created a lab setup similar to the reporter's setup.
@craterman it seems bug with your resolution.
Oct 26 2020
set service https certificates certbot
domain-name(s) should contain the desired server-name. A rewrite is in progress in:
https://phabricator.vyos.net/T2289
@jestabro hmmm I don't see that "certbot" in the completion - running on rolling 1.3... ? In fact, nodes "certificates" and "certbot" are not shown here:
set service https
Possible completions:
> api VyOS HTTP API configuration
> api-restrict Restrict api proxy to subset of virtual hosts
> certificates TLS certificates
+> virtual-host Identifier for virtual host
I've been running chronyd for some time in a number of environments without any noticeable issues. I do think the clock on the hosts seems to be a bit more stable, but not something that is overly remarkable one way or the other. I'd have no problem with the change.
It exists:
https://phabricator.vyos.net/T1585
I put a request on this up top. We'll get to it eventually, but I was hoping we could put it like this:
Can you add this commands
This still needs to be integrated into check-qemu-install before PR:
https://github.com/vyos/vyos-1x/compare/current...jestabro:vyos-configtest
PR for crux https://github.com/vyos/vyos-1x/pull/582
Update from VyOS 1.3-rolling-202010210152 to latest rolling vyos-1.3-rolling-202010260327-amd64.iso Failed.
Proposed CLI
set system options disable-spectre
Updated PR with section "parameters"
https://github.com/vyos/vyos-1x/pull/580
Once this task is solved, QoS documentation should include a subsection about NAT, explaining the procedure for both outbound and inbound traffic.
Limit can and should be lifted. I have also some Mellanox or Myricom cards with an MTU up to 16k
All of ours do as far as I know, which includes 10,40, and 100g. I'm pretty sure 2.5g and 5g will as well.
Don't some 10G/40G/100G gear support some megajumbo frame sizes now as well? Not sure about the 2.5/5G stuff though...
Oct 25 2020
Thanks - hopefully T2994 will catch all this stuff! Please be patient, I'm currently in the testing phase.