PR for the first issue:
https://github.com/vyos/vyos-1x/pull/3960
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 8 2024
Aug 7 2024
The PR above:
https://github.com/vyos/vyos-1x/pull/3876
As this will be a change in behavior, we may want to wait before backport to 1.4.x; remove tag for now, until inclusion in current and Circinus.
The PR
https://github.com/vyos/vyos-1x/pull/3937
will be moved out of draft following:
T6640 https://github.com/vyos/vyos-1x/pull/3955
Aug 6 2024
Aug 5 2024
Aug 4 2024
Aug 2 2024
Aug 1 2024
Jul 31 2024
Jul 30 2024
My opinion is largely based on my recent use-case for this, the GRE-match ethertype fields. I remember grumbling a couple of times about needing to convert bases to decimal in the past, but it's been too long to remember specifically what I was configuring at the time.
Top level op mode words have specific meanings in VyOS. clear is reserved for completely non-disruptive operations: clearing the screen, clearing rule counters... reset is for locally-disruptive operations.
Since removing a neighbor table entry can lead to lost packets or increased latencies for new connections, it doesn't qualify for clear, which is why it was called reset.
I'd prefer to keep that terminology consistent. BGP neighbors in Cisco IOS are also under clear, but we don't plan to mimic that, do we? ;)