- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
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
Has this one been resolved by adding named VRF targeting?
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 :
Feb 19 2025
Tested as working in: VyOS 1.5-rolling-202502190007
Closing this, new tasks can be opened for any issues found in new WLB.
Please re-open if this is encountered in new WLB.
This should not be an issue in new implementation
PR for new implementation: https://github.com/vyos/vyos-1x/pull/4356
Initial implementation PR https://github.com/vyos/vyos-vpp
Engineid cli is not ok:
Feb 18 2025
@markh0338 Are you able to add a Pull Request?
Small note, to reproduce it, you have to have at least one route not related to vpp interface, like the default route via eth0, but vpp interface eth1
delete vpp commit