To reproduce it add firewall and attach it to interface
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Apr 4 2021
It is a priority for configurations
When the system load, the firewall should have configuration, and after configuration is applied to the interface.
So I think we can't delete it in one commit, it tried to delete the firewall before detaching the firewall from the interface.
Apr 3 2021
We can do some workaround for that level,
It seems that "call" doesn't react to env.
'VYATTA_EDIT_LEVEL': '/system/login'
Apr 2 2021
Apr 1 2021
Chown for saved configuration file should be frr:frr
Mar 31 2021
Expect
vyos@r5-roll# set protocols ospf redistribute isis Possible completions: metric OSPF default metric metric-type OSPF metric type for default routes (default: 2) route-map Route map reference
Mar 30 2021
@dtoux show ipv6 route vrf foo
To reproduce, on clean install 1.3.-rc3
set interfaces ethernet eth1 address '2620:18:6000:aa10::2/64' set interfaces ethernet eth1 vrf 'foo' set protocols vrf foo static route6 ::/0 next-hop 2620:18:6000:aa10::1 set vrf name foo table '1050'
@dtoux vtysh -c "show run"
Also, it doesn't show a directly connected ipv6 route.
The route present in the frr
! vrf foo ipv6 route ::/0 2620:18:6000:aa10::1 exit-vrf !
Mar 29 2021
Mar 28 2021
Possible reason "> 2" in description "Ruby > 2.3"
vyos@r5:~$ echo "Package versions:"; dpkg -l | grep ruby-curse -A 2 Package versions: ii ruby-curses 1.2.4-1+b1 amd64 curses binding for Ruby ii ruby-did-you-mean 1.2.1-1 all smart error messages for Ruby > 2.3
Mar 26 2021
@trystan Can you re-check it ?
Do we need "awscli" for it?
Fixed VyOS 1.4-rolling-202103251004
Mar 25 2021
It was a broken image.
Mar 24 2021
The problem with "ip" path
It gets DHCP address and removes it
Possible reason https://phabricator.vyos.net/rVYOSONEXff6afe62e801e570f6478decf2b4a813a5c0ee94
Need to check. T3300 T3392
Mar 23 2021
PR for saving configurations to /run/frr/{daemon}.conf
https://github.com/vyos/vyos-1x/pull/784
I can confirm:
Something wrong in your configuration
Can you share more examples/configs?
How can we reproduce it?
Mar 22 2021
@francis try please vyos-1.3.0-rc2-amd64.iso
https://community.vyos.net/get/snapshots/
Another solution it include "user" defined file for options
An example CLI
set interfaces openvpn vtun10 openvpn-option-include '/config/openvpn/included.conf'
Mar 20 2021
Service still with no description VyOS 1.3-beta-202103170443
Mar 19 2021
I think vlan range should be 1-4094
@zadm do you test it?
Mar 17 2021
@iomart-network-team You don't need to change any file, but you can.
If you change something in the file, it not a bug.
It more seems like some typo in the file, which you generate.
Proposed changes
Add hook/magic word string and write values in one string if word string in options is present
Mar 14 2021
Mar 12 2021
I use set. Then commit and "save" the configuration and reboot the server.
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
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":[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): 0Fixed 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'
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'
Mar 10 2021
One solution that I see, uses vif/svlan/cvlan.
@mpueschel will be fixed in the next rolling 1.4 release, after 2021-03-10
Can you check it out?