vyos-1x.git/src/migration-scripts, branch vyos/1.2.6VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=vyos%2F1.2.62020-04-04T22:10:02+00:00bgp: T2100: migration to drop parameter disable-network-import-check2020-04-04T22:10:02+00:00John Estabrookjestabro@vyos.io2020-04-02T19:35:00+00:00urn:sha1:46d13b903be47454f22990c12cb0bb3d64e13a47
(cherry picked from commit 393dabe6f1ba9b298864a9ef6f7ea5592170f57c)
[BGP] T1490: Backport migration for obsoleted 'bgp scan-time' parameter2020-04-04T21:42:38+00:00John Estabrookjestabro@vyos.io2020-04-04T21:42:38+00:00urn:sha1:b320583b38ce2bd46c9f2423d463b9fbe77441a7T1967: add a migration script for the enforce-first-as option.2020-03-09T13:09:06+00:00Daniil Baturindaniil@baturin.org2020-03-09T13:09:06+00:00urn:sha1:6b4fb1820e740e6c7d63d7aba94fb2e0c7f5ededmigration-scripts: l2tp: T1811: add missing check on server existence2019-11-18T20:16:41+00:00Eshenko Dmitriysnooppy@mail.ua2019-11-18T20:15:08+00:00urn:sha1:af168aa1cceb420350955b62f5ae31e05978e5c1
(cherry picked from commit fb72bc367234bf35628bdccf84b0b76108f6341e)
snmp: T1769: remove TSM (Transport Security Mode) support2019-10-27T22:59:19+00:00Christian Poessingerchristian@poessinger.com2019-10-27T03:23:13+00:00urn:sha1:c9b892349bac27fad9e2336e2020c589759598a1
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)
snmp: T818: T1738: remove per user/trap engine id2019-10-27T22:58:32+00:00Christian Poessingerchristian@poessinger.com2019-10-26T22:47:50+00:00urn:sha1:4a077bd3f8e12eb7550f7f9bce1394646eb13a25
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)
powerdns: T1524: support setting allow-from network2019-08-25T17:19:20+00:00Christian Poessingerchristian@poessinger.com2019-08-20T09:50:55+00:00urn:sha1:8c471a772153ae7dc6d3b934c5a96706bc9a6ba5
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)
[dhcp-server]: bugfix on wrong exit code caused due to wrong indention2019-04-26T08:46:45+00:00Christian Poessingerchristian@poessinger.com2019-04-26T08:45:20+00:00urn:sha1:006d77eac795acfbe28dbdb73cd08249ca0e5fc7
(cherry picked from commit d46523b92a2e5959da66973343092c819fea6285)
[dhcp-server] T1335: bugfix when migrating authoritative section2019-04-20T14:49:25+00:00Christian Poessingerchristian@poessinger.com2019-04-20T14:25:36+00:00urn:sha1:afbd14c8a97984f7b1385ee6eaff08a7e2264956
(cherry picked from commit f8b7e3b2b20d143643bfac72db68943dfc9046f1)
Merge branch 'current' into crux2019-01-26T22:10:00+00:00Daniil Baturindaniil@baturin.org2019-01-26T22:10:00+00:00urn:sha1:97186852f529935309c009e38403cead2bf0ce75