Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Kelvin Chan <kelvinc@positronics.com>, bridge@linux-foundation.org
Subject: Re: [Bridge] bridge-utils and ppp
Date: Fri, 22 Aug 2008 19:50:10 -0400	[thread overview]
Message-ID: <20080822195010.601d1873@speedy> (raw)
In-Reply-To: <35768C4F0D45AD45BAB2832E96E079E30179BF@newposiserver.Positronics.local>

On Thu, 21 Aug 2008 17:44:59 -0700
"Kelvin Chan" <kelvinc@positronics.com> wrote:

> Hi Stephen,
> 
> --god, I hate outlook. Sorry, was trying to insert an line break
> but instead sent the email. --
> 
> I'm trying to create an multicast enabled Ethernet bridge using ppp
> and brctl. 
> 
> I tried:
> brctl addbr br0
> brctl addif eth0
> brctl addif ppp0
> 
> after last command, I get:
> can't add ppp0 to bridge br0: Invalid argument
> 
> both eth0 and ppp0 are up and have an address. I googled around 
> and found this an issue with the kernel bridge code. However, in 
> Linux Foundation's bridge-utils documentation, it didn't mention
> the required kernel version. I'm running 2.6.18 from Debian Etch.
> 
> Can you give me any hints to bridge an ppp to eth device?
> 

Won't work because PPP is a tunneling interface so it doesn't
have an ethernet header required for bridging.  Layer 2 versus Layer 3 issue.

       reply	other threads:[~2008-08-22 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <35768C4F0D45AD45BAB2832E96E079E30179BF@newposiserver.Positronics.local>
2008-08-22 23:50 ` Stephen Hemminger [this message]
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

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=20080822195010.601d1873@speedy \
    --to=shemminger@vyatta.com \
    --cc=bridge@linux-foundation.org \
    --cc=kelvinc@positronics.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