Comment 2 for bug 414618

If you disconnect a cable, the interface will lose its RUNNING indication.
For example:

cable connected:

$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:0c:29:fb:5a:c0
          inet addr:192.168.42.128 Bcast:192.168.42.255 Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fefb:5ac0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:37 errors:36 dropped:0 overruns:0 frame:0
          TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5334 (5.3 KB) TX bytes:7855 (7.8 KB)
          Interrupt:19 Base address:0x2024

cable disconnected:

$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:0c:29:fb:5a:c0
          inet6 addr: fe80::20c:29ff:fefb:5ac0/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:37 errors:36 dropped:0 overruns:0 frame:0
          TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5334 (5.3 KB) TX bytes:7855 (7.8 KB)
          Interrupt:19 Base address:0x2024

On Mon, Aug 17, 2009 at 6:18 PM, hexdump <email address hidden> wrote:

> Suggestion for addition: Can one then pull a cable in a multi-network
> setup, re-execute the command, and see or deduce from the command output
> the name (path) of the interface whose cable has been pulled? What would
> those command output differences be?
>
> --
> Ubuntu Server Tips: ifconfig -a
> https://bugs.launchpad.net/bugs/414618
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu Server Tips: New
>
> Bug description:
> ifconfig -a will show you your configured network interfaces.
>