| Age | Commit message (Collapse) | Author |
|---|
|
in the DHCPv6 client script instead of fetching them from the config.
|
|
|
|
|
|
Tighten the checks for configured search domains to exclude adding
unnecessary blank domains and expand the comments added to
/etc/resolv.conf to indicate the source of the search domains.
Bug #486 http://bugzilla.vyos.net/show_bug.cgi?id=486
|
|
Following the documentation, /etc/resolv.conf should only have comments
inserted that start with # at the beginning of a line, comments in
other locations are not supported. The exisiting method of tracking
changes in this file (done by both vyatta-system-nameservers and
vyatta_update_resolv.pl) relies on this unsupported feature.
This commit restructures the updates so they use comments on the
preceding line to track changes, along with updating the old style
comments to the new ones when the relevant scripts are called.
This also fixes a previous issue (which was reverted) where IPv6
nameservers worked incorrectly when the /etc/resolv.conf line ended
with a comment.
Bug #486 http://bugzilla.vyos.net/show_bug.cgi?id=486
|
|
When configuring DNS fowarding, allow multiple servers to be specified
when setting domain overrides, in order to allow Dnsmasq to gracefully
handle unavailable nameservers.
Bug #408 http://bugzilla.vyos.net/show_bug.cgi?id=408
|
|
The resolv.conf file contains comments at the end of the search and
domain entries which cause unexpected behaviour on lookups. Moving
these to the line above in each case fixes the issue.
Bug #468 http://bugzilla.vyos.net/show_bug.cgi?id=468
|
|
Add a couple of configuration options to DDNS, to allow the use=web
option from ddclient when determining the external IP address. This
will allow DDNS to be correctly updated when behind a NAT device.
Syntax:
set service dns dynamic interface eth0 use-web url (url to use)
set service dns dynamic interface eth0 use-web skip (search for this)
Bug #455 http://bugzilla.vyos.net/show_bug.cgi?id=455
|
|
Update the update_inittab function so when the system is configured for
Xen console (hvc0) access, the correct values are written out to
/etc/inittab.
|
|
Update scripts/system/vyatta_update_console.pl to have consistent
identation levels and style throughout.
|
|
Add support for using the afraid.org dynamic DNS service with VyOS.
This requires the updated ddclient package built for VyOS to work
correctly as the version currently in squeeze lacks support for the
freedns protocol.
Bug #287 http://bugzilla.vyos.net/show_bug.cgi?id=287
|
|
Update scripts/dynamic-dns/vyatta-dynamic-dns.pl to have consistent
identation levels and style throughout.
|
|
|
|
|
|
EdgeOS does this as well, not sure if VyOS should; feel free to ignore this PR if you feel otherwise. I'm setting up LibreNMS' detection of VyOS to allow for both.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The password reset option only allows resetting the password for the
default admin (vyos) user. This now allows the user to be specified
for the password reset, defaulting to the 'vyos' user with a password
of 'vyos'.
Bug #342 http://bugzilla.vyos.net/show_bug.cgi?id=342
|
|
In line with Bug #318, set the default vyos user password hash to use
SHA-512 instead of MD5 when recreating the user during a password reset
Bug #355 http://bugzilla.vyos.net/show_bug.cgi?id=355
|
|
Add the default plaintext-password entry to the default vyos user
created during password reset.
Bug #342 http://bugzilla.vyos.net/show_bug.cgi?id=342
|
|
If you delete the vyos user from the system and then go into password
reset mode on reboot, the configuration entry for the vyos user is
recreated but the command returns 'usermod: user 'vyos' does not exist'.
Despite this message the user is created correctly on a full reboot,
just not at the point the command is run.
Bug #342 http://bugzilla.vyos.net/show_bug.cgi?id=342
|
|
Allow interfaces with either dhcp or dhcpv6 addresses to be deleted.
Expand on the previous patch for Bug #305 to now take dhcpv6 addresses
into account, as well as an update to the original dhcp logic.
Bug #341 http://bugzilla.vyos.net/show_bug.cgi?id=341
|
|
|
|
|
|
Minor cleanup.
|
|
|
|
do AWS-specific things.
|
|
Rename allow-dhcp-nameservers to disable-dhcp-nameservers and update
the logic to take the new meaning into account. The option is now also
typeless, so the node is either absent (default) or present (enabled).
Format 'set / delete system disable-dhcp-nameservers'
Linked to Bug #182 and Bug #308
Bug #314 http://bugzilla.vyos.net/show_bug.cgi?id=314
|
|
Expand the logic in 'set system allow-dhcp-nameservers', so that in
addition to either allowing / denying DHCP related updates to
resolv.conf when the interface changes state, it will also either
add or remove the currently supplied DHCP name-servers depending on
it's state. This change in name-servers will take place immediately
on commit.
Bug #309 http://bugzilla.vyos.net/show_bug.cgi?id=309
|
|
Update scripts/vyatta-system-nameservers to have consistent identation
levels and style throughout.
|
|
'remote-ip' is nowt set.
|
|
Instead of simply allowing / denying DHCP related updates to resolv.conf
based on the current values of 'set system name-server', as initially
proposed for Bug #182 (http://bugzilla.vyos.net/show_bug.cgi?id=182),
this patch replaces that behaviour with a global option to allow /
deny these updates.
Add 'set system allow-dhcp-nameservers' as a boolean value that has the
default value of true, so allowing DHCP nameserver updates by default.
Bug #308 http://bugzilla.vyos.net/show_bug.cgi?id=308
|
|
Reverting commit bb71cf5b7b3a48812e28dbefba8c535f9bbf9973 as it breaks
the logic in vyatta_update_resolv.pl for removing name servers when
called by dhclient-script. As it stands, the commit causes name server
entries to be left behind in resolv.conf when a DHCP interface is
deleted, resulting in possibly old or invalid entries remaining
indefinitely.
Bug #307 http://bugzilla.vyos.net/show_bug.cgi?id=307
|
|
Update scripts/system/vyatta_update_resolv.pl to have consistent
identation levels and style throughout.
|
|
When DNS settings are statically configured, prevent DHCP interfaces
from appending to resolv.conf with additional name servers. If the
system has been configured with a static name server, just use that
instead of accepting ISP provided name servers. These can be accepted
again by simply deleting the statically configured name servers.
Bug #182 http://bugzilla.vyos.net/show_bug.cgi?id=182
|
|
Update scripts/system/vyatta_update_resolv.pl to have consistent
identation levels and style throughout.
|
|
Update the checks in scripts/vyatta-address to allow the deletetion of
an interface that has a DHCP address. The patch put in place for
Bug #259 (http://bugzilla.vyos.net/show_bug.cgi?id=259) checks that an
interface exists before preceding with the delete, but this chokes when
supplied with the address 'dhcp'.
This patch checks if the supplied interface is a DHCP address, before
extracting the IP address and then using that address for the check.
Bug #305 http://bugzilla.vyos.net/show_bug.cgi?id=305
|
|
Update scripts/vyatta-address to have consistent identation levels and
style throughout.
|
|
When the values for SysContact, SysLocation and SysDecr are written to
the snmpd.conf file, they are enclosed in backslash escaped quotes.
This isn't part of the syntax for snmpd.conf and looks wrong / could
break snmp related things, the example snmpd.conf files show these
values as unquoted.
This patch corrects the output and adds validation for the supplied
values, limiting them to a maximum of 255 printable characters
(RFC 3418).
The documentation also needs amending to take this into account.
Bug #261 http://bugzilla.vyos.net/show_bug.cgi?id=261
|
|
|
|
|
|
|
|
|
|
|
|
|
