| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As bad as it can be, it seems to sort of work.
|
|
|
|
|
|
The ignore-hosts-file option did not work; because it's a boolean it didn't return any value and was always undefined when the test was done. Using $config->exists() fixes this.
|
|
This fixes the following error:
Global symbol "$ignore_hosts_file" requires explicit package name at /opt/vyatta/sbin/vyatta-dns-forwarding.pl line 77.
Global symbol "$ignore_hosts_file" requires explicit package name at /opt/vyatta/sbin/vyatta-dns-forwarding.pl line 86.
Global symbol "$ignore_hosts_file" requires explicit package name at /opt/vyatta/sbin/vyatta-dns-forwarding.pl line 99.
Execution of /opt/vyatta/sbin/vyatta-dns-forwarding.pl aborted due to compilation errors.
|
|
|
|
Bug #195: Added feature to send log message to remote syslog server over UDP or TCP.
|
|
upgrading to newer version of debian.
|
|
The init script was not running on boot because the init script
symlinks were not created in /etc/rcX.d for the runlevels: 2,3,4,5.
This fix runs the update-rc.d command in the is_amazon_ec2_ami
function, thus creating the required symlinks and also updating
/etc/init.d/.depends.on.start.
|
|
- grub.cfg is now correctly modified when installing on a VyOS AMI
- ec2-fetch-ssh-public-key init script still needs to be activated
if installing on a VyOS AMI. This is an outstanding issue which
needs to be addressed. See debian/vyatta-cfg-system.postinst.in.
|
|
See VyOS bug 196 for more information about the feature request.
|
|
See VyOS bug 195 for more information about the feature request.
|
|
- Check if installing on AWS EC2 platform via instance metadata.
- Configure GRUB correctly, so that boot messages are available
via instance's console.
- Add init.d script to fetch user's EC2 public key during boot.
|
|
|
|
|
|
Correction of a "DHCPv6Client"-related script for use with parameters only SLAAC
|
|
The "dhcpv6-options" option parameter corrected the bug which is not
reflected normally.
|
|
It seems that immediately the back of an IPv6 address will not be
normally recognized if it is not "\n" when using a DNS server with an
IPv6 address.
|
|
As we are no longer setting the ROOT_OFFSET based on disk size,
I have removed the ROOT_OFFSET variable and the set_root_fstype
function.
|
|
The current parted command does not align the root partition as desired
by the `--align optimal` option. This is evident from this parted message:
"Warning: The resulting partition is not properly aligned for best performance."
Instead of setting the ROOT_OFFSET=64S or ROOT_OFFSET=1024S (> 10GB) we should
set it to 0%. This will result in optimal alignment regardless of disk size.
Source: https://unix.stackexchange.com/a/49274
|
|
Changes are copyright 2013, Vyatta, a Brocade company.
|
|
|
|
|
|
|
|
|
|
Also remove a Vyatta occurence.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
