Same issue. I'm happy to send my config file (not publically) for further debug if that'll help?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Mar 11 2021
Most likely this should be done (after firewall rewrite) as jump statements.
Kernel related part is located here: https://github.com/vyos/vyos-build/tree/current/packages/linux-kernel
The rest is here: https://docs.vyos.io/en/latest/contributing/build-vyos.html
The idea stays actual, but unfortunately, it needs now to be rewritten according to the new config implementation.
just tested - 1.2.6-S1 - it is still working as described by ciprian.craciun
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":[Configured SNMP also add impact
top - 12:51:59 up 3:25, 2 users, load average: 1.35, 0.70, 0.28 Tasks: 214 total, 2 running, 210 sleeping, 2 stopped, 0 zombie %Cpu0 : 0.0 us, 0.0 sy, 0.0 ni, 99.7 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st %Cpu1 : 22.6 us, 77.4 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu2 : 0.0 us, 0.3 sy, 0.0 ni, 99.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu3 : 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 9972.9 total, 6710.1 free, 2044.5 used, 1218.3 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 7195.8 avail Mem
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
vyos@r2-1.2.7-epa1:~$ 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@Viacheslav can confirm, issue is fixed in VyOS 1.3-beta-202103110443
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'
Sure thing, I'll try it again tomorrow.
I can't reproduce it. Updated successfully. from 1.2.6-s1 to 1.2.7-epa1
Fixed VyOS 1.3-beta-202103110443
set protocols rpki cache rtr-ham1.mhl-lab.net port '3323' set protocols rpki cache rtr-ham1.mhl-lab.net preference '2'
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
Curl should only need the private key, since it will extract the public key from it on demand. In any case the private key should probably be password protected and then you'd need some way of prompting for the password and provide it to curl using the --pass parameter.
Is there anything else I can do to help debug this issue?
One solution that I see, uses vif/svlan/cvlan.
Looks good on 1.4-rolling-202103100218:
The fix submitted is not working as intended.. both - and _ are allowed characters in dns, so this this break dns names with _ in them. Before anyone complains, rfc952 that sets the name definition disallows use of underscore in hostnames and top level domains, not subdomains where the use is fully valid
@mpueschel will be fixed in the next rolling 1.4 release, after 2021-03-10
Can you check it out?
This is still an issue.
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.
PR for "equuleus" https://github.com/vyos/vyos-1x/pull/765
@Dmitry @a952637635. It seems that, I changed the handle address to avoid conflict. I don't know if it will conflict
@jack9603301 it looks like this issue related to your patch https://github.com/vyos/vyatta-cfg-qos/commit/6391325271be489d29f0b7aa2982952068c6a53c
T3089
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.
A very nice test, I always tested with USB to serial adapters and not with a real serial port.
Also, add some overhead netplug
top - 19:14:34 up 26 min, 1 user, load average: 10.29, 13.17, 8.57 Tasks: 568 total, 5 running, 228 sleeping, 0 stopped, 335 zombie %Cpu0 : 5.0 us, 10.6 sy, 0.0 ni, 84.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu1 : 9.8 us, 15.2 sy, 0.0 ni, 75.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu2 : 40.7 us, 3.0 sy, 0.0 ni, 56.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu3 : 9.6 us, 86.4 sy, 0.0 ni, 4.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3870.9 total, 1375.2 free, 1499.9 used, 995.8 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 1716.8 avail Mem
PR for "current" https://github.com/vyos/vyos-1x/pull/764
Expected format @[2001:db8::2]:514