Not sure if this is a bug. Verify Release of Device Case ID: hcn-002

Asked by Mark Nighswonger

command "sudo ifdown eth0" produces this response "Ignoring unknown interface eth0=eth0." then "ifdown: interface eth0 not configured"
command "ifconfig" eth0 is still listed.

mark@mark:~$ sudo ifdown eth0
[sudo] password for mark:
Ignoring unknown interface eth0=eth0.
mark@mark:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 70:5a:b6:cc:41:12
          inet addr:192.168.2.5 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: fe80::725a:b6ff:fecc:4112/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1503 errors:0 dropped:0 overruns:0 frame:0
          TX packets:725 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:285839 (285.8 KB) TX bytes:94244 (94.2 KB)
          Interrupt:45

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:12044 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12044 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1747132 (1.7 MB) TX bytes:1747132 (1.7 MB)

mark@mark:~$ sudo ifdown eth0
ifdown: interface eth0 not configured
mark@mark:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 70:5a:b6:cc:41:12
          inet addr:192.168.2.5 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: fe80::725a:b6ff:fecc:4112/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1894 errors:0 dropped:0 overruns:0 frame:0
          TX packets:988 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:372382 (372.3 KB) TX bytes:124233 (124.2 KB)
          Interrupt:45

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:12384 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12384 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1803029 (1.8 MB) TX bytes:1803029 (1.8 MB)

I don't know enough about this test to declare this a bug!

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu ifupdown Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Eliah Kagan (degeneracypressure) said :
#1

Does the eth0 interface work (i.e. can you plug your computer into a network device with an ethernet cable and use the network through the ethernet interface)? That is, are you just trying to understand ifdown's behavior, or was that something you tried in order to fix your ethernet interface?

What is the significance of the text "Verify Release of Device Case ID: hcn-002" in this Question's title?

Revision history for this message
Mark Nighswonger (marknigh) said :
#2

Yes it does. I was running through laptop testing on this page. http://testcases.qa.ubuntu.com/Plans/LaptopTesting#Input/output Scroll halfway down the page to: "Verify Release of Device Case ID: hcn-002" The LAN connection worked fine. When it came time to release the connection, ifconfig showed it as still present. Later on in the test it was released along with a wireless connection. It asks if I want to file a bug, but I wasn't sure if this qualifies as one, so I followed the link here to let a more knowledgeable person make that decision.

Revision history for this message
Jeruvy (jeruvy) said :
#3

Can you try 'ifdown --force eth0', does that take it down?
What is the output for 'ifconfig -a'?
Also what is the content of /etc/network/interfaces?

Revision history for this message
Mark Nighswonger (marknigh) said :
#4

mark@mark-AO532h:~$ ifdown --force eth0
ifdown: failed to open statefile /var/run/network/ifstate: Permission denied
mark@mark-AO532h:~$ sudo ifdown --force eth0
[sudo] password for mark:
mark@mark-AO532h:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 70:5a:b6:cc:41:12
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:45

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:120 errors:0 dropped:0 overruns:0 frame:0
          TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9264 (9.2 KB) TX bytes:9264 (9.2 KB)

wlan0 Link encap:Ethernet HWaddr f0:7b:cb:62:05:a4
          inet addr:192.168.2.6 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: fe80::f27b:cbff:fe62:5a4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:89452 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45209 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:72329474 (72.3 MB) TX bytes:6260054 (6.2 MB)

"the content of /etc/network/interfaces"
auto lo
iface lo inet loopback

I hope that helps. I have only used the ethernet a few times but this is
always up.
MN

On Wed, Feb 2, 2011 at 12:48 PM, Jeruvy <
<email address hidden>> wrote:

> Your question #142389 on ifupdown in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/ifupdown/+question/142389
>
> Status: Open => Needs information
>
> Jeruvy requested for more information:
> Can you try 'ifdown --force eth0', does that take it down?
> What is the output for 'ifconfig -a'?
> Also what is the content of /etc/network/interfaces?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+source/ifupdown/+question/142389
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Jeruvy (jeruvy) said :
#5

Ok, according to that output, eth0 went down (or was down).

Revision history for this message
Mark Nighswonger (marknigh) said :
#6

Okay. Here is the laptop testing question I am trying to answer at http://testcases.qa.ubuntu.com/Plans/LaptopTesting#Input/output

Verify Release of Device

Case ID: hcn-002

   1.

      In the terminal, run sudo ifdown [interface] where [interface] is the interface name, above.
   2.

      In the terminal, run ifconfig and verify that only the loopback device ("lo") is listed.

My question now is, do we need to rework this question, or is it a "FAIL" and I should file a bug report? Yes "sudo ifdown --force eth0" apparently took down or stopped eth0, but that isn't the question I am trying to answer. Is this a question that can be answered here or should it be directed to another forum?
Thank you,
MN

Revision history for this message
Jeruvy (jeruvy) said :
#7

In order to decently answer your question, I would have to know and understand the purpose of that link you posted. BTW it was inaccurate and that page is huge, finding your case took a bit extra time.
As well I don't understand the purpose of the test, or how it was performed. Was this a full install or a wubi or a livecd?
Since I cannot provide you directly with an answer I will leave this open for others to try and solve.

But if you were trying to verify that eth0 worked and that the hardware is supported I'd say with a little hesitation 'yes'.

Revision history for this message
Launchpad Janitor (janitor) said :
#8

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#9

@Mark
Given the time that has passed, at this point, unless you've determined that this is *not* due to a bug, I'd recommend reporting it as one. In the (it seems) unlikely event that it turns out not to be one, the Ubuntu developers on the bug tracker can mark your bug as Invalid.

Revision history for this message
Mark Nighswonger (marknigh) said :
#10

This whole section needs to be rewritten! We can all just skip it until such time that someone has the knowledge and time to make it worthwhile.

http://testcases.qa.ubuntu.com/Plans/LaptopTesting

Networking

Test Automatic Connectivity

Case ID: hcn-001

    Ensure that NetworkManager is running (computer icon in the notification area) and that no networks are currently connected.

    Open gnome-terminal (Applications -> Accessories -> Terminal).

    In the terminal, run ifconfig. Verify that only the loopback device ("lo") is listed.
    Connect the network adapter to a network with a DHCP server.

    After approximately 30 seconds, run ifconfig in the terminal. Verify that a new network device is present and has received an IP address. Note the interface name (e.g. eth0).

    In the terminal, run route -n. Note the IP address that is not "0.0.0.0" in the Gateway column.

    In the terminal, run ping -c 5 [gateway] where [gateway] is the IP address of the Gateway, above. Verify that the command reports "5 packets transmitted, 5 packets received".

File a bug

Verify Release of Device

Case ID: hcn-002

    In the terminal, run sudo ifdown [interface] where [interface] is the interface name, above.

    In the terminal, run ifconfig and verify that only the loopback device ("lo") is listed.

File a bug

Verify Manual Connectivity

Case ID: hcn-003

    In the terminal, run ifconfig [interface] [staticIP] where [interface] is the interface name and [staticIP] is a valid unused IP address on the current network. (Consult your network administrator if you do not know such an address.)

    In the terminal, run ifconfig. Verify that the network device is again listed and has the IP address ([staticIP]) as given above.

    In the terminal, run ping -c 5 [gateway] where [gateway] is the IP address of the Gateway, above. Verify that the command reports "5 packets transmitted, 5 packets received".

    In the terminal, run ifdown [interface] where [interface] is the interface name, above.

File a bug

Test Automatic Connectivity

Case ID: hwn-001

    Ensure that NetworkManager is running (computer icon in the notification area) and that no networks are currently connected.

    Open gnome-terminal (Applications -> Accessories -> Terminal).

    In the terminal, run ifconfig. Verify that only the loopback device ("lo") is listed.

    Right-click on the NetworkManager icon and ensure that Enable Wireless is checked.

    After approximately 30 seconds, left-click on the NetworkManager icon. Verify that one or more wireless networks are visible.

    Select an open (no "shield" symbol next to it) network and left-click it. Verify that the network connection succeeds and that a series of bars replaces the NetworkManager icon.

    In the terminal, run ifconfig. Verify that a new network interface is listed.

    In the terminal, run route -n. Note the IP address that is not "0.0.0.0" in the Gateway column.

    In the terminal, run ping -c 5 [gateway] where [gateway] is the IP address of the Gateway, above. Verify that the command reports "5 packets transmitted, 5 packets received".

File a bug

Verify Release of Device

Case ID: hwn-002

    Right-click the NetworkManager (bars) icon.

    Uncheck the box Enable Wireless.

    In the terminal, run ifconfig and verify that only the loopback device ("lo") is listed.

Revision history for this message
Mark Nighswonger (marknigh) said :
#11

Filed a bug https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/731737
You can close out this question. Thanks for everyone's input.
Mark