Age | Commit message (Collapse) | Author |
|
Conflicts:
Makefile
|
|
(cherry picked from commit 4e4f1dbd745952a24d70c3e2d7dc495d675dff34)
|
|
(cherry picked from commit 6f73338f0a652ca9b68a5778456f63d098f04522)
|
|
(cherry picked from commits c043aab86d3014146a643f1c6d25edec09278873
9ff0fd30b985cc1ff8d9237158e0c110a81feccc)
|
|
(cherry picked from commit 258c24ab9be8aa4ced8bfa1c19f134ec8bbfb1a0)
|
|
(cherry picked from commit a1ed1bf1db1eb23455a3555a6fc0842104efdeb6)
|
|
(cherry picked from commit d1848a9f9447408deac451edf6392b8351ef6f64)
|
|
(cherry picked from commit d34fd745438951d55c5c4899b2b3c7bfa5d08026)
|
|
(cherry picked from commit 6b25ed2a44dde77f5cbfbf68fb4f5f661a34c1c0)
|
|
(cherry picked from commit 3aadfc1fb0e3af03a98fb908c8709e4099296821)
|
|
(cherry picked from commit fb72bc367234bf35628bdccf84b0b76108f6341e)
|
|
|
|
Poessinger et al.
|
|
- change DUID to IAID_DUID
- format IAID_DUID as colon-separated hex list
- implement functions: pool, sort, state
- add op-mode definitions for pool, sort, state
- add columns: State, Type, Last communication, Pool
- implement json output
- implement completionHelp function
|
|
* typo fixed
|
|
|
|
Commit 967067970494c1800f ("ddclient: T1030: adjust to latest syntax")
was under the impression that ddclient 3.9.0 now handles every config
item with a comma in the end. This is unfortunately not true on RFC2136
dynamic DNS entries.
Remove commas on config template.
(cherry picked from commit cc2ea329b1bb2ac23ffcc64892e831e7978023e2)
|
|
(cherry picked from commit bbb3a9ecdf2cf76b6336414928030798007dc1c7)
|
|
(cherry picked from commit 967067970494c1800f028e5a44ff2fc9e39eabb9)
|
|
(cherry picked from commit 760ac992c827734032cc41a77ba21bcc4bde50e1)
|
|
(cherry picked from commit 564c75c511c2cfd23404a500340a53441c694ffd)
|
|
(cherry picked from commit ed642ff5e958c6ef43dee5ef684fb5ccf85ad8cf)
|
|
(cherry picked from commit b86f1d702e3b67774d3a2eec1f9fa83108711798)
|
|
The SNMPv3 TSM is very complex and I know 0 users of it. Also this is untested
and I know no way how it could be tested. Instead of carrying on dead and
unused code we should favour a drop of it using a proper config migration
script.
(cherry picked from commit 556b528ef9cc1eca9d142ebe1f8f88cd02d536da)
|
|
As of the SNMP specification an SNMP engine ID should be unique per device.
To not make it more complicated for users - only use the global SNMP engine ID.
(cherry picked from commit d523111279b3a9a5266b442db5f04049a31685f7)
|
|
There was a bug when refactoring this with commits 5848a4d ("dhcp-server:
T1707: remove DHCP static-mappings from address pool") and 1182b44
("dhcp-server: T1707: bugfix on subsequent DHCP exclude addresses") that when
a static address assignemnt was using the last IP address from the specified
range.
This triggered the following error:
"DHCP range stop address x must be greater or equal to the range start
address y!"
(cherry picked from commit 735d73e162634d598aa6b8ee13197aa231eefedb)
|
|
Previously when static-mappings have been created the address was still within
the DHCP pool resulting in log entries as follows:
dhcpd: Dynamic and static leases present for 192.0.2.51
dhcpd: Remove host declaration DMZ_PC2 or remove 192.0.2.51
dhcpd: from the dynamic address pool for DMZ
|
|
|
|
Moved the code for splicing a DHCP range into its dedicated function as this
will later be required again. Having subsequent DHCP exclude addresses
e.g. 192.0.2.70 and 192.0.2.71 did not work as the previous algorithm
created a range whose start address was after the end address.
|
|
|
|
(cherry picked from commit 6a6634b02d73cc93cd7368cf2290940b57fae9c7)
|
|
(cherry picked from commit 87df87e3983e120ad171ae9dc2966309fc14fcd8)
|
|
(cherry picked from commit b04a9791226f7953cfa740804ec0d43745605f49)
|
|
|
|
|
|
|
|
Implementation by Daniil Baturin and John Estabrook.
|
|
[wireguard] T1428: correct handling of the fwmark option
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
debian/control
|
|
Netmasks (both IPv4 and IPv6) that are allowed to use the server. The default
allows access only from RFC 1918 private IP addresses. Due to the aggressive
nature of the internet these days, it is highly recommended to not open up the
recursor for the entire internet. Questions from IP addresses not listed here
are ignored and do not get an answer.
https://docs.powerdns.com/recursor/settings.html#allow-from
Imagine an ISP network with non RFC1918 IP adresses - they can't make
use of PowerDNS recursor.
As of now VyOS hat allow-from set to 0.0.0.0/0 and ::/0 which created an open
resolver. If there is no allow-from statement a config-migrator will add
the appropriate nodes to the configuration, resulting in:
service {
dns {
forwarding {
allow-from 0.0.0.0/0
allow-from ::/0
cache-size 0
ignore-hosts-file
listen-address 192.0.2.1
}
}
}
(cherry picked from commit dc0f641956d002fa8588ef8d1213791cf36e92f2)
|