selecting ethernet controller fails

Bug #313821 reported by dale
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

ubuntu 2.6.24 -updated this morning
root@moxie:/home/motodale# lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
root@moxie:/home/motodale#

failure is selecting operating ethernet controller
configuration:
1st ethernet cont address 192.168.1.55 - rj45 plug is disconnected
2nd ethernet cont address 192.168.1.47 - operational

if both controllers are left in the up state
the 2nd controller will not answer a ping request.

doing a ifdown on controller eth0 allows the second controller (eth1)
to respond to a ping request.

also it seems than the configuration of eth0 down and eth1 up
does not continue after a restart (reboot)
tried saving the configuration to disk, but does not seem to load that configuration at boot time.

Revision history for this message
Ted (tedks) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Revision history for this message
dale (dalep1) wrote : Re: [Bug 313821] Re: selecting ethernet controller fails

hi;

yes this problem is reproducible.
pc is a penutium processor w/ 1GB memory
ubuntu 8.04 + updates
two ethernet cards.
eth0 = address 192.168.1.47
eth1 = address 192.168.1.50

boot system:
eth0 = not pluged in
eth1 = pluged into switch
A:

1. from remote computer:

ping to 47 fails

ping to 50 fails

2 .from ubuntu (root user):
ping to external computer fails

3. do ifdown on eth0 (address 47)
 now ping to etth1 (address 50) works
and ping from ubuntu to remote computer works

4. do ifup on eth0
 now ping to eth1 (address 50) stills works
and ping to eth0 (address 47) works!!
ping from ubuntu to remote computer works on
address 50

B:
reboot ubuntu and switch plug on ethernet cards from
eth1 to eth0 (50 to 47)

ping to eth0 (address 47) works

ping to eth1 (address 50) works

ping from ubuntu to remote works on eth0 (address 47)

 comment:
if the configuration would persist over a boot/reboot
this would not be an big issue
although answering a ping for an address not connected is strange.

whatever else you need, will try and get it..

thanks;
dale

----- Original Message -----
From: "Ted" <email address hidden>
To: <email address hidden>
Sent: Sunday, February 22, 2009 12:04 AM
Subject: [Bug 313821] Re: selecting ethernet controller fails

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
> 1. Is this reproducible?
> 2. If so, what specific steps should we take to recreate this bug? Be as
> detailed as possible.
> This will help us to find and resolve the problem.
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> --
> selecting ethernet controller fails
> https://bugs.launchpad.net/bugs/313821
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: Incomplete
>
> Bug description:
> ubuntu 2.6.24 -updated this morning
> root@moxie:/home/motodale# lsb_release -rd
> Description: Ubuntu 8.04.1
> Release: 8.04
> root@moxie:/home/motodale#
>
> failure is selecting operating ethernet controller
> configuration:
> 1st ethernet cont address 192.168.1.55 - rj45 plug is disconnected
> 2nd ethernet cont address 192.168.1.47 - operational
>
> if both controllers are left in the up state
> the 2nd controller will not answer a ping request.
>
> doing a ifdown on controller eth0 allows the second controller (eth1)
> to respond to a ping request.
>
> also it seems than the configuration of eth0 down and eth1 up
> does not continue after a restart (reboot)
> tried saving the configuration to disk, but does not seem to load that
> configuration at boot time.
>
>

Revision history for this message
Alex Denvir (coldfff) wrote :

We are closing this bug report because it has not been updated for some time. Please reopen it if you have more information to submit, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.