netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Michal Ostrowski <mostrows@speakeasy.net>
Cc: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
	Networking Team <netdev@oss.sgi.com>,
	mh+kernel-bugzilla@zugschlus.de
Subject: Re: [Bug 4177] New: Please consider adding possibility to have	multiple PPPoE sessions with different MAC addresses
Date: Mon, 07 Feb 2005 08:49:46 -0800	[thread overview]
Message-ID: <42079C2A.4010006@candelatech.com> (raw)
In-Reply-To: <1107793112.15984.238.camel@brick.watson.ibm.com>

Michal Ostrowski wrote:
> I'm very hesitant to put something like this into the PPPoE code, though
> I could if the demand for it is strong enough. I think the proper
> solution is something that should be implemented primarily in the
> generic networking code.  
> 
> The right approach IMO is to do something similar to IP-aliasing; that
> is to permit an alternate instance of the interface to exist with the
> desired MAC address.
> 
> Currently one can use IP-aliasing to do this at the IP level:
> 
> ifconfig eth0    10.10.10.10 up ....
> ifconfig eth0:1  10.10.10.11 up ....
> 
> Likewise, I'd propose ethernet aliasing
> 
> ifconfig eth0 10.10.10.10 up ....   #Use native address
> ifconfig eth0.A hw ether AA:BB:CC:DD:EE:FF  # Create mac-addr alias dev
> 
> 
> Given something like this, PPPoE over eth0.A would just work using the
> MAC address bound to eth0.A.
> 
> The virtues of such a scheme are that it eliminates the need for
> management code in PPPoE as PPPoE is not responsible for implementing
> the binding of the new MAC address.  The PPPoE code should not be in the
> business of putting devices into promiscuous mode, and then tracking
> whether or not they should be taken out of promiscuous mode. 
> 
> This scheme also allows for the possibility that hardware devices
> themselves may support multiple MAC addresses (if they can be programmed
> to do so).

I have a MAC-VLAN patch that already does this.  It's based on work
by Alex Zeffertt, but has been considerably hacked by me so he no
should get no blame for what I have done :)  MAC-VLANs allow one to create
a virtual ethernet interface and packets are routed to it based on the
source (or destination) MAC address.  To user-space, each MAC-VLAN
looks just like an ethernet interface.

It is all glommed into my big networking patch, but if there is serious
interest, then I will split it out.  It does require a hook near the bridging
hook in dev.c, and in the past, DaveM has not liked me putting hooks there, so
he may not accept this anyway...

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

      reply	other threads:[~2005-02-07 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200502061207.j16C7UOB009882@fire-1.osdl.org>
2005-02-06 20:53 ` [Bug 4177] New: Please consider adding possibility to have multiple PPPoE sessions with different MAC addresses Arnaldo Carvalho de Melo
2005-02-07 16:18   ` Michal Ostrowski
2005-02-07 16:49     ` Ben Greear [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=42079C2A.4010006@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=acme@conectiva.com.br \
    --cc=mh+kernel-bugzilla@zugschlus.de \
    --cc=mostrows@speakeasy.net \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).