Age | Commit message (Collapse) | Author |
|
Use common method for formatting CLI style help when
entering interface name.
Move loopback name syntax check into CLI expression to
avoid overhead of perl here.
|
|
Per current policy remove verb from all help messages in th is package
|
|
Since brctl has cap_net_admin, don't need to use sudo
|
|
No longer need sudo on ip because of cap_net_admin
|
|
Use same format/syntax over all interface types.
Bug 5257
|
|
* fix this for eth, eth.vif, bond, bond.vif interfaces
* also, bridge-group code for bonding interfaces wasn't changed
with commit ec080f99 that re-strucutred bridging code in eth and
eth.vifs to fix bug 4708. bridge-group code for bond and bond.vif
interfaces is now similar to the fix for 4708
|
|
|
|
|
|
|
|
|
|
Eventually, need to be able to devices named something other
than 'ethX' into bridge. So use sysfs to find devices.
|
|
The CLI should not be enforcing arbitrary restrictions on the number of
devices. The limit should be based on the resources of the system and
only the kernel would know that. So let the user try and make 10000
bridge devices, maybe its on a 2000 core machine with 64G of memory.
Any failure will show up when the attempt is made to create the tunnel
device.
|
|
|
|
Conflicts:
templates/interfaces/bridge/node.def
templates/interfaces/ethernet/node.tag/bridge-group/node.def
|
|
|
|
- help strings standardized in vyatta-cfg-system
|
|
|
|
|
|
|