This changes the parameters for four functions in HAProxy.php.
The ACME Client appears to call these functions with positional rather than named params
so also switch the order of the parameters in these function calls in
* Convert TAYGA virtual interface to interface group
Allows nat64 interface assignment (required for adding custom routes).
* Add nat64 interface to tayga interface group
Required because TAYGA virtual interface was converted to interface group in c350c81e49a89b9d57d3a86355907910b589a098.
* Add TAYGA configuration item to disable IPv6 route
* Add TAYGA GUI option to disable IPv6 prefix route
Required for adding custom routes.
* Add variable for disabling TAYGA IPv6 route
Required for adding custom routes.
* Add IPv6 route disable switch to TAYGA rc.d
Required for adding custom routes.
* Update TAYGA plugin to version 1.2
New feature: Custom IPv6 Routing
* Update TAYGA plugin to version 1.2
New feature: Custom IPv6 Routing
* Configure routes after TAYGA start
Required for custom routes.
* net/frr add bgp weight attribute and move disable-connected-check to the correct place. it looked like "community lists" missed a toggle action, added that as well.
While working on an Azure setup where the neighbor isn't within visible range, we stumbled upon the "disable-connected-check" option to allow loopback addresses.
Reading a bit further there seem to be different ways of dealing with similar kind of situations.
Either by setting an ebgp-multihop ttl value or to enable the disable-connected-check option. Since the multihop didn't come with a help text, it seemed like a good idea to add at least the upstream frr one. Knowning that the current multihop fieldtype currently is wrong ("enabling" will set a ttl of 255, where it should have been a number)
Franco Fichtner
Michael
Patrik Kernstock
Frank Wall
Jan Winkler
Gavin Chappell
Maurice Walker
corentin
Ad Schellevis
Budiman Jojo
Malware Utkonos