| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
within a single set of deactivated commands. only preserves
the parent deactivated node in this case.
|
|
remove these comments from the comments in the action configuration the user should:
1) save their current configuration
2) run this script on the saved configuration
3) reload their configuration (which will strip the migration comments from the active configuration tree)
|
|
and is active in loaded configuration.
|
|
configuration of disable nodes. requires vyatta-config-migrate package as well.
Additional fix required for loading configuration with deactivated nodes that are activated through the loading process.
|
|
feedback.
|
|
* use "enumeration" template field for both CLI completion and GUI2
enumeration support.
* CLI completion now uses enumeration if it exists.
* add "existing-interfaces" script as an example.
|
|
/* to create a comment */
> comment [PATH-TO-NODE] "my comments"
/* to delete a comment */
> comment [PATH-TO-NODE] ""
|
|
has already been deactivated.
|
|
2) remove priority from node.def when priority value is 0 in priority file;
3) copy over comment and empty lines in the beginning of node.def
|
|
|
|
supported.
|
|
|
|
end
|
|
each node.def according to the inputs.
|
|
priority: PARENT
Means that this priority group will adopt the priority value of the parent. And the behavior on deletion of this priority root node will be deleted before the parent. On
all other operations this node will be scheduled after the parent.
This should fix problems in scheduling creation/deletion orders for priority groups so long as they are located within the same hierarchy.
priority.pl has been updated as well.
|
|
|
|
|
|
Also sort the names when multiple values have same priority.
|
|
Use perl library rather than external find/grep. Cleaner and
more efficient.
|
|
All the other templates and scripts related to interfaces
are in vyatta-cfg-system
|
|
This fixes Bug 3917 by checking for interface current state rather
than configuration state.
Also changed variable names and command arguments to improve clarity.
Instead of --op_command="dhcp-renew" use "--dhcp renew".
|
|
|
|
|
|
Also change priority.pl script to display inline comments found in
"priority:" fields if they are present.
|
|
By calling fsync, we can be more assured that file actually makes
it to disk.
|
|
Previously the script determined the driver that a NIC was using, then
used that to parse the queue names from /proc/interrupts. Now, it
determines the naming convention just by looking at the queue names.
Now the script should work for all NICs that support one of the two
standard naming conventions.
Also added some support for single-queue NICs.
|
|
|
|
|
|
vyatta config token at end of file. this will prevent the
accidental overwrite of non vyatta config files. check on prevent existing files that don't contain ' === vyatta-config-version:'
from being saved to.
|
|
This change implements a mechanism for setting the IRQ affinity of NIC
interrupts in a way that is optimally balanced. The affinity settings
are static, and are set up at configuration time. I've added "auto"
as a new legal value to the "interfaces ethernet ethX smp_affinity"
configuration parameter. If this value is set, then the system
attempts to perform automatic IRQ affinity assignment.
At this time, automatic IRQ affinity is supported only for multiqueue
NICs that use the igb or bnx2 drivers. Even with these two,
differences in the organization of queues and their naming convention
necessitate some NIC-specific code. The assignment strategy attempts
to assign all queues of all NICs that share the same queue number to
the same CPU. This has been shown to be optimal for IP forwarding
workloads in 2.6.31 kernels.
Setting the value to "auto" for NICs that use other drivers will be a
no-op.
|
|
Also restore "--valid-addr" flag to vyatta-interfaces.pl since it is used outside
this package.
|
|
Changed the the set-time and commit-time check of ethernet interface address
values. These checks need to prevent configuring both DHCP and static
IPv4 addresses on the same interfac. The previous checks were comparing
against the running configuration tree, not the proposed config tree. Now
the set-time check is purely a syntax check, and the commit-time check
only checks for both DHCP and static IPv4 addresses in the proposed config.
The system now allows DHCP and static IPv6 addresses to be configured on
the same interface.
|
|
The script was hiding any error exit codes from 'ip' command.
Switch to using exec so that error exits fail the commit.
Discovered when testing with IPV6 disabled.
|
|
This does the same thing as vyatta-quagga-utils.pl --exists, but
it is generally useful (outside quagga) and has less overhead than
a perl compile.
|
|
|
|
|
|
|
|
|
|
(cherry picked from commit abc33133b79759a629b14b81e6a65eed0fa23e8a)
|
|
|
|
|
|
|
|
|
|
Move the speed/duplex setting into script where we can handle errors
better, and avoid setting speed/duplex twice.
(cherry picked from commit 330470f1f060f579434eb89469f4ed021c95449d)
|
|
The "check" sub-command is called by the CLI at "set" time. The interface
may not be configured, or may be configured but not "up" at this time.
So we don't want to perform any validation on the interface.
|
|
|
|
Better than reading sysfs directly.
|
|
|
