Ethernet bridging weirdness

[Douglas Stanley]

On Wed, Sep 15, 2010 at 11:18 AM, jim <jim at well.com> wrote:
>
>   From the beginning of this thread you have claimed
> that the hardware is identical. No one has challenged
> this claim until now: it's a long shot, I know, but
> given the time you have invested it seems worth while
> to verify that the chip sets of the NICs are identical
> (the lspci command will probably yield sufficient
> detail; I'd be interested in knowing of alternative
> commands).
>   Have you exhausted searching the /proc/ directory
> (e.g. /proc/sys/net/*).
>   Also, Soren's remark re load order might offer a
> clue: I suppose you've investigated the output of the
> dmesg command; I'd be interested in knowing any other
> commands that would yield pertinent information.
>
>
Output of lspci is identical, for example:

$ lspci |grep Ethernet
01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network
Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network
Connection (rev 01)
04:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network
Connection (rev 01)
04:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network
Connection (rev 01)

Both machines put out identical output for that command.

Yes, I've investigated the output of dmesg...on the machine where it
doesn't work, eth2 is mentioned at the very beginning, where all the
hardware is found, but not mentioned again anywhere, and neither is
br1. On the machine where it does work, eth2 and br1 are both
mentioned right around where br0 is initialized.

As for /proc, not reall sure what I should be looking for there?

Also, I should mention, that if I change br1 from manual to dhcp, it
seems to come up automatically. I don't want dhcp running on that
though, as it should never have an IP address (it's only to be used by
virtual machines to bridge to the outside).

Thanks,
Doug

>
>
> On Wed, 2010-09-15 at 10:50 -0400, Douglas Stanley wrote:
>> On Wed, Sep 15, 2010 at 7:52 AM, Soren Hansen <soren at ubuntu.com> wrote:
>> > On 15-09-2010 00:15, Douglas Stanley wrote:
>> >>> My guess is that eth2 isn't around at the time br1 has its first config
>> >>> attempt. Can you try removing the "auto br1" line and add an
>> >>> "allow-hotplug br1" line instead?
>> >> Nope, no luck.
>> >
>> > Come to think of it, I'm not sure "allow-hotplug br1" should even be
>> > there. Try removing that, too.
>> >
>>
>> So are you suggesting I have no auto br1 or allow-hotplug br1? How
>> will it start on boot then?
>>
>> I also tried changing auto eth2 to allow-hotplug eth2, but still nothing.
>>
>> This is driving me absolutely batty! I've wasted 3 or 4 days now, when
>> I have projects pilling up that need to get up and running on this
>> hardware.
>>
>> Does anyone know just how I can debug the sittuation?? The devices are
>> abviously attempting to get configured, as they are getting entries
>> put in /var/run/network/ifstate, however, they are not actually coming
>> up!
>>
>> Thanks,
>> Doug
>>
>> > --
>> > Soren Hansen
>> > Ubuntu Developer    http://www.ubuntu.com/
>> > OpenStack Developer http://www.openstack.org/
>> >
>> > --
>> > ubuntu-server mailing list
>> > ubuntu-server at lists.ubuntu.com
>> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
>> > More info: https://wiki.ubuntu.com/ServerTeam
>> >
>>
>>
>>
>> --
>> Please avoid sending me Word or PowerPoint attachments.
>> See http://www.gnu.org/philosophy/no-word-attachments.html
>>
>
>



-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html