ifup - bring a network interface up
ifdown - take a network interface down
2. SYNOPSIS ▲
ifup [-nv] [--no-act] [--verbose] [-i FILE|--interfaces=FILE] [--allow CLASS] -a|IFACE...
ifdown [-nv] [--no-act] [--verbose] [-i FILE|--interfaces=FILE] [--allow CLASS] -a|IFACE...
3. DESCRIPTION ▲
R ifup commands may be used to configure (or, respectively, deconfigure) network interfaces based on interface definitions in the file /etc/network/interfaces .
4. OPTIONS ▲
A summary of options is included below.
If given to ifup, affect all interfaces marked auto. Interfaces are brought up in the order in which they are defined in /etc/network/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 configuration or deconfiguration of the interface.
Show summary of options.
Only allow interfaces listed in an allow-CLASSline in /etc/network/interfaces to be acted upon.
- -i FILE, --interfaces=FILE
Read interface definitions from FILEinstead of from /etc/network/interfaces.
Don't configure any interfaces or run any "up" or "down" commands.
Don't run any mappings. See
R interfaces (5) for more information about the mapping feature.
Show copyright and version information.
Show commands as they are executed.
5. EXAMPLES ▲
Bring up all the interfaces defined with autoin /etc/network/interfaces
Bring up interface
Bring up interface
eth0 as logical interface
Bring down all interfaces that are currently up.
6. NOTES ▲
R ifup are actually the same program called by different names.
The program does not configure network interfaces directly; it runs low level utilities such as
R ifconfig to do its dirty work.
7. FILES ▲
definitions of network interfaces See
R interfaces (5) for more information.
current state of network interfaces
8. KNOWN BUGS/LIMITATIONS ▲
The program keeps records of whether network interfaces are up or down. Under exceptional circumstances these records can become inconsistent with the real states of the interfaces. For example, an interface that was brought up using
ifup and later deconfigured using
ifconfig will still be recorded as up. To fix this you can use the
--force option to force
ifdown to run configuration or deconfiguration commands despite what it considers the current state of the interface to be.
The file /etc/network/run/ifstatemust be writable for
ifdown to work properly. If that location is not writable (for example, because the root filesystem is mounted read-only for system recovery) then /etc/network/run/ifstateshould be made a symbolic link to a writable location. If that is not possible then you can use the
--force option to run configuration or deconfiguration 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 configuration of network interfaces you need to install other packages such as
R hotplug (8) or
R ifplugd (8).
9. AUTHOR ▲
The ifupdown suite was written by Anthony Towns <>.
10. SEE ALSO ▲
R interfaces (5),
R ifconfig (8).