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

PR for ping https://github.com/vyos/vyos-1x/pull/1175

Close the task
@Watcher7 Re-test it or describe steps hot to reproduce, as since 1.2-rc2 was implemented a lot of changes regarding vrf + frr.
You can set both vrf + next-hop address

Some detail here T1280

@sdev: in your original commit for this task, recent rules are somehow semi-discarded (the time/counter condition will not be written out; however, the action will be written out) because of an apparent problem with nftables in this area.

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

Previous example was expanded, in order to test filtering between native bridge interface and vlans interface on bridge.
Filtering rules:

• Filter traffic from vlan br0.55 to br0.66
• Filter traffic from vlan1 to br0.55
• Allow all

Ah! ok, I will close this. Looking at the man pages, seems like open nhrp doesn't have a no-unique registration feature?

We don’t use frr nhrpd, more details T2326
We use opennhrp

Filtering tested on version 1.4-rolling-202201060842

A simple check works fine:
Set 20% quota for snmpd
And check it with script:

#!/usr/bin/env bash

https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html

It was fixed in above commits, wrong testing form my site.

Cherry-pick PR https://github.com/vyos/vyos-1x/pull/1146

It seems -V option:

Is it an actual task? If yes, can someone explain which configuration you expect from keepalived.conf or radvd.conf?
As I see PR 9aad6f was merged.

@rps this did not make it into 1.3.0, but was discussed recently and will be addressed; it is, as you point out, a regrettable omission in functionality

Do we know if this made it into the 1.3.0 release or is this now a 1.4 issue?

Fixed for 1.4 in T4128 with update "keepalived".
In 1.3 we don't update this pkg and it still has this bug.

Fixed in https://github.com/vyos/vyatta-cfg-vpn/pull/56

Maybe fixed in T4128

This sounds like a "peer-link" or "heartbeat-link" between two VyOS boxes. I have yet no idea how the CLI could look like, maybe you have one?

Suggested fix: https://github.com/vyos/vyatta-op/pull/52

This is a mutability issue: since under vyos-configd the script is loaded as module, global variables persist, however:

Configuration tested on 1.3 and 1.4 version.

Re-opened as this task regarding dhcp-server, not dhcp-client

Fixed VyOS 1.3.0:

vyos@r4# run show conf com | match dhcp
set interfaces ethernet eth2 vif 35 address 'dhcp'
[edit]
vyos@r4# run show int
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface        IP Address                        S/L  Description
---------        ----------                        ---  -----------
eth0             192.168.122.14/24                 u/u  WAN
eth1             203.0.113.14/24                   u/u  Lan
                 192.0.2.14/24                          
eth2             -                                 u/u  
eth2.35          10.0.2.10/24                      u/u

To reproduce:

set interfaces ethernet eth2 vif 35
set interfaces pppoe pppoe0 authentication password 'MYPASSWORD'
set interfaces pppoe pppoe0 authentication user 'MYUSER'
set interfaces pppoe pppoe0 default-route 'force'
set interfaces pppoe pppoe0 mtu '1492'
set interfaces pppoe pppoe0 redirect 'ifb0'
set interfaces pppoe pppoe0 source-interface 'eth2.35'
set interfaces pppoe pppoe0 traffic-policy out 'OUT2'
set interfaces input ifb0

Commit:

vyos@r11-roll# commit
[ interfaces pppoe pppoe0 redirect ifb0 ]
Cannot find device "pppoe0"
tc qdisc ingress failed at /opt/vyatta/sbin/vyatta-qos.pl line 334.

One issue with static + dhcp on one interface at the same time.
After renew, the static address 192.168.122.11 is disappears
To reproduce:

vyos@r11-roll:~$ show conf com | match eth0
set interfaces ethernet eth0 address '192.168.122.11/24'
set interfaces ethernet eth0 address 'dhcp'

Renew dhcp:

vyos@r11-roll:~$ renew dhcp interface eth0

Static address not in the system:

vyos@r11-roll:~$ show int
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface        IP Address                        S/L  Description
---------        ----------                        ---  -----------
eth0             192.168.122.166/24                u/u  WAN
eth1             203.0.113.1/24                    u/u

In VyOS 1.3.0-epa3

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

Somewhat related since about November builds of Vyos 1.4 I loose my firewall rules when I reboot and make a configuration change. If I do not make a configuration change it doesn't get wiped from the config. The ip table rules are still present but missing from the config causing a reboot to actually wipe the firewall rules... This is a little scary.

@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

@NikolayP Change it https://github.com/vyos/vyatta-cfg-firewall/blob/1e06e3f891f8238d565ff0eddb4cd8c9b6032346/templates/firewall/name/node.tag/rule/node.def#L5-L9 to the required range.

this requires a helper that will be responsible for the DNS resolution and update of the corresponding rules
each DNS resolution will refresh IPs every 15 seconds or in smart mode will rely on DNS TTL for records and will do a lookup on TTL expire (and update firewall if required)

Interestingly if vyos-configd is in use this bug is triggered. If vyos-configd is not used the bug is not triggered :/

In T891#20803, @Watcher7 wrote:

2. VyOS command syntax cannot currently specify both a next-hop and interface for the same static route, despite FRR being able to do so.