Frr doesn't provide such option for ipv4, only for ipv6

It does not work when established / invalid rules are at the top of the access list in any order. This works if the invalid state rule is positioned after the GRE rule, but this is not an expected behavior.

Try to place that rule after established, for example, number 25

Duplicate T3349

Update pr

remote.py declaring support for TFTP and HTTP(S) might complicate things further. Since it's only for downloading, the latter shouldn't be too complicated to handle with urllib but if we need HTTP(S) uploading capabilities, an external library like requests would be preferable. As for TFTP, there's no support for it in the standard library, but instead of pulling in a third-party library for TFTP alone, we can just write an ad hoc wrapper for curl dedicated to TFTP. It wouldn't be as complicated since TFTP has no form of authentication so there's no need to worry about host keys and such.

I will try the latest

Yes, sure. It will work only if one vlan-id defined, e.g. if you configure a couple vlan-id you will get wrong syntax"

set service pppoe-server interface eth1 vlan-id '50'
set service pppoe-server interface eth1 vlan-id '60'

In generated config

vlan-mon=eth1,50,60
interface=eth1.50,60

Expected:

vlan-mon=eth1,50,60
interface=eth1.50
interface=eth1.60

PR https://github.com/vyos/vyos-1x/pull/755
@Dmitry Can you check/review PR?

Good job! I think there exists one remark. If we set set service pppoe-server interface eth1 vlan-id '50' that means you want to listen to pppoe client on eth1.50, but in config you have

vlan-mon=eth1,50
interface=re:eth1\.\d+

e.g. eth1\.\d+ mean all vlans in eth1, even eth1.50.50.50 will fit for this regular expression
I propose do not to use a regular expression for vlan-id, as an example:

1. set service pppoe-server interface eth1 vlan-id '50'

vlan-mon=eth1,50
interface=eth1.50

Yes, agree it works by show interfaces vrrp, but behavior in 1.2.x also displayed VIP by command show interfaces
I think this is a bug and need to fix it.

https://github.com/vyos/vyos-build/pull/150

https://github.com/vyos/vyos-build/pull/149

You can use <x.x.x.x>-<x.x.x.x>
Or you need "multi" addresses not in "range"? Something like

set nat destination rule 5 translation member 203.0.113.1
set nat destination rule 5 translation member 203.0.113.14
set nat destination rule 5 translation member 203.0.113.240

Temporary workaround for the VyOS 1.3-rc1 users:

I agree we should just check if it starts with a letter and doesn't include characters that an FQDN cannot have.

Backport is complete - It will "work" once the 1.3 kernel is updated to 5.10 series

A work-around for this was added in 1.2.6 and I verified it's working in 1.3.0-rc1

Just chiming back in to let you guys know I installed the latest vyos rolling release after all this time and the issue seems to have been fixed!

@craterman Thanks.

@Viacheslav, tested on VyOS 1.3-beta-202102270443. It works

Node "protocols" in 1.4 also doesn't have a description