iiii

1. Republic of Iraq
Ministry of Higher Education
And Scientific Research
University of Diyala
College of Engineering
Roaming
By :
‫جمعة‬ ‫احمد‬

2. SEAMLESS WI-FI ROAMING
» Hotel guests want to be connected anytime
and anywhere while they are in hotel, even
when they are on the move
• Problem • Solution
» Fast roaming between separate APs across the
hotel property allows for seamless
connectivity
Login page
ESSID Hotel
4ipnet EAP-series
Indoor AP
ESSID Hotel
4ipnet OWL-series
Outdoor AP
4ipnet WHG-series
WLANController
2
Why need Roaming?

3. Purpose & Benefit
3
• Wi-Fi users who move between the APs are able to maintain the network connection
without any human intervention
» no need to manually disconnect the association to one AP and re-associate to another AP
» no need to change their own IP address
» no need re-authenticate under the authentication controller (ex. 4ipnet’s controller)

4. PLM VLAN Roaming
• It is commonly used in hospitality venues to manage
the internet service for their guest rooms and public
areas
• Each Port Location Mapping entry can be configured
to provide auth. required service at the location
corresponding to the entry’s VLAN Tag
4

5. Layer 2 & Layer 3 Roaming
• Layer 2 Roaming
» Same SSID
» Same Subnet
» Same Security Level
» Different Channel (Optional)
• Layer 3 Roaming
» Same SSID
» Different Subnet
5

6. Test for Layer 2 Roaming
6
• You may do a simple test
1. Scan for their SSID and connect
2. Go to each AP’s web UI (eg. AP-1 and AP-2) and see
which one being connected.
3. Power off the AP being connected (eg. AP-1) and you
will see you on the other AP’s current user list
immediately (eg. AP-2).
Power Off

7. WISPr
7

8. Local/ On-Demand Account Roaming Out
• Local/ On-Demand Database of WHG711 acts like an external RADIUS server for remote gateway
to service “Roaming Out” users. (AP is not enabled as 802.1X Authenticator)
8

9. Cross Gateway Roaming
• The device’s IP address does not change after the roam.
• The only thing is that service zones of multiple gateways
should not be of the same subnet. Please use
172.21.1.x/24 as WHG2's default SZ, for example.
9

10. 4ipnet Cross Gateway Roaming
10
– [Configurations for controller#1 - Master mode]
1. Click Main Menu -> System -> Service Zone; Enable SZ1 (ex: 192.168.1.x/24)
2. Create a test local account (ex: user1@local)
3. Go to Main Menu > Network > Client Mobility > Cross Gateway Roaming; set controller#1 to Master Mode, enter the
WAN IP address of controller#2 & the Key string, check the Active checkbox, and click Apply.
[Configurations for controller#2 - Slave mode]
1.Click Main Menu -> System -> Service Zone; Enable SZ1 to be with different IP subnet from SZ1 of controller#1 (ex:
172.21.1.x/24)
2. Go to Main Menu > Network > Client Mobility > Cross Gateway Roaming; set controller#2 to Slave Mode, enter the
WAN IP address of controller#1 & the Key string, and click Apply.
3. Click on the "Node List" to verify the active Roaming Gateways.
[Tests of client computer]
1. Client associates to AP1 on the LAN side of controller#1
2. Log in with user1@local
3. Go to controller#1 Main Menu > Status > Online Users to check if the client is online
4.Force the client to roam to AP2 on the LAN side of controller#2; check IP address of the client - it keeps original IP
address
5. Go to controller#1 Main Menu > Status > Online Users to check if the client is still online;
6.The client's Internet traffic will be sent through the GRE tunnel back to the controller#1 and then routed to the Internet
through the WAN connection of the controller#1 at the Master site.
Note: the service zone mapping is 1-to-1 (SZ1 to SZ1, SZ2 to SZ2, SZ3 to SZ3, etc) on both sides of master and slave
controllers, and the subnet must be separate.