From: Lou Steinberg <lspam5@operations.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] bridge-utils and ppp
Date: Mon, 10 Mar 2008 12:18:06 -0400 [thread overview]
Message-ID: <47D55F3E.4030603@operations.com> (raw)
In-Reply-To: <20080310082655.2f9cd485@extreme>
Stephen-
Stephen Hemminger wrote:
>
> The bridging code only works for devices that have Ethernet headers.
> That is the way the bridging 802.2 standard works, it is a Layer 2 bridge
> and it uses the address information from Ethernet to do routing.
>
> PPP does not use Ethernet level framing so it can't be bridged.
> What were you trying to do? there are plenty of other ways to get the
> same effect.
Makes sense, I suppose (The forwarding is complicated by a p-p link
without a destination mac addr that looks like ethernet). I expected
that someone had built a table to do the mappings because the docs I
referenced in the original post specifically say that ppp can be bridged.
What I'm trying to do is a simple/low latency forward from a vpn
concentrator/firewall/router out to a cellular WAN modem that attaches
to a USB. My firewall lacks the USB interface so I simply need to
forward packets between the USB and ethernet. Am doing it now at layer
3 (using iptables to do NAT) but that adds a lot of complexity and my
firewall already does NAT (so it's happening twice). I haven't yet
tested an ipsec tunnel over the link, but am concerned that I may also
need to add ipsec passthrough if I do this at layer 3.
All in all, a simple layer 2 forward between eth0 and ttyUSB0 is what I
really need.
/Lou
next prev parent reply other threads:[~2008-03-10 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 21:00 [Bridge] bridge-utils and ppp Lou Steinberg
2008-03-09 7:38 ` richardvoigt
2008-03-09 13:58 ` Lou Steinberg
2008-03-10 15:26 ` Stephen Hemminger
2008-03-10 16:18 ` Lou Steinberg [this message]
[not found] <35768C4F0D45AD45BAB2832E96E079E30179BF@newposiserver.Positronics.local>
2008-08-22 23:50 ` Stephen Hemminger
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=47D55F3E.4030603@operations.com \
--to=lspam5@operations.com \
--cc=bridge@lists.linux-foundation.org \
--cc=shemminger@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox