May be an upstream bug, possible fixed in https://github.com/acassen/keepalived/commit/2f1024d382783742df0e5c3dd705596f958b77b5
and https://github.com/acassen/keepalived/commit/5681838ac21de25b935632c5ec41569f79b48c19

PR https://github.com/vyos/vyos-1x/pull/1034

To disable shared-network at least one shared network should be working. The second can be disabled without issues.

PR https://github.com/vyos/vyos-1x/pull/1031

An interesting thing that I get the error with that configuration:

As an option it is possible this workaround:
Install tshark and use this script https://george.mibloving.net/nivex/d6rm/raw/commit/701d49cce3a308aed0c3d89d47be7601178ea4c4/d6rm.py

All subnets that share the same physical network should be declared within a shared-network declaration

Oct 18 22:24:01 r1-roll dhcpd[4985]: Interface eth2 matches multiple shared networks

@mickvav You can use &quot. Can you re-check it?
Tested on node VyOS 1.4-rolling-202110130217

As I know, iptables works only in UTC time. And any workaround with recalculate Datetime will be affected incorrect behavior.

As for me we shouldn’t allow to downgrade images. So there are no “downgrade migration scripts”. Each downgrade - good point to get a brick.
At least we should generate a warning.

PR for "crux": https://github.com/vyos/vyos-1x/pull/1029

@artooro Will be available in the next rolling release
Let us know, if you want some other capabilities

PR https://github.com/vyos/vyos-1x/pull/1027

Maybe be added to gether with T1229

@maznu Can you create a PR?

Initial bug was Fixed, VyOS 1.4-rolling-202110130217

vyos@r1-roll# compare 
[edit container]
+name dns02 {
+    image ubuntu:focal
+    network dnsnet {
+        address 10.0.72.253
+    }
+}
+network dnsnet {
+    prefix 10.0.72.0/24
+}
-network net01 {
-    prefix 10.0.72.0/24
-}

@c-po Is it already implemented with commit https://github.com/vyos/vyos-1x/commit/ae2dc55aa68679e828d4bb133fc515172c081d0f ?

Fixed, VyOS 1.4-rolling-202110130217

vyos@r1-roll:~$ show nat source rules 
Rule       Source                                             Translation                                        Outbound Interface
----       ------                                             -----------                                        ------------------
3          192.168.0.0/24                                     masquerade                                         eth0

As for me, it should be configured in the global firewall log level, not per rule.

set firewall log-level x

PR https://github.com/vyos/vyos-1x/pull/1026

PR https://github.com/vyos/vyatta-cfg-system/pull/170

The real bug is it shouldn't allow port-range values as it is not implemented.
Or just add this feature T2798

@foxbox Will be fixed in the next rolling release.

PR https://github.com/vyos/vyos-1x/pull/1025

@BiMW Can you re-check it?

Not reproducible, VyOS 1.4-rolling-202109300217

set service ipoe-server authentication radius dynamic-author key 'ssss'
set service ipoe-server authentication radius dynamic-author server '192.168.122.11'
set service ipoe-server authentication radius nas-ip-address '192.168.122.11'
set service ipoe-server authentication radius server 192.168.122.11 key 'ciscoradiuskey'
set service ipoe-server interface eth1 client-subnet '192.0.2.0/24'

@FileGo Can you replace double-quotes with single-quotes?

Fixed

sever@sever:~$ ssh [email protected]

Present in 1.4 and 1.3.0-epa1

set service pppoe-server authentication radius server 192.0.2.1 acct-port
Possible completions:
   <1-65535>    Numeric IP port (default: 1813)

@c-po in 1.3.0-epa1 works fine.

Re-opened, the same bug in VyOS 1.4-rolling-202109300217

sever@sever:~/docker$ ssh [email protected]

@SquirePug Can you share more details, which templates and parameters did you edit?

PR https://github.com/vyos/vyos-1x/pull/1022

@RyVolodya can you check a new image and close this task if it was fixed?

@francis It is not clear. Can you provide an example of configuration? What do you get and what do you expect?

The same bug described there T2845

Not sure why we should check the primary ip address, but to fix it possible to change:

if is_subnet_connected(subnet, primary=False)

It was described there T3610 and requires more tests.

PR https://github.com/vyos/vyos-1x/pull/1018
PR https://github.com/vyos/vyos-build/pull/192

@danielpo Will be fixed in the next rolling release.

PR https://github.com/vyos/vyos-1x/pull/1016
Change priority for nat66

PR https://github.com/vyos/vyatta-cfg-quagga/pull/89

Not all clients support the gateway option (get issues in mac and windows):
Mac

tun_prop_route_error: route destinations other than vpn_gateway or net_gateway are not supported

set interfaces openvpn vtun20 openvpn-option '--push dhcp-option DNS 203.0.113.1'

generated config:

--push dhcp-option DNS 203.0.113.1

expected configuration:

push dhcp-option "DNS 203.0.113.1"