I like the idea. Maybe we can extend this logic to other things, like WireGuard or VPNs. @a.apostoliuk @dmbaturin
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Today
Yesterday
This is a different maniphestation of the same mistake I made in is_admin — not checking if the effective UID is already zero. User vyos is a red herring because it's the actual user name but what actually matters is the effective UID instead.
Yes after reboot the command works. So to male it work it seems to be necessary to reboot the system after adding the interface.
Wed, Dec 3
It was decided to configure forwarding automatically to simplify CLI for the user
Do interfaces exist in the config, or did you add them to the already loaded system but there is no interface ethernet ethX config?
Tue, Dec 2
Cisco and Arista support such addresses as interface addresses, and the anycast bit doesn't preclude unicast usage, so we should allow that.
Mon, Dec 1
Not sure if it is the correct fix but something with this logic https://github.com/vyos/vyos-utils/blob/dbecbd0c4f25f8b8d7055e5ed3ffc8e5be59b1f0/src/vyos_op_run.ml#L297
Sun, Nov 30
Sat, Nov 29
FRR case where there is a long explanation: https://github.com/FRRouting/frr/issues/15400
Fri, Nov 28
This comment in ipaddrcheck explains why I disallowed all-zero host part addresses: https://github.com/vyos/ipaddrcheck/blob/current/src/ipaddrcheck_functions.c#L337-L346
I think this should be handled in documentation and not alter the code behaviour.