L2Ogre - Ruckus Wireless SmartCell Gateway 200 Reference Manual

3rd Party Access Network Protocol
Access Network
3rd party AP zones can also be configured with QinQ as the access network
protocol. For traffic from these zones, the UE packets are QinQ tagged, and the
SVLAN/CVLAN tags must match one of the defined ranges of SVLAN/CVLAN
configured for that zone. 3rd party AP-Zone to data plane is a 1:1 mapping. No data
plane redundancy is offered for 3rd party APs.
Each 3rd party AP Zone is identified by a list of IP addresses, range, and subnets
used by the APs for sending RADIUS traffic to the SCG. A 3rd party AP Zone ID is
generated internally for each zone. Authentication and accounting procedures
supported are same as Ruckus Wireless APs.
3rd party AP Zone support different northbound tunnels for Ruckus WLAN.

L2oGRE

3rd party AP sends GRE encapsulated packet to the datablade, which has the
header form as seen in Figure 11.
Figure 11. L2oGRE header
Ethernet 802.3 packet is the payload from the UE and includes UE MAC. On
receiving the datacore, it first verifies if the packets are from the supported APs. An
L2oGRE packet does not necessarily come directly from the AP. There could be
one or more intermediate routers indicating that the MAC address may not be that
of the AP. The IP address is used for identifying the AP.
The attribute src_ip address matches and identifies the 3rd party AP zone, which
sends the packet and forwards it to the GRE input module for processing. The GRE
packet header stores the appropriate information in the packet descriptor. For 3rd
party AP packets, it includes AP Zone ID and/or the network traffic profile associated
with the AP zone. The GRE input also maintains the AP table, including statistics.
27
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A