[RP-PPPoE] Req:Hints for mulitple pppoe-server instances

[Insane Laughing Clown]

On 06/05/2012 03:48 AM, hbreschner wrote:
> Hi,
>
> So far so gut I launched the PPPoE server with the command line
> "pppoe-server -C sandbox -L 192.168.121.254 -p /etc/ppp/ippool -m 1412
> -I eth1.10"
> cat ippool says "192.168.121.1-100"
>
> Well I changed the setup to let at least a single PPPoE Server catch the
> VLAN 10 tagged packages on either eth1 and eth1.10.
> But the PPPoE server does NOT reply to them.
>
> The VLAN devices are made with
>
> "ip link add link eth1 name eth1.10 address 00:00:00:aa:bb:1a type
> macvlan".
>
> Please can someone tell me what I am doing wrong?
>

I think there's some confusion about vlans. The macvlan you are 
referring to above does NOT create vlans, it creates a new network 
device with a new mac address thats all. More than likely it could have 
'worked' in the sense of running pppoe-server on it, but I bet you did 
not put the interface 'up' (eg: ip link set eth1.10 up). However, this 
is the wrong direction anyways.

When I am saying vlan, and what I thought you were referring to from 
your original message, is 802.1q protocol based VLAN support, which is 
an ethernet level tag added to the frames which identifies them as 
members of a particular network. Managed network switches, dsl access 
concentrators, and other devices understand these tags and give the 
administrator (you) tools to set up which ports are members of any given 
VLAN. This in turn allows you to create many virtual networks over a 
common infrastructure, so you can offer different PPPoE for example to 
different vlans, or dhcp on other vlans, all depending on how the 
endpoint (the end user) is connected (which vlan member they are).

Linux vlan support is the 'vconfig' tool by the way, and if you go this 
route you need to make sure your switches are _configured_ for the vlans 
you want to use.

-ILC