From: "John W. Linville" <linville@tuxdriver.com>
To: "Peter Valdemar Mørch (Lists)" <4ux6as402@sneakemail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Ethernet+Wireless Bridge?
Date: Tue, 29 Apr 2008 13:22:22 -0400 [thread overview]
Message-ID: <20080429172222.GA11866@tuxdriver.com> (raw)
In-Reply-To: <48173D49.50608@sneakemail.com>
On Tue, Apr 29, 2008 at 05:22:49PM +0200, "Peter Valdemar Mørch (Lists)" wrote:
> Hi all you wonderful people,
>
> Srinivas M.A. srinivas.aji-at-gmail.com |Lists| wrote:
> > The equivalent solution on Linux seems like parprouted
> > (http://www.hazard.maks.net/parprouted/), which also seems to be
> > packaged for Debian, etc. I haven't used it, just found it searching
> > for "arp proxy" and linux. But it seems worth a look.
>
> Yes, I tried parprouted. It works well within what it promises to do.
> But broadcast (e.g. for DHCP!) is not supported. It, in turn suggests to
> use dhcrelay to support DHCP with parprouted. But I didn't try that. I
> still hadn't given up on getting a bridge to work.
>
> But I have now.
Discussion of parprouted is probably off-topic here, but I'm glad
someone mentioned it because I didn't know about it. I have, however,
been manually using the techniques it seems to use for some time to
good effect.
I have had trouble getting either dhcrelay or dhcp-fwd to work in
this kind of environment. If you figure-out how to make it work,
let me know! I suspect that the authors of those utilities did not
anticipate that sort of usage, and therefore are not using APIs that
direct outgoing frames appropriately. However, I could be wrong --
I haven't dug very deeply.
> John W. Linville linville-at-tuxdriver.com |Lists| wrote:
> > For now, my previous recommendation (routing w/ or w/o IP NAT) still
> > stands as the simplest and best documented approach. If that does
> > not appeal to you, I suspect that bridging combined with L2 NAT via
> > ebtables as described in the URL cited above will work...YMMV.
>
> I've just purchased a 3Com 3CRUSB10075 based on the zd1211 driver. Like
> always with Linux it seems, buying hardware is a pseudo-man-month job
> understanding the underlying technologies and so forth. Is the zd1211
> driver "good"? No idea. Does it support WDS? Promiscuous mode? No idea.
> Will I ever need either? No idea.
Unfortunately, I don't think you will see any different (or at least
not better) behavior with that driver either -- it is also based
on mac80211.
> The fact that I'm frustrated is not an indication that I'm less than in
> awe of the response and attention I've gotten here. Thanks a bundle. I'm
> off to enjoying my 3com with parprouted when it arrives and to
> experiment with nat, routing and ebtables just in case.
Good plan... :-)
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-04-29 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 9:25 [Bridge] Ethernet+Wireless Bridge? "Peter Valdemar Mørch (Lists)"
2008-04-28 12:53 ` John W. Linville
2008-04-28 14:04 ` Mark S. Mathews
2008-04-28 15:29 ` "Peter Valdemar Mørch (Lists)"
2008-04-28 16:28 ` John W. Linville
2008-04-29 10:29 ` "Peter Valdemar Mørch (Lists)"
2008-04-29 12:10 ` Srinivas M.A.
2008-04-29 13:15 ` John W. Linville
2008-04-29 15:22 ` "Peter Valdemar Mørch (Lists)"
2008-04-29 17:22 ` John W. Linville [this message]
2008-05-02 12:04 ` Nicolas
2008-05-02 18:32 ` John W. Linville
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=20080429172222.GA11866@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=4ux6as402@sneakemail.com \
--cc=bridge@lists.linux-foundation.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.