Doesn't this feature exist in 1.5?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jun 10 2025
In T7476#226565, @badger42 wrote:@Viacheslav
can you provide an example of how to use policy route to control the source-interface of these packets?
Jun 9 2025
Yes, embedded shell scripts are incompatible with the idea to execute op mode commands through a wrapper, which is required for permission checking.
@Viacheslav
can you provide an example of how to use policy route to control the source-interface of these packets?
suppress-ra can currently be configured at the interface level in FRR, but this setting is overridden by bgpd if extended-nexthop is enabled
The problem is certainly real:
Jun 8 2025
Here's what I did to get a nice color prompt containing time, hostname, build version, working directory and when in config mode, a clear bright yellow "✎ edit »" line. with the actual path you're editing in. It then looks like this:
Need this fix to build libvyosconfig again.
https://github.com/vyos/libvyosconfig/pull/41
Directly use T7374 for tracking this.
This has been addressed in https://github.com/vyos/vyos-1x/pull/4266/ - we now support using openssh keys defined in the PKI subsystem as trusted root for TrustedUserCAKey.
An easy mitigation is to just update the command that is run to:
journalctl --no-hostname --boot -k | grep "ipv4-NAM-${6:0:15}"The only issue with this as the only solution, is you could lose granularity in logging if you were to have names like:
test-test-test-1 test-test-test-2
Running show log firewall ipv4 name test-test-test-1 would return log entries for both names since the string would be ipv4-NAM-test-test-test-. That's where a warning could come into play, stating it is recommended to keep names to no more than 15 characters.
Jun 7 2025
Also relevant refs:
Comparing to other vendors this setting should be set on interface level and not in bgp settings.