Qinq (L2) - Ruckus Wireless SmartCell Gateway 200 Reference Manual

3rd Party Access Network Protocol
Access Network

QinQ (L2)

Wi-Fi clients associated with 3rd party AP zones using QinQ access can be
configured to be bridged to the core network with 0, 1 or 2 VLAN tags. On the
access network, UE traffic from 3rd party APs is sent to the data plane as QinQ
tagged packets. The configuration is as per the zone specifying the accepted
SVLAN and CVLAN ranges of QinQ tags. The UE packet is accepted (based on per
zone authentication settings) provided the QinQ tags of the packet are within the
configured range.
In the user interface, when the administrator user configures the Access Network
as QinQ and the Core Network as Bridge, the SCG acts as the RADIUS proxy and
is managed by the AP controller. The AP acts like a RADIUS client and uses 802.1X/
EAP for authentication. The client traffic is forwarded to the SCG via QinQ. The SCG
support multiple 3rd party zones.
QinQ is configured per 3rd party AP zone, which accesses UE traffic arriving at the
data plane as tagged packets (double VLAN). QinQ access packets are recognized
by configuring SVLAN/ CVLAN range in 3rd party AP zone configuration as seen in
Figure 13. SVLAN/CVLAN range does not overlap between the zones.
NOTE: The SCG does not support roaming for 3rd party APs.
29
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A