Age | Commit message (Collapse) | Author |
|
|
|
Values > 30 are likely to cause login timeout, so don't allow them.
|
|
Bug 458
Add
service snmp trap-source <address>
wrapper for /etc/snmp/snmp.conf
|
|
Bug 3756
Allow setting trap communities and port values.
|
|
Postscript to bug 4499
|
|
Bug 212
The entries in config under protocols were all routing protocols
except SNMP which was an unfortunate original design choice.
Config script does migration.
|
|
Bug 4499
|
|
Want to process loopback first, so any local addresses assigned
to loopback are done.
|
|
1. Use non-expression syntax
2. Remove unused init action
|
|
All the other interface types are in vyatta-cfg-system, only
loopback and ethernet were in vyatta-cfg
|
|
Move them under user/node.tag/authorization
|
|
New syntax:
system login user vyatta authentication public-key user@remote type ssh-rsa
|
|
Also change config version for migration.
|
|
|
|
Add public key support
Convert allow-root and password-authentication from boolean nodes to
regular nodes.
|
|
First, we need to set the global IPv6 parameter under "all" when
"disable-forwarding" is deleted because this is the parameter that
actually controls whether the stack will forward IPv6 packets.
Second, if router advertisements were configured while global IPv6
forwarding was disabled, we need to re-start the daemon when global
IPv6 forwarding is re-enabled.
|
|
Now a flag file indicates that IPv6 forwarding is disabled on a specific
interface.
|
|
Part of Bug 3255
|
|
|
|
|
|
|
|
|
|
got "invalid variable reference (invalid format)"
- need extra escape magic to call vyatta-cli-expand-var.pl.
|
|
|
|
|
|
|
|
|
|
Other half of Bug 5014
|
|
|
|
|
|
|
|
|
|
|
|
Added the parameter "system ipv6 disable". If set, the module
parameter "disable_ipv6=1" will be passed to the IPv6 module. This
inhibits assignment of IPv6 addresses on any interfaces, effectively
preventing any IPv6 communication. But it leaves the IPv6 module
loaded so that applications that depend upon its existence will not
fail.
|
|
Some changes to group interface:
* don't allow vyattaop the new group used for operators
* check for allowed syntax
* add missing continuation on syntax check
|
|
Bug 4918
|
|
Enforce syntax checks on encrypted password field to prevent user errors.
But can't check salt field because it is optional and default
config.boot doesn't use one!
Bug: 4077
|
|
This reverts commit a0fe319ce069e15646077a635bc970b961124540.
|
|
Enforce syntax checks on encrypted password field to prevent user
errors.
Bug: 4077
|
|
Since kernel driver does not handle mode changes properly. Workaround
by removing slaves (and readding) before changing mode.
Bug 4758
|
|
The last change broke bond-group setup.
|
|
Use similar action to new bridge-group
Bug 4768
|
|
Use similar action to new bridge-group
Bug 4768
|
|
Unless miimon parameter is set, bonding device won't watch for
link changes (which makes it useless for any backup modes).
|
|
handled.
In order to correctly handle cases where parameters are changed after a repository
configuration has been set up, we need to do the work in an "end" field instead
of a "create" field. The "create" field is only executed when the node itself
is created, not when nodes below it are modified.
(cherry picked from commit e500a9e4494649e0ecb523d36b28452f2e9dd326)
|
|
Bug 4672
Use ip command rather than sysfs to avoid quoting issues
(cherry picked from commit 1b4902564b5a853b925d2c239c8e6a39b1734433)
|
|
bug 4694
No reason to block disabling bonding interface with VIF
Kernel handles it fine.
(cherry picked from commit 3c76bd6b12dd211075d1dd689a2772c534ec7abe)
|
|
Workaround for bonding VLAN_CHALLENGED bug 4694
(cherry picked from commit ca8bff3d63074c52cf9b532eeec3a6a4cfe76722)
|
|
(cherry picked from commit c43e9e86ea502c455dcffac10d50304d47cad8ba)
|
|
(bug 4656)
(cherry picked from commit a054f90f492653c34d8c1c6443b1b132bc9fbc22)
|