When is 'ifup' really done?


 
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
IFSERVICES(5)						       Network configuration						     IFSERVICES(5)

NAME
ifservices-* - control network services with ifup/down SYNOPSIS
/etc/sysconfig/network/ifservices-<configuration_name>/ DESCRIPTION
The directory /etc/sysconfig/network/ifservices-<configuration_name>/ is read by the script /etc/sysconfig/network/scripts/ifup-services which starts and stops system services when an interface is set up/down. ifup-services is used by /sbin/ifup, which is the command line user interface for setting up network interfaces. This is useful if you don't have a permanent network connection. If you sometimes boot without network and plug in the network cable later you can add links to system services in this directory. These services will then be started with ifup and stopped with ifdown. The configuration name used for ifservices-* should match exactly the configuration name of the ifcfg-* file for the interface. For the usage with NetworkManager (where you don't necessarily need a ifcfg-* file) you can also use /etc/sysconfig/network/ifser- vices-<interface>-<essid>/ (for wlan interfaces) or if that does not exist /etc/sysconfig/network/ifservices-<interface>/. As a final fallback /etc/sysconfig/network/ifservices/ is checked as well. If NetworkManager is active services will be stopped after the interface is down. The links in this directory are equal to the links in the runlevel directories /etc/init.d/rc*.d/ They have to point to service start scripts which are usually in /etc/init.d/. Links starting with 'S' are start links, which are called in alphabetical order after ifup has set up the interface. Links starting with 'K' are kill links which are called before ifdown takes down the interface. See also section Sequencing Directories in boot (7). EXAMPLE
In this example we use an interface with MAC address 00:de:ad:be:af:00. This interface is not always physically connected. As soon as you plug in the cable ypbind and autofs should be started. When you pull the cable they should be stopped. This can be reached with: in file /etc/sysconfig/network/ifcfg-eth-id-00:de:ad:be:af:00 ... STARTMODE=ifplugd ... in dir /etc/sysconfig/network/ifservices-eth-id-00:de:ad:be:af:00/ S10portmap -> /etc/init.d/portmap S20ypbind -> /etc/init.d/ypbind S30autofs -> /etc/init.d/autofs S20autofs -> /etc/init.d/autofs K30ypbind -> /etc/init.d/ypbind Now you have to disable the start of this services at boot time chkconfig ypbind off chkconfig autofs off Notes: You may call scripts/create-ifservices-directory [<interface_name>] to create a directory with the links from this example. This will cre- ate the directory ifservices-<interface_name> or if no interface name was given ifservices-template. Maybe you have to add also variable IFPLUGD_PRIORITY. For details about startmode ifplugd read ifup (8). The service portmap had to be added because ypbind needs it. This service is still started at boot time because it does not need an active network connection. But ypbind may now be started earlier as usual. Therefore we make sure that portmap is started before. Starting an already running service again does not affect the service. SEE ALSO
ifup(8), ifcfg(5). AUTHOR
Christian Zoz <zoz@suse.de> sysconfig February 2005 IFSERVICES(5)