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

Age	Commit message (Collapse)	Author
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.