Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

usernetctl(8) [redhat man page]

USERNETCTL(8)						      System Manager's Manual						     USERNETCTL(8)

NAME
usernetctl - allow a user to manipulate a network interface if permitted SYNOPSIS
usernetctl interface-name up|down|report DESCRIPTION
usernetctl checks to see if users are allowed to manipulate the network interface specified by interface-name, and then tries to bring the network interface up or down, if up or down was specified on the command line, or returns true or false status (respectively) if the report option was specified. usernetctl is not really meant to be called directly by users, though it currently works fine that way. It is used as a wrapper by the ifup and ifdown scripts, so that users can do exactly the same thing as root: ifup interface-name ifdown interface-name and ifup and ifdown will call usernetctl automatically to allow the interface status change. OPTIONS
interface-name The name of the network interface to check; for example, "ppp0". For backwards compatibility, "ifcfg-ppp0" and "/etc/sysconfig/net- work-scripts/ifcfg-ppp0" are also supported. up|down Attempt to bring the interface up or down. report Report on whether users can bring the interface up or down. NOTES
Alternate device configurations may inherit the default configuration's permissions. RHS
Red Hat, Inc. USERNETCTL(8)

Check Out this Related Man Page

IFCFG-BONDING(5)					       Network configuration						  IFCFG-BONDING(5)

NAME
ifcfg-bonding - interface bonding configuration SYNOPSIS
/etc/sysconfig/network/ifcfg-bond* Bonding Interfaces To setup a bonding interface you need a configuration file ifcfg-bond<X> with the usual network settings. But you must add additional vari- ables BONDING_MASTER must be set to 'yes' to identify this interface as a bonding interface BONDING_SLAVE_<X> here you specify the interface name representing the slave network interfaces. BONDING_MODULE_OPTS contains bonding options. Here you can set interface timeouts or working modes ('mode=active-backup' for backup mode). For addi- tional information take a look into the documentation mentioned at the bottom. Note, that this options are not passed as parameters to the bonding kernel module any more, but set via sysfs interface. This variable will be renamed in the feature. BONDING_SKIP_REMOVE_WORKAROUND When set to "yes", a bonding interface will be not removed while ifdown any more to avoid problems, e.g. when some third party ker- nel module, such as Veritas 'llt' module, does not react correctly to the UNREGISTER event and does not remove its references to the bonding interface causing all network related operation to stuck. Note: the bonding options are not reverted when this option is enabled and it is required to either explicitly keep the old options and set them to their default setting on bonding configuration changes or to reboot. Example Example for a bonding interface on eth0 and eth1 using the backup mode ifcfg-bond0 STARTMODE='onboot' BOOTPROTO='static' IPADDR='192.168.0.1/24' BONDING_MASTER='yes' BONDING_SLAVE_0='eth0' BONDING_SLAVE_1='eth1' BONDING_MODULE_OPTS='mode=active-backup miimon=100' Additional Information For additional and more general information take a look into /usr/src/linux/Documentation/networking/bonding.txt. Maybe you need to install the kernel sources to get this additional documentation. The configuration of routes for this kind of interface does not differ from ordinary interfaces. See man routes for details. BUGS
Please report bugs at <http://www.suse.de/feedback> AUTHOR
Christian Zoz <zoz@suse.de> -- ifup script Wilken Gottwalt <wgottwalt@suse.de> -- ifcfg-bonding manual page SEE ALSO
ifcfg(5), ifup(8). sysconfig April 2005 IFCFG-BONDING(5)
Man Page