| Age | Commit message (Collapse) | Author |
|---|
|
Commit 579275e ("ntp: T2230: move inlined templates to dedicated files")
altered the import statements for forgot to adjust the code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Commit 3d978249b313 ("wireless: T1627: move Jinja2 templates to data/templates
folder") remove a wildcard import statement which is required for MAC address
modification for the AP.
|
|
* 't2206-wireguard' of github.com:c-po/vyos-1x:
wireguard: T2228: support ports less then 1024
wireguard: T2206: add valueHelp for listen port
wireguard: T2206: split endpoint node into address and port
wwan: migrate: fix comment
|
|
|
|
|
|
WireGuard has been the only subsystem combining a remote ip address and a
remote port number into a single node. This is bad as there is no possiblity
for the XML based input validation for IP address and port numbers.
That's the reason the peer endpoint node goets migrated into a peer address
and a peer port node utilizing the embedded syntax node checking for IP
addresses and port ranges.
|
|
|
|
|
|
Commit 3d978249b313c ("wireless: T1627: move Jinja2 templates to data/templates
folder") made use of a new library function (chown_file) from vyos.util,
unfortunately the required import was somehow not added into the patch.
|
|
pim: T1729: Add dr-priority and IGMP join support
|
|
|
|
|
|
Now both files and directories are supported.
|
|
If the unreachable routes for IPv4 and IPv6 are not deleted, there will be an
error when creating the same VRF again after removal.
Error changing VRF: Command '['sudo', 'ip', '-4', 'route', 'del', 'vrf',
'Blue', 'unreachable', 'default', 'metric', '4278198272']' returned
non-zero exit status 2.
|
|
|
|
This is a low level requirement for supporting l2vpn evpn.
|
|
ifconfig: T2190: option to prevent Interface creation
|
|
wireless: T2211: bugfix: vht_oper_chwidth was not set in hostapd config
|
|
ifconfig: T2205: silence ethtool harmless failures
|
|
openvpn: T2222: set 'multihome' option when local-host is unset
|
|
wireless: T2208: bugfix: errors in the XML and Python file
|
|
Should the openvpn status file not be present, present a blank
interface.
|
|
When any defaults are set, VHT capabilities are automatically assumed
for all WiFi modes which does not match the reality. Therefore we must
leave this undefined by default.
|
|
|
|
When operating in certain modes, channel width must be configured for
WiFi interfaces. The hostapd config does this in two separate lines
which must both be configured:
vht_oper_chwidth=(0|1|2|3)
vht_capab+=[VHT160] for 160MHz in one block or
vht_capab+=[VHT160-80PLUS80] for 160MHz as 2x 80MHz in two separate
blocks.
|
|
The old implementation actually did not work as the Quotes "" around the
"vrf foo" statement got actually lost in translation.
|
|
Commits to
"interfaces wireless wlanX capabilities vht link-adaptation (unsolicited|both)"
always failed.
|
|
a new option was added to the Interface class "create".
By default the value is set to True, and when an instance of the
class is created and the underlying interface does not exists, the
class will create it.
If the option "create" is set to False, the interface will not be
created and instead the class will raise an error when it is
instantiated.
|
|
If configured with protocol udp and no local-host, openvpn needs
the 'multihome' option to correctly work on all addresses.
|
|
Commit b250b233ec1 ("pppoe: T1318: move Jinja2 templates to data/templates
folder") actually placed the pre-up configuration script into the ip-up
folder.
|
|
|
|
|
|
Not all interface are capable of all features. Since commands are
now checked for valid completion, ethtool command failure must
be ignored.
|
|
As PPPoE interfaces should be part of a VRF it is required that the default
can also be set into the specified VRF. The default way of PPP by setting the
"defaultroute" option does not take a VRF into account. In this case PPP
installs a Kernel route forwarding all default traffic over this interface.
This change installs a static route with metric 1 instead into the routing
table via FRR. This is not the same as a Kernel route in terms of metric 1
compared to 0 but it should do the trick.
|
|
|
|
|
|
|
|
This makes the actual code which generates the configs much more human
readable.
|
|
|
|
This makes the actual code which generates the configs much more human
readable.
|
|
A ip-pre-up script is better the ip-up as this is done before any addresses
have been added and any traffic flows.
|
|
VRRP: T1820: Added transition-script support for sync-groups
|
