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
|
|
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
|
|
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
|
|
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.
|
|
See VyOS bug 195 for more information about the feature request.
|
|
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.
|
|
SNMP-135 store SNMP superuser password to config file
SNMP-130 add engineId for trap-target
SNMP-134 use 'stop' and 'start' instead of 'restart'
SNMP-141 change engineID syntax checking
SNMP-136 Users are lost after changing TSM port
SNMP-149 TLS Error: Permission denied
SNMP-147 Not correct priority in TSM users
SNMP-148 Configuring already use port for TSM is destroying users.
SNMP-151 Errors in logs after first snmp configuration
SNMP-152 Hide 'No such file or directory' error message
SNMP-153 Debug messages after 'delete service snmp'
SNMP-157 Run Perltidy for all Perl scripts
SNMP-158 change syntax of trap-target engineID
SNMP-163: added script to check name, apply it for user, group and view names
SNMP-161 Faulty configuration with many trap-target
SNMP-160 Look for TSM keys in /config folder
SNMP-162 CLI permit not correct oid
SNMP-163: typo in script
SNMP-160 Look for TSM keys in /config folder
SNMP-163: added support of upper case for names in the script
SNMP-163: create rule for names, permit only a-zA-Z0-9
SNMP-163: typo
|
|
Currently only restart rsyslog but more can be added as needed.
Fixes bug 8237.
|
|
Fixes bug 8380
|
|
|
|
logrotate needs the create config option so that it keeps the
original log file's permissions and ownership.
Fixes bug 8240
|
|
The previous implementation of log rotation used an hourly cron job to
check log file size and possibly perform a rotation. If the logging
rate is high, this interval may allow for root file system space
exhustion.
Utilizing rsyslog's outchannel mechanism enables log rotation to be
initiated as soon as the log file becomes larger than its configured
size.
Fixes Bug 7807.
|
|
Bug 7623
Patch provided by Stig.
|
|
If device disappears or is renamed between the time udev script
is run, and the vyatta-router script is run; then don't add an entry
to the config file.
|
|
Code of the form:
for $i qw(a b c)
causes the warning:
Use of qw(...) as parentheses is deprecated
|
|
1. Fix thread_per_core -- now a global variable
2. Add documentation about where still broken with offline cpus
3. Break out hamming weight function (might be used to fix #2)
Tested on UP, 4 core x 2 thread, 8 socket (virt) and Multiqueue
and single queue NIC.
|
|
Change to using sysfs to read cpu topology. This makes code more
robust and follow the standard practice of other utilities.
As an added benefit, irq-affinty now handles offline cpu's and
other cases where cpu numbers are not fully populated.
|
|
|
|
On a UP system, there is no "physical-id" in /proc/cpuinfo.
|
|
Rather than reinventing existing code, use library.
|
|
Some single-queue NICs use the multiqueue IRQ naming format
(e.g. eth0-rx-0). We need to select the CPU assignements for these
IRQs using the same algorithm that we use for single-queue NICs using
the standard naming format (e.g. eth0).
|
|
|
|
|
|
For routing and other applications it is helpful to provide some
mechanism to reserve some set of CPU's and not assign interface
IRQ's to them.
Uses environment variable VYATTA_IRQAFFINITY_BANNED_CPUS
as mechanism similar to irqbalance(8).
|
|
Multiqueue setup was broken ixgbe because of s/assign/assing/
|
|
Bug 7062
The irq's on Netxen NIC are named:
eth0[0] eth0[1] eth0[2] ...
This confuses the auto IRQ affinity script.
|
|
Bug 7032 (reprise)
Since there are various forms of multi-queue naming, it is better
to just go with the simplest pattern which is to take all the irq's
of form ethX-... and sort them.
|
|
Bug 7032
Fix matchinging of irq's named 'eth0-TxRx-0'. And change the code to
handle any form of IRQ naming of multiqueue that is eth0-xxx-0.
|
|
|
|
The mislabeled commit ddce08161907797fe914ba609b362d812e23fc8a
Fix wrong name in get_irq_affinity
Was some code to handle Broadcom device IRQ naming convention
that was untested. The part that built regex was incorrectly
expanding a string with regex characters.
|
|
|
|
Bug 6845, 6821
Need to avoid using /sys/class/net/ethX/device/irq (or /sys/bus/pci/.../irq)
because these don't handle MSI or multiqueue. This also resolves issues
with Vmware/ESX.
|
|
meant to allow any upper (or lower case) in domain name.
|
|
Bug 6845
Warn (and ignore) attempt to assign IRQ directly on multiqueuej
NIC.
|
|
Bug 6837
Xen does not behave like normal hardware. It assigns a random MAC
address (with local bit set).
|
|
Bug 6243
More complete validation of host name and domain name
|
|
Bug 6784
No point in trying to force affinity if device is offline.
|
|
Adapt to irq naming convention in 2.6.37 kernel for vmxnet3 driver.
|
|
Bug 6784
Disabled device has no IRQ, so don't change it.
|
|
The initial CPU selection function needs to take hyperthreading
into account.
|
|
(cherry picked from commit a943568e64bca73bb2951e968d0cc752d72874ab)
|
|
Bug 6663
(cherry picked from commit fa7d81f125033b7ed4bd549eb6905918612a6877)
|
|
The problem was due to incorrect initialization of the $q and $cpu
variables. Their initializations were reversed.
|