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
Previous example was expanded, in order to test filtering between native bridge interface and vlans interface on bridge.
Filtering rules:
I'm experiencing this with a custom ISO built from the stable 1.3 sources. Haven't done further debugging yet, a bgpd restart helped every time.
In 1.3 (VyOS 1.3-rolling-202201030317) the rules are handled correctly (except for the numbers in description).
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
I just realize it's getting more complicated as python/vyos/firewall.py will later write out the rules for these empty groups and when reading-them in, nftables will complain (again) when trying to resolve them, e.g.
Pythonic reimplementation complete. Now only the XML op-mode definition and the auto-complete script remain.
To my understanding, the template data/templates/firewall/nftables.tmpl is probably the culprit, as it doesn't check whether group_conf.address (and similarly the others) has any elements at all and introduces the offending white-space:
In ISC dhcpd this corresponds to the boot-size option http://www.ipamworldwide.com/ipam/isc-dhcpv4-options.html
Package upgraded
Filtering tested on version 1.4-rolling-202201060842
I revisited this in: https://github.com/vyos/vyos-1x/pull/1147
@Viacheslav Yes, You're right.
in.tftpd got started (but only a few seconds).
Scenario proposed by @NikolayP gives next content in table ip filter:
A simple check works fine:
Set 20% quota for snmpd
And check it with script:
#!/usr/bin/env bashIt was fixed in above commits, wrong testing form my site.
@aha As I see tftp can't bind ipv6 link local address:
Cherry-pick PR https://github.com/vyos/vyos-1x/pull/1146
It requires checking for 1.3 as it was changed and it uses the old backend on Perl (links above).
vyos@vyos# run show config comm | grep fire set firewall name FOO default-action 'accept' set firewall name FOO rule 10 action 'accept' set firewall name FOO rule 10 source address '198.51.100.0/24' set firewall name FOO rule 999997 action 'drop' set firewall name FOO rule 999997 source address '203.0.113.0/24' [edit]
It seems -V option:
PR for 1.3 https://github.com/vyos/vyos-nhrp/pull/7
PR for 1.4 https://github.com/vyos/vyos-1x/pull/1145
Check a real generated firewall iptables/nftables config
As 10000 it is the latest default rule, so your rules can be applied after default action with seq 10000
Could you also create a pr for 1.4?
Or 1.4 doesn’t have such limits?
Does it work with vlan bridges T3115?
Some notes:
Tested in VyOS 1.3-rolling-202201030317 & 1.4-rolling-202201070726
@NikolayP Could you test if all works fine?
Check the real generated firewal rules.
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.
It requires option -6
For example:
sudo ip -6 rule add prio 10 from de:de::1 lookup 5
Show v6 rules:
vyos@r11-roll# sudo ip -6 rule show 0: from all lookup local 10: from de:de::1 lookup 5 32766: from all lookup main [edit] vyos@r11-roll#
The situation has not changed in VyOS 1.4-rolling-202201070726
Tested in VyOS 1.4-rolling-202201060842
Works