I have successfully added a *ton* of address families in my build. I will PR it, but we also have found an error. The error that we have found is an FRR error at this link here.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Mar 14 2021
Sadly, this isn't a trivial update due to dependencies. However, Microsoft's own documentation says the version that is unsupported for real is 2.2.10, and 2.20 is still supported, even if they recommend the very latest one.
This is a config syntax design mistake on our side indeed. The "preference" option should have always been under "cache".
Mar 13 2021
thank you very much ! Very responsive 😄
Tomorrows 1.3 beta image and 1.4 rolling will have the fix included.
Yeah, that would work. We still try to keep the number of custom validators to a minimum.
The XML file is changed now for 1.4 (and soon 1.3).
When I create dedicated validator and modify manually file /opt/vyatta/share/vyatta-cfg/templates/interfaces/tunnel/node.tag/parameters/ipv6/encaplimit/node.def it work :)
commit now produces an error:
Now, the last migration of this task should have completed the preliminary implementation (the operation mode can view NAT rules), but it does not support port rule display
Latest PR of T2518: https://github.com/vyos/vyos-1x/pull/771 The display script of rule file is completed
Yes, some time ago, it could produce kernel issues https://www.mail-archive.com/netdev@vger.kernel.org/msg218964.html
And I think it will be good to add the possibility to control unit-cache to have the opportunity to influence this.
Mar 12 2021
Any reason to not default enable it?
Assuming T3356 can be backported to equuleus, this fix will not be needed.
After a while, I may consider how to provide the operation mode command for nat66
Specifically, to reproduce the issue - you need to make the changes in the configuration file - and use load /config/xxx
I use set. Then commit and "save" the configuration and reboot the server.
Did you use set commands - or did you use load ...? Its regularly/easily produced here.
I can't reproduce it.
vyos@1.1.8:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
bond0 - u/u
bond0.11 10.0.11.1/24 u/u
100.64.11.1/29
bond0.12 10.0.12.1/24 u/u
100.64.12.1/29
bond0.13 10.0.13.1/24 u/u
100.64.13.1/29
bond0.14 10.0.14.1/24 u/u
100.64.14.1/29
bond0.15 10.0.15.1/24 u/u
100.64.15.1/29
bond0.16 10.0.16.1/24 u/u
100.64.16.1/29
bond0.17 10.0.17.1/24 u/u
100.64.17.1/29
bond0.18 10.0.18.1/24 u/u
100.64.18.1/29
bond0.19 10.0.19.1/24 u/u
100.64.19.1/29
bond0.20 10.0.20.1/24 u/u
100.64.20.1/29
bond0.21 10.0.21.1/24 u/u
100.64.21.1/29
bond0.22 10.0.22.1/24 u/u
100.64.22.1/29
bond0.23 10.0.23.1/24 u/u
100.64.23.1/29
bond0.24 10.0.24.1/24 u/u
100.64.24.1/29
bond0.25 10.0.25.1/24 u/u
100.64.25.1/29
bond0.26 10.0.26.1/24 u/u
100.64.26.1/29
bond0.27 10.0.27.1/24 u/u
100.64.27.1/29
bond0.28 10.0.28.1/24 u/u
100.64.28.1/29
bond0.29 10.0.29.1/24 u/u
100.64.29.1/29
bond0.30 10.0.30.1/24 u/u
100.64.30.1/29
eth0 192.168.122.14/24 u/u
eth1 - u/u
lo 127.0.0.1/8 u/u
::1/128
vyos@1.1.8:~$
vyos@1.1.8:~$
vyos@1.1.8:~$ show vrrp
Name Interface VRID State Last Transition
------ ----------- ------ ------- -----------------
BND011 bond0.11 11 MASTER 2m13s
BND012 bond0.12 12 MASTER 2m13s
BND013 bond0.13 13 MASTER 2m13s
BND014 bond0.14 14 MASTER 2m13s
BND015 bond0.15 15 MASTER 2m13s
BND016 bond0.16 16 MASTER 2m13s
BND017 bond0.17 17 MASTER 2m13s
BND018 bond0.18 18 MASTER 2m13s
BND019 bond0.19 19 MASTER 2m13s
BND020 bond0.20 20 MASTER 2m13s
BND021 bond0.21 21 MASTER 2m13s
BND022 bond0.22 22 MASTER 2m13s
BND023 bond0.23 23 MASTER 2m13s
BND024 bond0.24 24 MASTER 2m13s
BND025 bond0.25 25 MASTER 2m13s
BND026 bond0.26 26 MASTER 2m13s
BND027 bond0.27 27 MASTER 2m13s
BND028 bond0.28 28 MASTER 2m13s
BND029 bond0.29 29 MASTER 2m13s
BND030 bond0.30 30 MASTER 2m13s
vyos@1.1.8:~$Needs to migrate "maximum-paths" to afi and add ipv6 (1.3)
vyos@r1.3# set protocols bgp 65001 maximum-paths Possible completions: ebgp Maximum ebgp multipaths ibgp Maximum ibgp multipaths
Mar 11 2021
Still does not work in 1.4-rolling-202102060218
Moving tunnels between bridges works well in:
1.3-beta-202103110443
1.4-rolling-202102060218
Both UEFI and MBR boot modes are supported currently.
As a replacement for keys from Microsoft, it is possible to use our keys and ask users to install CA into a MOK database.
Fresh SNMP Daemon has some option which might be helpful
https://manpages.debian.org/unstable/snmpd/snmpd.conf.5.en.html
ifmib_max_num_ifaces NUM