PR for 1.3:
https://github.com/vyos/vyos-1x/pull/1187

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

From ISC-DHCP manual pages:
https://kb.isc.org/docs/isc-dhcp-44-manual-pages-dhcp-options

Re-tested in VyOS 1.4-rolling-202201140317
Now it works, thank you!

PR:
https://github.com/vyos/vyatta-cfg-firewall/pull/29/commits

In 1.3 (VyOS 1.3-rolling-202201030317) the rules are handled correctly (except for the numbers in description).

Tested in VyOS 1.3-rolling-202201030317 & 1.4-rolling-202201070726

The situation has not changed in VyOS 1.4-rolling-202201070726

Tested in VyOS 1.4-rolling-202201060842
Works

Checked in 1.3-rolling-202201030317, health-check works

PR for 1.2:
https://github.com/vyos/vyatta-cfg-vpn/pull/55

PR for 1.3:
https://github.com/vyos/vyatta-cfg-vpn/pull/54

@Viacheslav thank you so much for your help!

PR for 1.4:
https://github.com/vyos/vyatta-cfg-firewall/pull/28

PR for 1.3:
https://github.com/vyos/vyatta-cfg-firewall/pull/27

In 1.3.0 the limitation remains

Duplicate PR:
https://github.com/vyos/vyos-1x/pull/1118
Request revoked

@Viacheslav found the source of the restriction:

Didn't notice this message, thanks!
Maybe we should add a corresponding sync_group command to the CLI?

Have you tried writing the description with spaces in quotes?
Something like this:

Looks like the issue is persistent.
Tested on VyOS 1.3-beta-202112080938
Reboot VyOS (first one, wait for it to load. Then the other one)
'transition-script master' script doesn't start

There is a task with VRRP scripts problem on reboot:

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

A feature request was made with a change in behavior:
https://phabricator.vyos.net/T4005
(Feature Request: IPsec IKEv1 + IKEv2 for one peer)

pool request:
https://github.com/vyos/vyatta-cfg-vpn/pull/51
Create an Ike-group without a command "key-exchange" (like in VyOS 1.4):

Mentioned here (FRRouting):
BGP vpnv6 next hop address maybe error?

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

It seems to be because of the keepalived reloading at "commit".

Of course, external services with the same port is not available
This is what you should expect from NAT rules (110)
Works exactly as configured

WAN interface is eth2. It set to DHCP
LAN interface is eth3. It set to static address

Tested on VyOS 1.3.0-epa1

Tested in VyOS 1.2.8, VyOS 1.3.0-epa1, VyOS 1.4-rolling-202109190558

Tested in VyOS 1.3.0-epa1 & VyOS 1.4-rolling-202109190558

Tested on VyOS 1.3.0-epa1.
Confirm IBGP reflection to non-RR-Client
Lab Topology:

@francis Sorry, I don't understand the problem.
Agree that route received from one IBGP peer should not be forwarded to another IBGP peer. Except for the RR client.

If Cluster ID is not used, full IBGP mesh must be used. Exception is RR client, they should only have peering with RR.
Router 10.0.0.21 has no peering with 10.0.0.3.
This is incorrect IBGP design.

Perhaps the command should be changed a bit
MSS is a property of the TCP protocol, not IP:

Acknowledged. Tested on 1.3.0-epa1

Tested in vyos-1.4-rolling-202109190558,
works

Cisco Auth is a necessity for those who want to migrate from this vendor's hardware to VyOS. You can easily add a VyOS node to an existing DMVPN.