crux PR https://github.com/vyos/vyatta-wanloadbalance/pull/11
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Mar 11 2021
Mar 11 2021
c-po added a project to T2927: isc-dhcpd release and expiry events never execute: VyOS 1.2 Crux (VyOS 1.2.7).
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":[jack9603301 triaged T3305: Ingress qdisc does not work anymore in 1.3-rolling-202101 snapshot as High priority.
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
Viacheslav added a project to T3395: WAN load-balancing fails with nexthop dhcp: VyOS 1.2 Crux (VyOS 1.2.7).
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): 0jack9603301 moved T3305: Ingress qdisc does not work anymore in 1.3-rolling-202101 snapshot from Open to Finished on the VyOS 1.4 Sagitta board.
jack9603301 closed T3305: Ingress qdisc does not work anymore in 1.3-rolling-202101 snapshot as Resolved.
jack9603301 added a comment to T3305: Ingress qdisc does not work anymore in 1.3-rolling-202101 snapshot.
Now the problem should be solved
Viacheslav added a comment to T3396: syslog can't be configured with an ipv6 literal destination in 1.2.x.
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'
Viacheslav moved T3396: syslog can't be configured with an ipv6 literal destination in 1.2.x from Open to Backport Candidates on the VyOS 1.4 Sagitta board.
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.
jack9603301 added a comment to T3305: Ingress qdisc does not work anymore in 1.3-rolling-202101 snapshot.
Now, let's move the patch to 1.3
Mar 10 2021
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
Mar 9 2021
c-po added a comment to T3376: Setting ipv6 address autoconf causes all interfaces besides the target to lose their IP.
Did they also loose their IPv4 assignment?
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.102 / 5.10.20 to Update Linux Kernel to v5.4.104 / 5.10.22.
Fixed in next rolling release.
c-po moved T3382: Error creating Console Server from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3382: Error creating Console Server from Need Triage to Finished on the VyOS 1.3 Equuleus board.
A very nice test, I always tested with USB to serial adapters and not with a real serial port.
Viacheslav added a comment to T3396: syslog can't be configured with an ipv6 literal destination in 1.2.x.
PR for "current" https://github.com/vyos/vyos-1x/pull/764
Viacheslav added a comment to T3396: syslog can't be configured with an ipv6 literal destination in 1.2.x.
Expected format @[2001:db8::2]:514
Viacheslav moved T3392: vrrp over dhcp default route bug (unexpected vrf) from Open to Backport Candidates on the VyOS 1.4 Sagitta board.
Looks good on 1.4-rolling-202103090218:
Viacheslav changed the status of T3392: vrrp over dhcp default route bug (unexpected vrf) from Open to Needs testing.
Viacheslav moved T3271: qemu-kvm grub issue from Open to Backport Candidates on the VyOS 1.4 Sagitta board.
I kill the vm 80+ times.
All works fine.
@c-po can we "cherry-pick" it to 1.3.0?
Mar 8 2021
Mar 8 2021
stepler changed the status of T3395: WAN load-balancing fails with nexthop dhcp from Open to In progress.
Looks good on 1.4-rolling-202103080218:
Looks good on 1.4-rolling-202103080218:
Mar 7 2021
Mar 7 2021
vrf detected even it not created
https://github.com/vyos/vyos-1x/blob/dd35eb76153191bc487e3ea23c3e73c753ec1d4b/src/etc/dhcp/dhclient-enter-hooks.d/03-vyos-ipwrapper#L55-L59
root@r-roll01:/home/vyos# basename /sys/class/net/eth1/upper_* | sed -e 's/upper_//' eth1v1
Viacheslav updated the task description for T3392: vrrp over dhcp default route bug (unexpected vrf).
Viacheslav renamed T3392: vrrp over dhcp default route bug (unexpected vrf) from vrrp over dhcp default route bug to vrrp over dhcp default route bug (unexpected vrf).
Viacheslav changed the status of T3300: Add DHCP default route distance from In progress to Needs testing.
Wrong behavior
Unknown Object (User) added a comment to T3353: PPPoE server wrong vlan-range generating config.
@Viacheslav , thanks for improving, now it works properly. I found one interesting moment, it looks like we cant configure via CLI listen to PPPoE clients on interfaces eth1 and eth1.50 or eth1.something at the same time.
vyos@vyos# run show configuration commands | match "pppoe-server interface" set service pppoe-server interface eth1 vlan-id '50' set service pppoe-server interface eth1.1000 vlan-range '1-4095' [edit] vyos@vyos# set service pppoe-server interface eth1
Viacheslav moved T3379: Add global-parameters name-server for dhcpv6-server from Open to Backport Candidates on the VyOS 1.4 Sagitta board.
Also does not display other interfaces under the end node
vyos@RTR1# run show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
eth0 xxx.xxx.36.246/24 u/u
lo 127.0.0.1/8 u/u
::1/128
tun0 2001:470:xxxx:xxx::2/64 u/u HE.NET IPv6 Tunnel
[edit]
vyos@RTR1# run show interfaces tunnel
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
[edit]
vyos@RTR1# run show interfaces ethernet
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
[edit]
vyos@RTR1#Mar 6 2021
Mar 6 2021
For 1.2 this could be evaluated in the tunnels node.def file by something like:
c-po moved T3381: Change GRE tunnel failed from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po moved T3381: Change GRE tunnel failed from Backport Candidates to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3381: Change GRE tunnel failed from Needs Triage to Backlog on the VyOS 1.2 Crux (VyOS 1.2.7) board.
Mar 5 2021
Mar 5 2021
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.101 / 5.10.19 to Update Linux Kernel to v5.4.102 / 5.10.20.
Submitted this PR to fix the issue:
Mar 4 2021
Mar 4 2021
Viacheslav changed the status of T3388: show interfaces doesn't display pppoeX from Open to Confirmed.
Expected output, in VyOS 1.3.0-rc1 works fine
showvyos@vyos:~$ show int
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
eth0 - u/u WAN01-pppoe
eth1 10.0.0.1/24 u/u LAN
eth2 192.0.2.12/24 u/u WAN02-dhcp
eth3 - u/u
lo 127.0.0.1/8 u/u
::1/128
pppoe0 10.1.1.101/32 u/uViacheslav renamed T3388: show interfaces doesn't display pppoeX from show interfaces don't show pppoeX to show interfaces doesn't display pppoeX.
Viacheslav changed the status of T3386: PPPoE-server don't start with local authentication from Open to Needs testing.
Viacheslav changed the status of T3211: ability to redistribute ISIS into other routing protocols from Open to Needs testing.
Backport to 1.3 done
c-po moved T3386: PPPoE-server don't start with local authentication from Backport Candidates to Finished on the VyOS 1.4 Sagitta board.
c-po moved T3386: PPPoE-server don't start with local authentication from Need Triage to Finished on the VyOS 1.3 Equuleus board.
Viacheslav moved T3386: PPPoE-server don't start with local authentication from Open to Backport Candidates on the VyOS 1.4 Sagitta board.
c-po moved T3381: Change GRE tunnel failed from Open to Backport Candidates on the VyOS 1.4 Sagitta board.
Issue also exists in VyOS 1.2.7-rc1
Unexpected redistribution for isis VyOS 1.4-rolling-202103040218
Unknown Object (User) added a comment to T3386: PPPoE-server don't start with local authentication.
There is a bug exactly with client-ip-pool range, config generated with the mistake
[ip-pool] gw-ip-address=10.1.1.1 10.1.1.100-10.1.1.111
but expected
10.1.1.100-111