Login or Register to Ask a Question and Join Our Community


UNIX for Advanced & Expert Users

When is 'ifup' really done?

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users When is 'ifup' really done?
# 1  
Old 05-03-2008
When is 'ifup' really done?
I have been looking in the scripts for interface management, in an effort to kick off a script of my own on any "significant network event" (I will qualify that in a bit)

I managed to add a check to tell netplugd to run my script every time there is a hot-plug event. Now I need to make it so my script is also kicked off on a 'service network restart' or simply an 'ifup ethX'... which seemed doable to me...

Looking in the ifup script, I saw the ifup-eth script get kicked off, from there, the ifup-post script, to the ifup-local script (which doesn't exist, so isn't run)... stupid me, I made the assumption that "post" meant "after", and instead of seeing my script run, I see messages like "arping: recvfrom: Network is down" (arping is being called from my script)

btw - the first exec of my script happens *after* the interfaces are raised, but only because I do it via the boot-order rc3.d script-list

Any idea how I can make my script *actually* kick off after the interface is *actually* up?
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Red Hat

Dual NICs - When I 'ifup eth1' it replaces eth0

I've got an issue with a VMWare server running RHEL 6.3 that has dual E1000 NICs. I have configured the cards as I would normally do in /etc/sysconfig/network-scripts as ifcfg-eth0 and ifcfg-eth1. I can execute ifup eth0 and bring the interface up quite happily, however when I execute ifup eth1 it... (2 Replies)
Discussion started by: phaedrus
2 Replies

2. Red Hat

ifconfig , ifdown, ifup

hi there the ethernet wire was out of the pc when the system started. #ifconfig #ifconfig -a i did not get any ip for eth0. i plug the cable into the pc #ifdown eth0 #ifup eth0 now the ip address is assigned to eth0 Question is : IS this right way to bring ethernet down... (2 Replies)
Discussion started by: dplinux
2 Replies

3. Shell Programming and Scripting

log in ifup

I have a little script in the /etc/network/if-up.d (debian). It should do something and write the output to a log file. But it doesn't seem to work. ifup wlan0 dosomething >> /var/log/dosomething.log I would like to add the date to the output, can somebody help me please? Thanks! (6 Replies)
Discussion started by: borobudur
6 Replies
Login or Register to Ask a Question

LEARN ABOUT SUSE

ifcfg-bonding

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)