Age | Commit message (Collapse) | Author |
|
|
|
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
|
|
|
|
Adjusting the mtu node prority from 381 to 382 so child interfaces
set their MTU after the parent interface. This was reported for
multiple vifs when setting the MTU to 9000 for jumbo frames, although
it only exhibited it when more than one vif was configured.
Bug #473 http://bugzilla.vyos.net/show_bug.cgi?id=473
|
|
|
|
|
|
|
|
If radvd is not running, the pgrep command returns an empty string, not zero.
Reported-by Carl Byington <vyos-bug@five-ten-sg.com>
|
|
|
|
|
|
|
|
users.
|
|
|
|
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
|
|
This reverts commit 733259a85b0791b9779e4a03fa65158770c48637.
|
|
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
|
|
|
|
|
|
DHCPv6 options to be configured at the same time.
|
|
Seems to work with 319.
|
|
in the DHCPv6 client script instead of fetching them from the config.
|
|
|
|
Adding support for spaces in the key comment field. Bug 411
|
|
|
|
Bug #381: fix for unusable "link" option
|
|
In the inital state, the "link" option was not usable,
so I moved the "link" directory under "node.tag".
Aftewards, the "link" option became usable.
|
|
|
|
|
|
Remove the comment from the plaintext-password node regarding empty
encrypted password values as you can't set them as empty.
|
|
You can't create a user without a password, but once this user is
created, you can then delete the encrypted password. However, deleting
the encrypted password from the config doesn't actually remove the
password on the system and in addition breaks the config on reboot,
resulting in the system login node being entirely absent.
This fix ensures that the encrypted password is set to "!" when the
config node is deleted, removing the password login capability for this
account but still allowing SSH RSA key login.
Bug #336 http://bugzilla.vyos.net/show_bug.cgi?id=336
|
|
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
|
|
|
|
vyatta-cfg-system: allow dhcp and dhcpv6 addresses to be deleted
|
|
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.
|