summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-11-12snmpd: T1705 - High CPU usage by bgpd when snmp is activehagbard
* typo fixed
2019-11-10[HTTP API] Backport config file and image management functions.Daniil Baturin
2019-11-09ddclient: T1789: fix RFC2136 generated configChristian Poessinger
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)
2019-11-09ddclient: T1030: add cloudflare zone config entryChristian Poessinger
(cherry picked from commit bbb3a9ecdf2cf76b6336414928030798007dc1c7)
2019-11-09ddclient: T1030: adjust to latest syntaxChristian Poessinger
(cherry picked from commit 967067970494c1800f028e5a44ff2fc9e39eabb9)
2019-11-09ddclient: T1030: auto create runtime directoriesChristian Poessinger
(cherry picked from commit 760ac992c827734032cc41a77ba21bcc4bde50e1)
2019-11-09ddclient: T1030: use new default configuration file pathChristian Poessinger
(cherry picked from commit 564c75c511c2cfd23404a500340a53441c694ffd)
2019-10-28snmp: fix verify() bail out early orderChristian Poessinger
(cherry picked from commit ed642ff5e958c6ef43dee5ef684fb5ccf85ad8cf)
2019-10-27snmp: T1738: cleanup import statementsChristian Poessinger
(cherry picked from commit b86f1d702e3b67774d3a2eec1f9fa83108711798)
2019-10-27snmp: T1769: remove TSM (Transport Security Mode) supportChristian Poessinger
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)
2019-10-27snmp: T818: T1738: remove per user/trap engine idChristian Poessinger
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)
2019-10-19dhcp-server: T1745: bugfix corner case on static-assignmentsChristian Poessinger
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)
2019-10-17snmp: T1737: add missing completion helpersChristian Poessinger
(cherry picked from commit 7f9dceaa7898d6418edcdf148b52b66ccd3bd36a)
2019-10-11Jenkins: Docker: always pull container from DockerhubChristian Poessinger
(cherry picked from commit ef7c5aaecd2936d9c2f28d22aec185602dc48206)
2019-10-06T1496: use upstream accel-ppp rather then an unmaintained forkChristian Poessinger
(cherry picked from commit 41aa7bc4c804c0eba36ba6ec10b49b303e8c1df4)
2019-10-03dhcp-server: T1707: remove DHCP static-mappings from address poolChristian Poessinger
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
2019-10-03dhcp-server: only import ip_address and ip_network from ipaddress classChristian Poessinger
2019-10-03dhcp-server: T1707: bugfix on subsequent DHCP exclude addressesChristian Poessinger
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.
2019-09-28Jenkins: assume dependencies are available in Docker containerChristian Poessinger
2019-09-24Jenkins: sync with current versionChristian Poessinger
2019-09-24T1638: generated hosts file fix for proper FQDN resolutionkroy
2019-09-22Jenkins: use Dockerhub tag 'crux'Christian Poessinger
2019-09-22Jenkins: sync to current branchChristian Poessinger
Imported Jenkinsfile from commit b6c8ba61582d38c72b13c5
2019-09-04T1439: remove beginning and end anchors, they are implied with re.fullmatchJernej Jakob
(cherry picked from commit 03c09b1b0d7dfdab9fc87bc7b017455c45141ced)
2019-09-04T1439: move DUID validator to regexJernej Jakob
(cherry picked from commit 6a6634b02d73cc93cd7368cf2290940b57fae9c7)
2019-09-04T1439: add dhcpv6-client-id validatorJernej Jakob
(cherry picked from commit 87df87e3983e120ad171ae9dc2966309fc14fcd8)
2019-09-04T1439: remove quotes around dhcp6.client-idJernej Jakob
(cherry picked from commit b04a9791226f7953cfa740804ec0d43745605f49)
2019-09-04[service https] T1443: rename "server-names" option to "server-name".Daniil Baturin
2019-09-04[service https] T1443: correct the listen-address option in the script.Daniil Baturin
2019-09-04[service https] T1443: use "listen-address" option instead of "listen-addresses"Daniil Baturin
to follow the established convention.
2019-09-04Update changelog.Daniil Baturin
2019-09-04[service https] T1443: create /etc/vyos if it doesn't exist.Daniil Baturin
2019-09-04T1443: backport the HTTP API to crux.Daniil Baturin
Implementation by Daniil Baturin and John Estabrook.
2019-08-31[wireguard] T1428: Add handling of fwmark setting (#70)Matthias Fetzer
[wireguard] T1428: correct handling of the fwmark option
2019-08-31[syslog] T1530 - "set system syslog global archive file" doesn't workhagbard
2019-08-31[VRRP] T1362: quote VRRP password strings to avoid config parse errors.Daniil Baturin
2019-08-30T1598: fix vyos-hostsd unit dependencies.Daniil Baturin
2019-08-29T1598: import the static-host-mappings CLI from current.Daniil Baturin
2019-08-29T1598: import the new host_name.py from current.Daniil Baturin
2019-08-29T1598: fix the debian/rules to get vyos-hostsd installed.Daniil Baturin
2019-08-27T1598: make dns_forwarding.py retrieve name servers from vyos-hostsd.Daniil Baturin
2019-08-27T1598: add a vyos-hostsd operation for retrieving name servers by tag.Daniil Baturin
2019-08-27T1606: change vyos-hostsd systemd target to avoid boot problemsJohn Estabrook
2019-08-27T1598: clean up vyos-hostsd state dump on clean shutdown.Daniil Baturin
2019-08-27T1598: improve autogenerated file comments.Daniil Baturin
2019-08-27T1598: handle the socket timeout exception in vyos.hostsd_clientDaniil Baturin
2019-08-27T1598: start vyos-hostsd before everything that may need it.Daniil Baturin
2019-08-27T1598: initial implementation of the hosts keeper daemon.Daniil Baturin
Conflicts: debian/control
2019-08-25powerdns: T1524: support setting allow-from networkChristian Poessinger
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)
2019-08-13Merge pull request #101 from DmitriyEshenko/patch-6Daniil Baturin
[show arp] T1576 deleting improper quotes
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-04 10:12:15 +0000