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
ifup(8) 																   ifup(8)

NAME
ifup - bring a network interface up ifdown - take a network interface down SYNOPSIS
ifup [-nv] [--no-act] [--verbose] [-i FILE|--interfaces=FILE] [--allow CLASS] -a|IFACE... ifup -h|--help ifup -V|--version ifdown [-nv] [--no-act] [--verbose] [-i FILE|--interfaces=FILE] [--allow CLASS] -a|IFACE... DESCRIPTION
The ifup and ifdown commands may be used to configure (or, respectively, deconfigure) network interfaces based on interface definitions in the file /etc/network/interfaces. OPTIONS
A summary of options is included below. -a, --all If given to ifup, affect all interfaces marked auto. Interfaces are brought up in the order in which they are defined in /etc/net- work/interfaces. If given to ifdown, affect all defined interfaces. Interfaces are brought down in the order in which they are currently listed in the state file. Only interfaces defined in /etc/network/interfaces will be brought down. --force Force configuration or deconfiguration of the interface. -h, --help Show summary of options. --allow=CLASS Only allow interfaces listed in an allow-CLASS line in /etc/network/interfaces to be acted upon. -i FILE, --interfaces=FILE Read interface definitions from FILE instead of from /etc/network/interfaces. -e PATTERN, --exclude=PATTERN Exclude interfaces from the list of interfaces to operate on by the PATTERN. Notice that the PATTERN can be a full interface name or substrings that match interfaces. Users could easily have unexpected behaviour if they use a small string to do the match. -n, --no-act Don't configure any interfaces or run any "up" or "down" commands. --no-mappings Don't run any mappings. See interfaces(5) for more information about the mapping feature. -V, --version Show copyright and version information. -v, --verbose Show commands as they are executed. EXAMPLES
ifup -a Bring up all the interfaces defined with auto in /etc/network/interfaces ifup eth0 Bring up interface eth0 ifup eth0=home Bring up interface eth0 as logical interface home ifdown -a Bring down all interfaces that are currently up. NOTES
ifup and ifdown are actually the same program called by different names. The program does not configure network interfaces directly; it runs low level utilities such as ip to do its dirty work. FILES
/etc/network/interfaces definitions of network interfaces See interfaces(5) for more information. /var/run/network/ifstate current state of network interfaces KNOWN BUGS
/LIMITATIONS The program keeps records of whether network interfaces are up or down. Under exceptional circumstances these records can become inconsis- tent with the real states of the interfaces. For example, an interface that was brought up using ifup and later deconfigured using ifcon- fig will still be recorded as up. To fix this you can use the --force option to force ifup or ifdown to run configuration or deconfigura- tion commands despite what it considers the current state of the interface to be. The file /var/run/network/ifstate must be writable for ifup or ifdown to work properly. On Ubuntu the /var/run location is a temporary filesystem which is always writable and thrown away on shutdown. You can also use the --force option to run configuration or deconfigura- tion commands without updating the file. Note that the program does not run automatically: ifup alone does not bring up interfaces that appear as a result of hardware being installed and ifdown alone does not bring down interfaces that disappear as a result of hardware being removed. To automate the configura- tion of network interfaces you need to install other packages such as hotplug(8) or ifplugd(8). AUTHOR
The ifupdown suite was written by Anthony Towns <aj@azure.humbug.org.au>. SEE ALSO
interfaces(5), ip(8), ifconfig(8). IFUPDOWN
22 May 2004 ifup(8)