Home » TP-Link Manuals » Networking » TP-Link EAP225-Wall » Manual Viewer

TP-Link EAP225-Wall Omada Controller Software 3.0.5 Windows/Linux User Guide - Page 9

Management in Different Subnets, Host B, IP: 192.168.0.200/24, Host A Controller Host, Layer 2 Switch

View all TP-Link EAP225-Wall manuals

Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

Host A (Controller Host) IP: 192.168.0.100/24 Omada Controller Layer 2 Switch Router (DHCP Server) LAN IP:192.168.0.1/24 Internet Host B IP: 192.168.0.200/24 EAPs Clients Note ··Omada Controller must be running all the time when you manage the network. ··Omada Controller can be running on only one host in a LAN. When other users in the LAN try to launch Omada Controller on their own hosts, they will be redirected to the host that is already running Omada Controller. Management in Different Subnets If your Omada Controller and EAPs are in different subnets, refer to the following topology. A router acts as the gateway of the network. A layer 3 switch acts as a DHCP server to assign IP addresses to EAPs and clients. The Controller Host and the EAPs are connected to the switch's different network segments. To help EAPs find the Controller Host, Omada Discover Utility should be installed on Host B which is in the same subnet with the EAPs. For how to use Omada Discovery Utility, refer to Inform the EAPs of the Controller Host's Address. 3

Section	Page
1 Quick Start	7
1.1 Determine the Network Topology	8
1.1.1 Management on the local Network	8
1.1.2 Management via Cloud Access	10
1.2 Install Omada Controller Software	11
1.2.1 Installation on Windows Host	11
1.2.2 Installation on Linux Host	11
1.3 Inform the EAPs of the Controller Host's Address	13
1.4 Start and Log In to the Omada Controller	14
1.4.1 Launch Omada Controller	14
1.4.2 Do the Basic Configurations	15
1.4.3 Log In to the Management Interface	18
1.5 Create Sites and Adopt EAPs	18
1.5.1 Create Sites	19
1.5.2 Adopt the EAPs	19
1.6 Monitor and Manage the EAPs	20
2 Monitor and Manage the Network	22
2.1 View the Statistics of the Network	23
2.1.1 View the Client Distribution on SSID	23
2.1.2 Have a Quick Look at EAPs and Clients	23
2.1.3 View Current Usage-Top EAPs	24
2.1.4 View Recent Activities	24
2.2 Monitor the Network with the Map	25
2.2.1 Add a Map	25
2.2.2 Monitor the EAPs on the Map	27
2.3 Monitor and Manage the EAPs	28
2.3.1 Manage the EAPs in Different Status	28
2.3.2 View the Detailed Information of EAPs	29
2.3.3 Manage the EAPs in the Action Column	29
2.4 Monitor and Manage Clients	31
2.4.1 View the Current Information of Clients	31
2.4.2 Manage Clients in the Action Column	31
2.5 View Clients Statistics During the Specified Period	32
2.5.1 Select a Specified Period	32
2.5.2 View the History Information of Clients	32
2.5.3 Manage Clients in the Action Column	33
2.6 Manage the Rogue APs List	33
2.6.1 Manage the Untrusted Rogue APs List	34
2.6.2 Manage the Trusted Rogue APs List	34
2.7 View Past Guest Authorization	35
2.8 View Logs	35
2.9 View Alerts	36
3 Configure the EAPs Globally	37
3.1 Wireless Network	38
3.1.1 Add Wireless Networks	38
3.1.2 Configure Advanced Wireless Parameters	43
3.1.3 Configure Band Steering	45
3.1.4 Configure Mesh	46
3.2 Access Control	50
3.3 Portal Authentication	51
3.3.1 No Authentication	52
3.3.2 Simple Password	56
3.3.3 Local User	60
3.3.4 Voucher	68
3.3.5 SMS	75
3.3.6 Facebook	80
3.3.7 External RADIUS Server	81
3.3.8 External Portal Server	86
3.4 Free Authentication Policy	87
3.5 MAC Filter	88
3.6 Scheduler	90
3.7 QoS	92
3.8 Site Settings	95
3.8.1 LED	95
3.8.2 Device Account	96
3.8.3 Reboot Schedule	96
3.8.4 Log Settings	97
3.8.5 Batch Upgrade	98
3.8.6 SSH	100
3.8.7 Management VLAN	101
4 Omada Cloud Service	102
4.1 Configure the Cloud Access	103
4.1.1 Enable Cloud Access	103
4.1.2 Manage the Cloud Users	103
4.2 Manage the Controller via Omada Cloud	105
4.2.1 Access the controller via Omada Cloud	106
4.2.2 Change your TP-Link ID information	108
5 Configure the EAPs Separately	109
5.1 View the Information of the EAP	110
5.1.1 Overview	110
5.1.2 LAN	110
5.1.3 Radio	111
5.2 View Clients Connecting to the EAP	111
5.2.1 User	111
5.2.2 Guest	112
5.3 View Mesh Information of the EAP	112
5.3.1 Uplinks	112
5.3.2 Downlinks	113
5.4 Configure the EAP	113
5.4.1 Basic Config	113
5.4.2 IP Setting	114
5.4.3 Radio	115
5.4.4 Load Balance	116
5.4.5 WLANs	117
5.4.6 Trunk Settings (Only for EAP330)	117
5.4.7 Rogue AP Detection	118
5.4.8 Local LAN Port Settings (Only for EAP115-Wall and EAP225-Wall)	118
5.4.9 Forget this AP	119
6 Manage the Omada Controller	120
6.1 User Account	121
6.2 General Setting	122
6.2.1 Configure Controller Name	122
6.2.2 Configure Mail Server	122
6.3 History Data Retention	124
6.4 Backup&Restore	125
6.5 Auto Backup	125
6.6 Information About the Software	128
7 Application Example	129
7.1 Basic Configuration	130
7.2 Advanced Settings	130
7.2.1 Monitor the EAPs with Map	130
7.2.2 Configure Portal Authentication	131
7.2.3 Create a SSID for the Employees	133
7.2.4 Configure Scheduler	134
Appendix: Omada App	136
1 Install Omada App on the Mobile Device	137
2 Manage your Network in Standalone Mode	137
3 Manage your Network in Controller Mode	140
3.1 Locally manage your EAPs using the Omada App	140

Match case Limit results 1 per page

Host B

IP: 192.168.0.200/24

Host A (Controller Host)

IP: 192.168.0.100/24

Layer 2 Switch

Internet

EAPs

Clients

Router (DHCP Server)

LAN IP:192.168.0.1/24

Omada Controller

±NtTe

Omada Controller must be running all the time when you manage the network.

Omada Controller can be running on only one host in a LAN. When other users in the LAN try to launch

Omada Controller on their own hosts, they will be redirected to the host that is already running Omada

Controller.

Management in Different Subnets

If your Omada Controller and EAPs are in different subnets, refer to the following topology.

A router acts as the gateway of the network. A layer 3 switch acts as a DHCP server to assign IP

addresses to EAPs and clients. The Controller Host and the EAPs are connected to the switch's

different network segments. To help EAPs find the Controller Host, Omada Discover Utility should

be installed on Host B which is in the same subnet with the EAPs. For how to use Omada Discovery

Utility, refer to

Inform the EAPs of the Controller Host’s Address