From: Stephen Hemminger <shemminger@osdl.org>
To: Juergen Pfeiffer <j.pfeiffer@seskion.de>
Cc: bridge@lists.osdl.org, uclinux-dev@uclinux.org
Subject: Re: [Bridge] Is bridgeing possible with kernel 2.6.10
Date: Wed, 26 Jul 2006 08:34:55 -0700 [thread overview]
Message-ID: <20060726083455.08989fc6@localhost.localdomain> (raw)
In-Reply-To: <44C77FD2.2030208@seskion.de>
On Wed, 26 Jul 2006 16:44:34 +0200
Juergen Pfeiffer <j.pfeiffer@seskion.de> wrote:
> Hi
>
> I didn't get bridgeing to work with Linux kernel 2.6.10 (coldfire 5485)
> yet. When i try to configure bridgeing
> with "brctl", everything seems to be ok, but i if i try to ping through
> my bridge, i see ARP-Request arriving on the other side, but the
> ARP-Responses do not go back through the bridge.
Did the bridge get set up right? Did the interfaces come up (look at 'brctl showstp br0')
The bridge is sensitive to the network devices reporting carrier properly,
so a bad network driver or card will make it not work.
> Now i could read in
> "http://www.tldp.org/HOWTO/Ethernet-Bridge-netfilter-HOWTO-2.html#ss2.1"
> that "Use of kernel 2.6 is not yet a good idea".
That's crap. 2.6 works great.
2.4 is now in frozen hibernation mode, there are bugs in
there that are not going to ever be fixed.
> So do i have a change to get it working?
>
next prev parent reply other threads:[~2006-07-26 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 14:44 [Bridge] Is bridgeing possible with kernel 2.6.10 Juergen Pfeiffer
2006-07-26 15:34 ` Stephen Hemminger [this message]
2006-07-26 16:26 ` Juergen Pfeiffer
2006-07-26 17:13 ` Stephen Hemminger
2006-07-27 9:15 ` Juergen Pfeiffer
2006-07-27 17:39 ` Stephen Hemminger
2006-07-28 19:17 ` Bart De Schuymer
2006-08-02 23:05 ` [Bridge] [uClinux-dev] " David McCullough
2006-08-14 15:52 ` [Bridge] " Juergen Pfeiffer
[not found] <1167297092.6795.17.camel@getafix.msbmicro.com>
2006-12-28 9:52 ` Juergen Pfeiffer
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=20060726083455.08989fc6@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.org \
--cc=j.pfeiffer@seskion.de \
--cc=uclinux-dev@uclinux.org \
/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.