WISPs often separates access networks using VLANs for easy management, and configure access services ( PPPoE, DHCP HotSpot, etc) on every defined VLAN.
However, it would be useful if the access services could be defined just once, and work across VLAN boundaries.
With this functionality the VLAN tagging on the incoming packets should just be used to mark the return packets, but ignored by the PPPoE/DHCP/etc server. They should be reported to the Radius server, though.
Besides much easier configuration, this will enable client handover between APs configured in separate VLANs.
Why do you need Vlan at the first place then??
VLAN are for strict network separation - if you use VLANs you must create one server for each VLAN. Thats how it suppose to be.
exactly, but you could always bridge the vlans
Some VLAN-related information may be useful in Radius for example.
Bridging will lose this, as all connections will come for the bridge.
How a well-known vendor implements this:
- enable
- configure terminal
- interface type number
- vlan-range dot1q start-vlan-id end-vlan-id
- pppoe enable [group group-name]
Well, at least “interface range” applies every command to each interface in range individually (for example, “interface gi1/1-2; no shutdown” will be internally executed as “interface gi1/1; no shutdown; interface gi1/2; no shutdown”), so it’s just a nice way for quick configuration. Doesn’t vlan-range have the same effect?