Age | Commit message (Collapse) | Author |
|
|
|
Add the additional services that are supported by ddclient to the list
of service defaults. Also add a function to use this list to check for
the allowed protocols, and update the protocol node to use this.
Bug #507 http://bugzilla.vyos.net/show_bug.cgi?id=507
|
|
|
|
Update the default protocol used for the dslreports service in the
revised dynamic DNS system and remove the default server settings for
freedns as it's already defined in ddclient. Uodate the wording in the
server node to indicate it's only needed for custom services.
Bug #507 http://bugzilla.vyos.net/show_bug.cgi?id=507
|
|
compatibility (#507)
|
|
When the system is installed in a raid configuration, grub is installed
to the raid device instead of to the individual slave drives, resulting
in a failure to boot after installation. This commit identifies the
slave drives and ensures grub is installed to all of them (rather than
just the primary), resulting in a system that will boot following a
primary drive failure.
Bug #106 http://bugzilla.vyos.net/show_bug.cgi?id=106
|
|
Skip over either invalid ntp servers, or ntp server hostnames that have
failed to resolve correctly, and continue to process the rest of the
configuration.
Bug #94 http://bugzilla.vyos.net/show_bug.cgi?id=94
|
|
Update the new NTP updating routines so they operate outside of
configuration mode (dhcp triggered updates). This also requires
changes to the vyatta-dhcp3 package (see Bug #500)
Bug #94 http://bugzilla.vyos.net/show_bug.cgi?id=94
|
|
Bug #94 http://bugzilla.vyos.net/show_bug.cgi?id=94
|
|
When NTP is configured on the system, it not only acts as a client
for the configured servers, but also as a server. Although the server
is only available as a time source, it still represents a service that
the user hasn't specifically enabled.
This commit sets the default configuration of NTP to disallow all
external access, so the system acts purely as a client by default, and
also introduces the ability to configure which addresses / subnets are
allowed to both query and use it as a time source. If the servers
configured are specified as host names, these are resolved to IP
addresses before being added to ntp.conf, with the same process carried
out after name server changes.
syntax 'set system ntp client address'
Bug #94 http://bugzilla.vyos.net/show_bug.cgi?id=94
|
|
users.
|
|
|
|
Bug #389: Add RFC2136 configuration options for ddclient 3.8.2
|
|
|
|
DHCPv6 options to be configured at the same time.
|
|
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.
|