From: Greg Morgan <drkludge@cox.net>
To: Wouter Coppens <wouter.coppens@dedigate.com>
Cc: bridge@osdl.org
Subject: Re: [Bridge] Bridging with kernel-2.6
Date: Fri, 27 Feb 2004 19:36:58 -0700 [thread overview]
Message-ID: <403FFECA.7050407@cox.net> (raw)
In-Reply-To: <DBAC6BAF12D1D64289EC75515BD86577CA653C@exch101>
Wouter Coppens wrote:
> Hey,
>
> Has anybody got bridging working with kernel-2.6?
> Are their things that need special attention?
>
> I have read about the iptables physdev match module for 2.6. Is it required to get the bridge up and running?
I thought you had to have the ebtables patch applied before the bridging
patch. However, with ebtables being in the 2.5 and above kernels, I've
lost track of the order of the patches these days. A quick look at
http://bridge.sourceforge.net/devel.html shows this "The code is updated
as part of the current kernels available at kernel.org." A link to
ebtables is on the same page. Are you experiencing some sort of problem?
Greg
prev parent reply other threads:[~2004-02-28 2:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 16:42 [Bridge] Bridging with kernel-2.6 Wouter Coppens
2004-02-28 2:36 ` Greg Morgan [this message]
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=403FFECA.7050407@cox.net \
--to=drkludge@cox.net \
--cc=bridge@osdl.org \
--cc=wouter.coppens@dedigate.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox