summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
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-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-24T1638: generated hosts file fix for proper FQDN resolutionkroy
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: 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 new host_name.py from current.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: 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-07-25T1541 Fix: adding additional checkEshenko Dmitriy
(cherry picked from commit 3945b2259aaa64eb9f4d61334126235f2d641293)
2019-07-23[wireguard] T1425 - assign a /31 address on Wireguard interfacehagbard
- added a validator for checking if the address is any cidr noted address (cherry picked from commit 2ee0eff1bd04ef02b0769341eee22543f8011b68)
2019-07-21[dns-forwarding] T1333: handle domain forward and general recursion in one ↵Christian Poessinger
configuration line In the past we used the PowerDNS cofniguration option forward-zones and forward-zones-recurse, but only the latter one sets the recursion bit in the DNS query. Thus all recursions have been moved to this config statement. (cherry picked from commit 5886dd27cbc65f8cda04752bbd39a960b0887523)
2019-07-19T1440: in IPv4 DHCP, print the subnet rather than a dict dumpDaniil Baturin
when a non-unique subnet is found.
2019-07-16T1531: do not include FQDN in the hostname.Daniil Baturin
2019-07-12Do not try to verify the config when host_name.py is called from dhclient ↵Daniil Baturin
script.
2019-07-11[wireguard] - T1516: changing committed config causes errorhagbard
2019-07-09T1497: remove duplicate values from name servers and search domains obtained ↵Daniil Baturin
from DHCP.
2019-07-08Fix a stray debug print in vyos-config-file-query.Daniil Baturin
2019-07-04Merge branch 'crux' of https://github.com/vyos/vyos-1x into cruxDaniil Baturin
2019-07-04T1497: make host_name.py wait for commit lock too.Daniil Baturin
2019-07-04T1497: remove the no longer necessary workaround for bad ↵Daniil Baturin
return_effective_values output.
2019-07-03Merge pull request #76 from qiuchengxuan/cruxChristian Poessinger
[pdns-recursor] T1469 - replace forward-zones with forward-zones-recurse
2019-07-03T1504: wait for commit lock before trying to update resolv.conf in the out ↵Daniil Baturin
of CLI mode.
2019-07-02T1497: "set system name-server" generates invalid/incorrect resolv.confUnicronNL
2019-06-25[pdns-recursor] T1469 - replace forward-zones with forward-zones-recurseqiuchengxuan
forward-zones-recurse behaves identically to dnsmasq server option in legacy vyos 1.1.8, while forward-zones option disallow recursive name resolving, which leads to dns lookup failure
2019-06-22DHCPDv6 T1433: rename daemon configuration fileChristian Poessinger
... to have the same pattern as the DHCPDv6 lease file (cherry picked from commit adaa9b78e2fb0c7da58ca6c09934b3e3cff44795)
2019-06-22DHCPDv6 T1433: fix wrong lease file nameChristian Poessinger
A wrong lease file caused the show command to fail: vyos@vyos:~$ show dhcpv6 server leases Traceback (most recent call last): File "/usr/libexec/vyos/op_mode/show_dhcpv6.py", line 81, in <module> leases = get_leases(lease_file, state='active') File "/usr/libexec/vyos/op_mode/show_dhcpv6.py", line 44, in get_leases leases = IscDhcpLeases(lease_file).get() File "/usr/lib/python3/dist-packages/isc_dhcp_leases/iscdhcpleases.py", line 110, in get with open(self.filename) as lease_file: FileNotFoundError: [Errno 2] No such file or directory: '/config/dhcpdv6.leases' (cherry picked from commit 3b9bfe322fd4a7d652b25b28cbcd4825fee0ea4b)
2019-06-22T1433: fix also filenames in /etc/default/isc-dhcpv6-serverJernej Jakob
(cherry picked from commit 690ae8bf526b6d45997bedf5e856f858ad251658)
2019-06-20firewall: T1461: deleting 'firewall options' causes Python TypeErrorChristian Poessinger
[ firewall options interface wg01 ] Traceback (most recent call last): File "/usr/libexec/vyos/conf_mode/firewall_options.py", line 139, in <module> apply(c) File "/usr/libexec/vyos/conf_mode/firewall_options.py", line 97, in apply if tcp['new_chain4']: TypeError: 'NoneType' object is not subscriptable delete [ firewall options ] failed delete [ firewall ] failed Commit failed (cherry picked from commit efb1a1c88f436a3704c4ca6e15b65aeded4b9654)