Implemented in VyOS 1.4
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Mar 14 2021
Example configurations:
I'm curious, I did a little research on Tacacs +, and I'm not sure what you want the certification service to do for you? SSH certification or?
Also CUMULUS has a nice looking package
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:
Yes, some time ago, it could produce kernel issues https://www.mail-archive.com/[email protected]/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.
Mar 11 2021
Still does not work in 1.4-rolling-202102060218
As a workaround, we can replace https://github.com/vyos/vyos-1x/blob/f892294239101aecc21a45629eb1d10bd89fba0b/python/vyos/ifconfig/vrrp.py#L95 to
from vyos.util import cmd
cmd(f'sudo kill -s {cls._signal[what]} {pid}')And get JSON values
vyos@r-roll01:~$ sudo cat /tmp/keepalived.json
[ { "data": { "iname": "test", "dont_track_primary": 0, "skip_check_adv_addr": 0, "strict_mode": 0, "vmac_ifname": "eth1v1", "track_ifp": [ ], "track_script": [ ], "ifp_ifname": "eth1v1", "master_priority": 100, "last_transition": 1615454936.7267461, "garp_delay": 5, "garp_refresh": 0, "garp_rep": 5, "garp_refresh_rep": 1, "garp_lower_prio_delay": 5, "garp_lower_prio_rep": 5, "lower_prio_no_advert": 0, "higher_prio_send_advert": 0, "vrid": 1, "base_priority": 100, "effective_priority": 100, "vipset": true, "vips": [ "172.20.110.111", "172.20.110.15" ], "evips": [ ], "promote_secondaries": false, "vroutes": [ ], "vrules": [ ], "adver_int": 1, "master_adver_int": 1, "accept": 1, "nopreempt": false, "preempt_delay": 0, "state": 2, "wantstate": 2, "version": 2, "smtp_alert": false, "auth_type": 0 }, "stats": { "advert_rcvd": 983, "advert_sent": 10535, "become_master": 1, "release_master": 0, "packet_len_err": 0, "advert_interval_err": 0, "ip_ttl_err": 0, "invalid_type_rcvd": 0, "addr_list_err": 0, "invalid_authtype": 0, "authtype_mismatch": 0, "auth_failure": 0, "pri_zero_rcvd": 2, "pri_zero_sent": 0 } } ]Or more readable:
{
"data":{
"iname":"test",
"dont_track_primary":0,
"skip_check_adv_addr":0,
"strict_mode":0,
"vmac_ifname":"eth1v1",
"track_ifp":[I don't seem to see the obvious problem (maybe I don't understand what you're referring to), assuming there is a problem and this is also an issue introduced by third party system components, maybe you should go upstream with feedback
VRRP return always [] <= nodata
https://github.com/vyos/vyos-1x/blob/f892294239101aecc21a45629eb1d10bd89fba0b/src/op_mode/show_interfaces.py#L68
Maybe don't have permissions to kill PID https://github.com/vyos/vyos-1x/blob/f892294239101aecc21a45629eb1d10bd89fba0b/python/vyos/ifconfig/vrrp.py#L95
The same bug with 1.2.7-epa1
set interfaces dummy dum0 set interfaces ethernet eth1 address dhcp set load-balancing wan interface-health eth1 nexthop dhcp set load-balancing wan rule 1 inbound-interface dum0 set load-balancing wan rule 1 interface eth1 commit
Status
[email protected]:~$ show wan-load-balance Interface: eth1 Status: active Last Status Change: Thu Mar 11 09:31:54 2021 +Test: ping Target: Last Interface Success: 0s Last Interface Failure: 2m35s # Interface Failure(s): 0
Now the problem should be solved
Fixed in VyOS 1.4-rolling-202103110218
set system syslog global facility all level 'info' set system syslog global facility protocols level 'debug' set system syslog host 192.168.122.1 facility all level 'all' set system syslog host 192.168.122.1 port '514' set system syslog host 2001:db8::2 facility all level 'all' set system syslog host 2001:db8::3 facility all level 'all' set system syslog host 2001:db8::3 port '514' set system syslog host 2001:db8::4 facility all level 'all' set system syslog host 2001:db8::4 port '514'
MD5 checksums are generated by Packer at build time (configured in vyos-build). We can switch to SHA256 or SHA512 (which Packer supports) although it seems redundant when the install script also fetches SHA256 sum file (guessed by the ISO URL) and compares against that. I'd say configuring Packer to use SHA256 and omitting SHA256 files from download directories altogether would be the cleanest solution.
Now, let's move the patch to 1.3
Mar 10 2021
One solution that I see, uses vif/svlan/cvlan.
Looks good on 1.4-rolling-202103100218:
Here is my current configuration. If I add any configuration to this and commit, it would not commit. It seems like there is something holding the commit from committing the new configuration.
We can't reproduce/fix it without any provided information/configuration.
Mar 9 2021
Did they also loose their IPv4 assignment?
Fixed in next rolling release.