I think this should be considered expected behaviour, during the several iterations of the firewall (including Vyatta era - without explicit tables and chains) we've not changed the logic of enabling conntrack.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feb 28 2025
I did more tests. If I create any rule called conntrack (in input, forward, with different conditions), Conntrack affects all traffic that passes through or to the router.
Feb 27 2025
Feb 26 2025
Alright - I've created PRs https://github.com/vyos/vyos-1x/pull/4371 and https://github.com/vyos/vyos-documentation/pull/1603 for this one.
Feb 25 2025
We can build ixgbe, ixgbevf and ice drivers from GitHut source for Kernel 6.6
Feb 24 2025
Cannot reproduce it. It is necessary to get a configuration:
I tested this config and all works fine
VyOS 1.5-rolling-202502220006 + latest vyos-1x
set load-balancing haproxy backend bk01 server srv01 address '192.168.122.16' set load-balancing haproxy backend bk01 server srv01 check set load-balancing haproxy backend bk01 server srv01 port '8000' set load-balancing haproxy backend bk01 server srv02 address '192.168.122.16' set load-balancing haproxy backend bk01 server srv02 check set load-balancing haproxy backend bk01 server srv02 port '8888' set load-balancing haproxy service web backend 'bk01' set load-balancing haproxy service web port '80'
@Viacheslav Yes, I will test it once it is included in the next rolling release.
Feb 23 2025
Feb 22 2025
Feb 21 2025
@talmakion I think it good idea is removed , this attribute was added by cisco in the early day of internet, as you mentioned , it can be solved using 0:0 in a RM.
Can't reproduce the issue
Looks like this was deprecated in FRR a while ago: https://github.com/FRRouting/frr/commit/81a57d81812115bdbab25168e86e509e2db607a1
Feb 20 2025
It looks like the problem is in this `key_mangling', it's probably that function where these kind of errors are given:
I've extend the test in the enviorment , it looks like there is a problem with names in our policies : eg , where it brokes the configuration :
@daniel.arconada are you able to test it with the next rolling release? Those options will be included.
@daniel.arconada are you able to test it with the next rolling release? Those options will be included.