FRR match always mean logical AND
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 20 2022
In T4350#123620, @c-po wrote:Is the fix for DMVPN hub or spoke?
May 19 2022
There is an issue with vrf device for LOCAL direction
Imagine if you have 50 interfaces in one VRF and you want to drop all traffic from one interface for example - eth2 and don't touch other interfaces
You set firewall on eth2 Local - drop all traffic for device vrf and it will be affected to another 49 interfaces as iifname VRF_DEVICE the same
PR https://github.com/vyos/vyos-1x/pull/1330
set firewall name FOO default-action 'accept' set firewall name FOO description 'desc' set firewall name FOO rule 10 action 'drop' set firewall name FOO rule 10 source address '8.8.8.8' set interfaces ethernet eth0 firewall local name 'FOO' set interfaces ethernet eth0 vrf 'ONE' set vrf name ONE table '150'
Check:
table ip filter {
chain VYOS_FW_LOCAL {
type filter hook input priority filter; policy accept;
iifname "ONE" counter packets 63 bytes 6024 jump NAME_FOO
jump VYOS_POST_FW
}
...
chain NAME_FOO {
ip saddr 8.8.8.8 counter packets 79 bytes 6636 drop comment "FOO-10"
counter packets 3 bytes 984 return comment "FOO default-action accept"
}
}@jjakob could you re-check it with new fix?
May 18 2022
May 17 2022
May 16 2022
Need testing:
set service pppoe-server authentication mode 'radius' set service pppoe-server authentication radius rate-limit attribute 'Mikrotik-Rate-Limit' set service pppoe-server authentication radius rate-limit enable set service pppoe-server authentication radius rate-limit multiplier '0.001' set service pppoe-server authentication radius rate-limit vendor 'Mikrotik' set service pppoe-server authentication radius server 192.0.2.1 key 'foo' set service pppoe-server client-ip-pool start '192.0.2.5' set service pppoe-server client-ip-pool stop '192.0.2.254' set service pppoe-server gateway-address '192.0.2.1' set service pppoe-server interface eth3
Or any live example
May 15 2022
May 13 2022
May 12 2022
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1324
PR revert previous commit https://github.com/vyos/vyos-1x/pull/1323
May 11 2022
May 10 2022
@dmbaturin Do we really need this?
Maybe it will fix it https://github.com/sematext/oxdpus/blob/master/pkg/xdp/prog/xdp.c
I could be wrong
1.3.0-rc6 old release
Could you check it on more actual version?
PR for 1.4 https://github.com/vyos/vyos-1x/pull/1321
@zedalert Tested addresses should be different, as I remember it send pings with "interface" option
So targets should be different
May 8 2022
Duplicate T4359
May 6 2022
Try to delete sync-group, as you use only one group
May 5 2022
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1315
In 1.4 it working
set policy route-map FOO rule 10 action 'permit' set policy route-map FOO rule 10 set as-path-prepend 'last-as 2'
May 4 2022
I can't reproduce it
With such configuration all works fine VyOS 1.4-rolling-202204300743:
set load-balancing wan interface-health eth4 failure-count '5' set load-balancing wan interface-health eth4 nexthop 'dhcp' set load-balancing wan interface-health eth4 success-count '1' set load-balancing wan interface-health eth4 test 10 target '192.0.2.40' set load-balancing wan interface-health eth5 failure-count '5' set load-balancing wan interface-health eth5 nexthop 'dhcp' set load-balancing wan interface-health eth5 success-count '1' set load-balancing wan interface-health eth5 test 10 target '192.0.2.50' set load-balancing wan interface-health eth6 failure-count '5' set load-balancing wan interface-health eth6 nexthop 'dhcp' set load-balancing wan interface-health eth6 success-count '1' set load-balancing wan interface-health eth6 test 10 target '192.0.2.60' set load-balancing wan rule 10 failover set load-balancing wan rule 10 inbound-interface 'eth7' set load-balancing wan rule 10 interface eth4 set load-balancing wan rule 10 interface eth5 set load-balancing wan rule 10 interface eth6 set load-balancing wan rule 10 protocol 'all' set load-balancing wan sticky-connections
Configuration
# cat /etc/sshguard/sshguard.conf #### REQUIRED CONFIGURATION #### # Full path to backend executable (required, no default) BACKEND="/usr/lib/x86_64-linux-gnu/sshg-fw-nft-sets"
May 3 2022
Could you also provide cat /var/lib/dhcp/dhclient_eth4.leases ?
no-default-route ignore just option routers and don't touch other options like classless-static-routes
https://github.com/vyos/vyos-1x/blob/2c29a3b3b46c7570f4a509f413b208348c0ce647/data/templates/dhcp-client/ipv4.tmpl#L18-L19
May 2 2022
Apr 28 2022
Apr 27 2022
@RyVolodya could you recheck it?
Try to replace option restart to reload-or-restart and re-configure from scratch, it may help.
https://github.com/vyos/vyos-1x/blob/363ecfa46cdb8402ea71637717863f01b09f428b/src/conf_mode/protocols_nhrp.py#L107
It is not only for dhcp, any service can be affected to this
There are no many check when we remove interface
@fernando Does it work if you "reload" configuration?
Apr 26 2022
Works as expected
@pyaskowski try zone-policy firewall
Fixed VyOS 1.4-rolling-202204260601
set nat source rule 10 destination port '!22,telnet,http,123,1001-1005'
nft:
oifname "eth4" tcp dport != { 22-23, 80, 123, 1001-1005 } counter packets 0 bytes 0 masquerade comment "SRC-NAT-10"VyOS 1.3.1-S1 is not affected:
table ip nat {
chain PREROUTING {
type nat hook prerouting priority dstnat; policy accept;
counter packets 1 bytes 112 jump VYATTA_PRE_DNAT_HOOK
}