vyos-1x.git - VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)

Age	Commit message (Collapse)	Author
2021-03-14	static: T3280: move building blocks to subfolder	Christian Poessinger
	As the amount of include files now has reached a certain amount, it is getting more and more crowsded, thuse introducing "per topic" subdirectories on the filesystem to keep a clean structure makes sense.
2021-03-14	xml: T1579: re-arrange xml interface include building blocks	Christian Poessinger
	As the amount of include files now has reached a certain amount, it is getting more and more crowsded, thuse introducing "per topic" subdirectories on the filesystem to keep a clean structure makes sense.
2021-03-14	vrf: T3344: set explicit priority values for routing protocols	Christian Poessinger
	We must ensure that an interface is already added to a VRF before it is referenced inside a VRF context, e.g. OSPF.
2021-03-14	vrf: T3344: move dynamic routing protocols under "vrf name <name> protocols"	Christian Poessinger
	Instead of having the dynamic routing protocols OSPF and BGP residing under the "protocols vrf <name> [ospf\|bgp]" nodes, rather move them directly under the "vrf name <name> protocols [ospf\|bgp]" node. Now all VRF related parts are placed under the same root node. This eases the verify steps tremendously, as we do not need to check wheter a VRF eists or not, it will always exist as we operate under a child node.
2021-02-05	vrf: T2450: provide full protocol support in XML and Python with new CLI	Christian Poessinger

2021-01-16	vrf: T31: migrate to get_config_dict()	Christian Poessinger

2021-01-13	ssh: T3212: do not make /run/sshd directory disappear on failure	Christian Poessinger

2020-07-04	vrf: T31: lower startup priority to 60	Christian Poessinger
	VRFs should be created as early as possible.
2020-05-30	vrf: T2530: instance name must be 15 characters or less	Christian Poessinger

2020-04-03	vrf: T31: name of isntance is not allowed to mimic an interface name	Christian Poessinger
	Every VRF that's created is not allowed to be named like any interface that can be active on the system. This includes eth, lan, br, dum, lo .... In theoriy this would work but as soon as such a regular interface is created things will go sideways rather quick thus we limit the namespace which can be used to create a VRF. Appending an interface name is still possible like coolvrf-eth0.
2020-03-29	vrf: T2178: table id must start at 100	Christian Poessinger
	... to not cause any issues with buildin tables or PBR. PBR uses table 1 - 200 so there is a small overlap (by intention)
2020-03-04	vrf: T31: rename 'vrf disable-bind-to-all ipv4' to 'vrf bind-to-all'	Christian Poessinger
	By default the scope of the port bindings for unbound sockets is limited to the default VRF. That is, it will not be matched by packets arriving on interfaces enslaved to an l3mdev and processes may bind to the same port if they bind to an l3mdev. TCP & UDP services running in the default VRF context (ie., not bound to any VRF device) can work across all VRF domains by enabling the 'vrf bind-to-all' option.
2020-03-04	vrf: T31: improve help for routing table	Christian Poessinger

2020-03-04	vrf: T31: reuse interface-description.xml.i for instance description	Christian Poessinger

2020-03-04	vrf: T31: use embedded regex on 'vrf name' instead of python script	Christian Poessinger

2020-03-04	vrf: T31: initial support for a VRF backend in XML/Python	Thomas Mangin
	This is a work in progress to complete T31 whoever thought it was less than 1 hour of work was ..... optimistic. Only VRF vreation and show is supported right now. No interface can be bound to any one VRF.