Works fine VyOS 1.3-stable-202308240442
vyos@r1# run generate wireguard client-config c1 interface wg0 server 203.0.113.1 address 10.0.0.2/32
Works fine VyOS 1.3-stable-202308240442
vyos@r1# run generate wireguard client-config c1 interface wg0 server 203.0.113.1 address 10.0.0.2/32
Implemented, checked in VyOS 1.3-stable-202308240442
vyos@r1# set policy local-route Possible completions: > local-route IPv4 policy route of local traffic > local-route6 IPv6 policy route of local traffic
Already present VyOS 1.3-stable-202308240442
release dhcp interface eth1
Looks like fixed VyOS 1.3-stable-202308240442
vyos@r1# run show conf com | match "traf|bon" set interfaces bonding bond0 member interface 'eth1' set interfaces bonding bond0 traffic-policy in 'BAND-IN' set traffic-policy limiter BAND-IN class 1601 bandwidth '100mbit' set traffic-policy limiter BAND-IN class 1601 match 16xx vif '1601' set traffic-policy limiter BAND-IN default bandwidth '10gbit' set traffic-policy shaper BAND-OUT class 1602 bandwidth '100mbit' set traffic-policy shaper BAND-OUT class 1602 match 16xx vif '1602' set traffic-policy shaper BAND-OUT default bandwidth '10gbit' [edit] vyos@r1# run show ver
We agree not to use RAW options for service configuration anymore.
Fixed VyOS 1.3-stable-202308240442
vyos@r1# show interfaces ethernet eth2 description LAN hw-id 52:54:00:6c:c7:ac vrf foo [edit] vyos@r1# compare [edit interfaces bridge br11] +member { + interface eth2 { + } +} [edit] vyos@r1# [edit] vyos@r1# commit [ interfaces bridge br11 ] Can not add interface "eth2" to bridge, it has a VRF assigned!
Works, tested with this steps https://docs.vyos.io/en/latest/installation/virtual/docker.html
root@r14:/home/vyos# podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d49f99e058d7 localhost/vyos:1.3-stable-202308240442 /sbin/init About a minute ago Up About a minute ago vyos root@r14:/home/vyos# root@r14:/home/vyos# root@r14:/home/vyos# sudo podman exec -ti vyos su - vyos vyos@vyos:~$ vyos@vyos:~$ vyos@vyos:~$ show version
@kroy What is wrong here?
set policy prefix-list foo rule 10 action 'permit' set policy prefix-list foo rule 10 prefix '10.0.0.0/8'
Implemented in previous versions, https://github.com/vyos/vyos-1x/blob/a5c5998a84917cc45f9fb3234607f53b27a109fc/interface-definitions/include/interface/mirror.xml.i#L1-L25
vyos@r1# set interfaces ethernet eth0 mirror Possible completions: egress Mirror the egress traffic of the interface to the destination interface ingress Mirror the ingress traffic of the interface to the destination interface
The cluster feature will be deprecated, as we use systemd we should avoid init.d scripts.
All logic should be rewritten to VRRP
I don't see any errors in VyOS 1.3-stable-202308240442
vyos@r1# set firewall group network-group FW-OUT network '191.200.161.8/31' [edit] vyos@r1# set firewall group network-group FW-OUT network '191.200.161.8/32' [edit] vyos@r1# commit [edit] vyos@r1# delete firewall group [edit] vyos@r1# commit [edit] vyos@r1#
Fixed
[edit] vyos@r1# set policy route-map TEST rule 10 set metric -10 [edit] vyos@r1# commit [edit] vyos@r1# sudo vtysh -c "show run" Building configuration...
I assume this will fix by itself if you build your own 1.3.3 LTS from sources today since 1.3.3 LTS was released in june 2023:
PR f or 1.3.4 https://github.com/vyos/vyos-1x/pull/2168
@zsdc Can we backport it to 1.3?
The short story:
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2158
Pull request #2156 opened
https://github.com/vyos/vyos-1x/pull/2156
Tested after merging T5476 and now we see a proper DHCP release message
It could be incorrect process name name='ddclient - sleeping for 10 seconds' expectedd ddclient, possible bug after commit https://github.com/vyos/vyos-1x/commit/58a20e42087cbb7a1b3b4725fa40fd15a31bb4ed
psutil.Process(pid=2282, name='sshd', started='12:29:23') psutil.Process(pid=2283, name='vbash', started='12:29:23') psutil.Process(pid=2625, name='rsyslogd', started='12:30:31') psutil.Process(pid=9841, name='vbash', started='13:02:24') psutil.Process(pid=10249, name='kworker/u2:1-events_unbound', started='13:03:58') psutil.Process(pid=10735, name='kworker/0:1-mm_percpu_wq', started='13:10:42') psutil.Process(pid=10737, name='kworker/u2:2-events_unbound', started='13:10:42') psutil.Process(pid=10987, name='ddclient - sleeping for 10 seconds', started='13:12:47')
interesting, as the above diff actually does the same but a bit earlier in the boot process
I was able to fix by adding the following code in /config/scripts/vyos-postconfig-bootup.script you can edit and save by running:
I can confirm that the issue is still here, something is wrong and usually when you assign ipv6 address to sub-interface like vlan or bridge etc.
How is your IPv6 config from the VyOS config?
I am having this exact problem and it evidently has been a problem for quite a few years.