All of lore.kernel.org
 help / color / mirror / Atom feed
From: Friedrich Dominicus <frido@q-software-solutions.de>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridge troubles
Date: Wed, 25 Jun 2008 10:38:48 +0200	[thread overview]
Message-ID: <87fxr16h9j.fsf@q-software-solutions.de> (raw)
In-Reply-To: <20080624093133.6f2b896b@extreme> (Stephen Hemminger's message of "Tue, 24 Jun 2008 09:31:33 -0700")

Stephen Hemminger <shemminger@vyatta.com> writes:

> On Tue, 24 Jun 2008 16:11:36 +0200
> Friedrich Dominicus <frido@q-software-solutions.de> wrote:
>
>> I'm sorry to bother you but I'm stuck
>> 
>> I can not make a bridge work for me. 
>> My current configuration is:
>> eth0      Link encap:Ethernet  Hardware Adresse 00:1d:7d:d1:06:bd  
>>           inet Adresse:192.168.1.1  Bcast:192.168.1.255  Maske:255.255.255.0
>>           inet6-Adresse: fe80::21d:7dff:fed1:6bd/64
>> Gültigkeitsbereich:V
>> 
>> according to all what I could find in the net. The following should do
>> to build a bridge 
>> ifconfig eth0 down
>> # brctl addbr br0
>> # addif br0 eth0
>> # ifconfig eth0 0.0.0.0 up
>> # ifconfig  br0 192.168.1.1 up
Ok, I tried exactly the same on  32-bit linux and there this simply
runs.

So I have to conclude that this either is a problem in my 64-bit machine
setup (however I tried on a different 64-bit platform with the same
result) 
Of that there is some bug on a 64-bit platform

Regards
Friedrich




  reply	other threads:[~2008-06-25  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 14:11 [Bridge] Bridge troubles Friedrich Dominicus
2008-06-24 16:31 ` Stephen Hemminger
2008-06-25  8:38   ` Friedrich Dominicus [this message]
2008-06-25 18:06     ` Stephen Hemminger
2008-06-26  4:47       ` Friedrich Dominicus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fxr16h9j.fsf@q-software-solutions.de \
    --to=frido@q-software-solutions.de \
    --cc=bridge@lists.linux-foundation.org \
    --cc=shemminger@vyatta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.