Maybe it will fix it https://github.com/sematext/oxdpus/blob/master/pkg/xdp/prog/xdp.c
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 10 2022
PR for 1.4 https://github.com/vyos/vyos-1x/pull/1321
May 9 2022
Tested on the latest rolling release:
May 8 2022
Duplicate T4359
May 7 2022
May 6 2022
PR for VyOS 1.3 https://github.com/vyos/vyos-1x/pull/1318
1.3 fix via https://github.com/vyos/vyos-1x/pull/1318
In T4417#123158, @Viacheslav wrote:Try to delete sync-group, as you use only one group
I was able to reproduce issue on latest VyOS 1.4-rolling-202205060217
Steps to reproduce:
1 - Fresh/clean vyos router
2 - Add interface configuration (dhcp on WANs and static IP addresses on LAN side), commit and save
3 - Add next WLB configuration:
Try to delete sync-group, as you use only one group
May 5 2022
Implemented as set policy route-map FOO rule 10 set as-path prepend-last-as 2
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1315
PR for 1.3: https://github.com/vyos/vyos-build/pull/231
PR for 1.4: https://github.com/vyos/vyos-build/pull/230
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
If it helps, I am also getting the exact same errors and problems, would love to see this working please
May 2 2022
We also need to verify remote-as in v6only or interface definitions:
May 1 2022
Apr 30 2022
Apr 29 2022
Apr 28 2022
I've tried with a new spoke and I can't seem to register using `reload-or-restart', although it resolved the lost connectivity issues the opennhrp process needs a full restart. however, if you restart opennhrp daemon it causes different issues and usually the spoke loses connection.
## hub
Thank you, team, for such a quick response to my request. I have not even had the chance to test it yet but trust that this will work perfectly. Again, many thanks!
