Age | Commit message (Collapse) | Author |
|
An ISC DHCP hook script is used to install the received default route into FRR
by simple calls to vtysh. By moving to frr-reload.py the DHCP default route
was deleted as it was not found in the running config.
This commit checks all interfaces if DHCP is enabled and if so - will dynamically
add the route to the generated FRR configuration.
|
|
(cherry picked from commit 01ed77040ec9493e4ca1cf868ff3c22847da4487)
|
|
To allow IPv6 only for vpn sstp sessions we have to add
'ppp-options' which can disable IPv4 allocation explicity.
Additional IPv6 ppp-options and fix template for it.
(cherry picked from commit dd036c62d1370f655a8d2075577597f24ffff7dc)
|
|
|
|
|
|
|
|
|
|
hosts: T2683: Allow multiple entries for static-host-mapping
|
|
|
|
|
|
mdns: T3917: Change to avahi-daemon for IPv4 + IPv6 mDNS repeater
|
|
|
|
ddclient: T3897: Add option for IPv6 Dynamic DNS
|
|
|
|
|
|
The hedadecimal option dhcp-cliend-identifier format is required
to set values without quotes, separated by colons.
|
|
As of NTP 4.2.7, 'nopeer' also blocks pool associations.
See https://bugs.ntp.org/show_bug.cgi?id=2657
See also https://github.com/geerlingguy/ansible-role-ntp/pull/84
(cherry picked from commit 854c68d43d8f1cf20417edd12284ea20f9e7ec9a)
|
|
|
|
|
|
|
|
|
|
|
|
Custom OpenVPN options moved back to the command line from a
configuration file. This should keep full compatibility with the
`crux` branch, and allows to avoid mistakes with parsing options
that contain `--` in the middle.
The only smart part of this - handling a `push` option. Because
of internal changes in OpenVPN, previously it did not require an
argument in the double-quotes, but after version update in
`equuleus` and `sagitta` old syntax became invalid. So, all the
`push` options are processed to add quotes. The solution is still
not complete, because if a single config line contains `push` with
other options, it will not work, but it is better than nothing.
|
|
(cherry picked from commit 8e6c48563d1612916bd7fcc665d70bfa77ec5667)
|
|
|
|
|
|
|
|
Some OpenVPN clients doesnt support option gateway and metric.
Set metric option only when 'metric' was added in config
explicity.
(cherry picked from commit 96681d8bf1ede069b573a4cbe3a2493c374d048e)
|
|
|
|
|
|
|
|
Commit 761631d6 ("vrrp: keepalived: T3847: migrate to get_config_dict()")
switched to the new python function get_config_dict(), when we deal with
tag nodes that can contain a hyphen, we should also set no_tag_node_value_mangle
in order to preserve it.
This caused a dict lookup error as the hyphens in the test scripts got replaced
by an _.
|
|
Rename virtual-address -> address as we always talk about an IP address.
|
|
|
|
|
|
Move keepalived configuration from /etc/keepalived to /run/keepalived.
|
|
This is a successor to commit a2ac9fac16e ("vyos.template: T2720: always enable
Jinja2 trim_blocks feature"). It only shifts the whitespaces / indents inside
the keepalived configuration file.
|
|
shared-network
|
|
|
|
The DHCP servers pool {} option can only be used when there follows a range
statement. This is invalid for a network with only "static" leases.
|
|
This option is mandatory and must be user configurable as it needs to match
on both sides.
|
|
|
|
|
|
DHCP servers "shared-network" level only makes sense if one can specify
configuration items that can be inherited by individual subnets. This is now
possible for name-servers and the domain-name.
set service dhcp-server shared-network-name LAN domain-name 'vyos.net'
set service dhcp-server shared-network-name LAN name-server '192.0.2.1'
|
|
IPv4 DHCP uses "dns-server" to specify one or more name-servers for a given
pool. In order to use the same CLI syntax this should be renamed to name-server,
which is already the case for DHCPv6.
|
|
vyos@vyos# show service dhcp-server
shared-network-name LAN {
subnet 10.0.0.0/24 {
default-router 10.0.0.1
dns-server 194.145.150.1
lease 88
range 0 {
start 10.0.0.100
stop 10.0.0.200
}
static-route 192.168.10.0/24 {
next-hop 10.0.0.2
}
static-route 192.168.20.0/24 {
router 10.0.0.2
}
}
}
|
|
The key defaults to 0 and will match any policies which similarly do not have
a lookup key configuration. This means that a vti0 named interface will pull in
all traffic and others will stop working. Thus we simply shift the key by one
to also support a vti0 interface.
|
|
This reverts commit 415e572dfba776a981e2ec1e4331c30cd5cb59f3.
|
|
|
|
Manually set peer id and use-x509-id are mutually exclusive!
|