The changes are also part of the patch for T2057 which was merged.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 29 2020
All my apologies for this stupid bug.
Feb 24 2020
The patch is ready for inclusion.
This work raised an issue with the current pattern of using Interface(..).remove() which is used in VLANIf as it requires Interface to know that EthernetIf can not be deleted (an implementation detail which should remain in EthernetIf).
Feb 20 2020
This work overtakes T2046, as it implements the same _create/_delete interface. If merged it would replace it.
Feb 19 2020
We could indeed create the VRF as we parse interfaces, and auto-allocate the VRF number, removing this control from the user.
Feb 18 2020
should for multiple routing tables:
https://andir.github.io/posts/linux-ip-vrf/
http://www.allgoodbits.org/articles/view/24
https://patchwork.ozlabs.org/patch/546171/
Feb 17 2020
Feb 14 2020
initial patch released calling for a review / comments ( PR from github.com/thomas-mangin/vyos-1x T2028 branch) - show command not migrated yet.
Feb 12 2020
> egrep -ri '[^ag]gre[^apens]' . ./data/templates/rsyslog/rsyslog.conf:$RepeatedMsgReduction on ./src/op_mode/maya_date.py: August 11, 3114 BC gregorian date. In this case UNIX epoch
Could be away. But from my experience most people use vrf to seperate managment from production, and as second prio seperate customers and so on.
But the managment vrf must not be the "default" vrf.
Here is a patch to implement VRF. Binding is set to work on all VRF for daemon so that BGP and other protocols will work on all VRF.
https://gist.github.com/thomas-mangin/7704c538d905190bd05cfe613bd9f4f5
while it would be quite nice to have a Cumulus 4.0+ like default management VLAN and make all services management aware (which would quite considerably increase the among of work to get something out), I am proposing instead make sure that all services running on the default VRF are available on VRF as a first step.
Feb 10 2020
suggesting https://github.com/vyos/vyos-1x/pull/217
Feb 5 2020
Identified configuration format change:
I have a use case for VRF / Linux namespace with VyOS and was wondering if there was a way to break this task down, first allowing the manual creation of VRF/namespace using the CLI (without linking the work to BGP). I will be able to contribute the required changes to the vyos-1x repository should I be given enough direction on how you would like to proceed.