All of lore.kernel.org
 help / color / mirror / Atom feed
From: David McCullough <david_mccullough@au.securecomputing.com>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] [uClinux-dev] Is bridgeing possible with kernel 2.6.10
Date: Thu, 3 Aug 2006 09:05:11 +1000	[thread overview]
Message-ID: <20060802230511.GA3547@beast> (raw)
In-Reply-To: <44C77FD2.2030208@seskion.de>


Jivin Juergen Pfeiffer lays it down ...
> 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.
> 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".
> So do i have a change to get it working?

One of the guys here has been testing bridging with 2.6.17 from the
uClinux-dist and it is working fine.  Probably can't offer you much more
than that though,

Cheers,
Davidm

-- 
David McCullough,  david_mccullough@securecomputing.com,   Ph:+61 734352815
Secure Computing - SnapGear  http://www.uCdot.org http://www.cyberguard.com

  parent reply	other threads:[~2006-08-02 23:05 UTC|newest]

Thread overview: 9+ 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
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 ` David McCullough [this message]
2006-08-14 15: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=20060802230511.GA3547@beast \
    --to=david_mccullough@au.securecomputing.com \
    --cc=bridge@lists.osdl.org \
    --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.