Home » TP-Link Manuals » Networking » TP-Link OC200 » Manual Viewer

TP-Link OC200 Omada Controller Software 4.1.5Windows/Linux User Guide - Page 117

Site-to-Site VPN, VPN Server

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

Page 117 highlights

Chapter 4 Configure the Network with Omada SDN Controller There are many variations of virtual private networks, with the majority based on two main models: ■■ Site-to-Site VPN A Site-to-Site VPN creates a connection between two networks at different geographic locations. Typically, headquarters set up Site-to-Site VPN with the subsidiary to provide the branch office with access to the headquarters' network. Site-to-Site VPN Branch Office Internet Headquarters Omada managed gateway supports two types of Site-to-Site VPNs: • Auto IPsec The controller automatically creates an IPsec VPN tunnel between two sites on the same controller. The VPN connection is bidirectional. That is, creating an Auto IPsec VPN from site A to site B also provides connectivity from site B to site A, and nothing is needed to be configured on site B. • Manual IPsec You create an IPsec VPN tunnel between two peer routers over internet manually, from a local router to a remote router that supports IPsec. Omada managed gateway on this site is the local peer router. ■■ Client-to-Site VPN A Client-to-Site VPN creates a connection to the LAN from a remote host. It is useful for teleworkers and business travelers to access their central LAN from a remote location without compromising privacy and security. The first step to build a Client-to-Site VPN connection is to determine the role of the gateways and which VPN tunneling protocol to use: • VPN Server The gateway on the central LAN works as a VPN server to provide a remote host with access to the local network. The gateway which functions as a VPN server can use L2TP, PPTP, IPsec, or OpenVPN as the tunneling protocol. • VPN Client Either the remote user's gateway or the remote user's laptop or PC works as the VPN client. 115

Section	Page
About this Guide	2
Omada SDN Controller Solution Overview	3
Overview of Omada SDN Controller Solution	4
Core Components	5
Get Started with Omada SDN Controller	10
Set Up Your Software Controller	11
Determine the Network Topology	11
Install Omada Software Controller	12
Start and Log In to the Omada Software Controller	14
Set Up Your Hardware Controller	19
Determine the Network Topology	19
Deploy Omada Hardware Controller	19
Start and Log in to the Controller	20
Set up Your Cloud-Based Controller	24
Manage Omada Managed Devices and Sites	25
Create Sites	26
Adopt Devices	30
For Omada Software Controller / Omada Hardware Controller	30
For Omada Cloud-Based Controller	42
Configure the Network with Omada SDN Controller	45
Navigate the UI	46
Modify the Current Site Configuration	49
Site Configuration	49
Services	49
Advanced Features	52
Device Account	54
Configure Wired Networks	55
Set Up an Internet Connection	55
Configure LAN Networks	69
Configure Wireless Networks	78
Set Up Basic Wireless Networks	78
Advanced Settings	84
WLAN Schedule	86
802.11 Rate Control	86
MAC Filter	87
Network Security	89
ACL	89
URL Filtering	97
Attack Defense	100
Transmission	105
Routing	105
NAT	108
Session Limit	111
Bandwidth Control	112
Configure VPN	116
Create Profiles	143
Time Range	143
Groups	144
Authentication	149
Portal	149
802.1X	180
MAC-Based Authentication	183
RADIUS Profile	184
Services	187
Dynamic DNS	187
SNMP	189
UPnP	190
SSH	191
Reboot Schedule	191
PoE Schedule	192
Export Data	193
Configure the Omada SDN Controller	195
Manage the Controller	196
General Settings	196
Mail Server	197
History Data Retention	199
Customer Experience Improvement Program	199
HTTPS Certificate	200
Access Port Config	200
Manage Your Controller Remotely via Cloud Access	202
Maintenance	204
Controller Status	204
User Interface	204
Backup & Restore	206
Migration	207
Site Migration	207
Controller Migration	212
Configure and Monitor Omada Managed Devices	219
Introduction to the Devices Page	220
Configure and Monitor the Gateway	224
Configure the Gateway	224
Monitor the Gateway	228
Configure and Monitor Switches	232
Configure Switches	232
Monitor Switches	249
Configure and Monitor EAPs	253
Configure EAPs	253
Monitor EAPs	263
Monitor and Manage the Clients	270
Manage Wired and Wireless Clients in Clients Page	271
Introduction to Clients Page	271
Using the Clients Table to Monitor and Manage the Clients	271
Using the Properties Window to Monitor and Manage the Clients	273
Manage Client Authentication in Hotspot Manager	278
Authorized Clients	278
Vouchers	278
Local Users	281
Operators	284
Monitor the Network	287
View the Status of Network with Dashboard	288
Page Layout of Dashboard	288
Explanation of Widgets	290
View the Statistics of the Network	298
Performance	298
Switch Statistics	301
Speed Test Statistics	303
Monitor the Network with Map	305
Topology	305
Map	307
View the Statistics During Specified Period with Insight	310
Known Clients	310
Past Portal Authorizations	311
Rogue APs	312
View and Manage Logs	314
Alerts	315
Events	316
Notifications	317
Manage Administrator Accounts of Omada SDN Controller	323
Introduction to User Accounts	324
Manage and Create Local User Accounts	325
Edit the Master Administrator Account	325
Create and Manage Administrator and Viewer	327
Manage and Create Cloud User Accounts	330
Set Up the Cloud Master Administrator	330

Match case Limit results 1 per page

115

Chapter 4

Conﬁgure the Network with Omada SDN Controller

There are many variations of virtual private networks, with the majority based on two main models:

■

Site-to-Site VPN

A Site-to-Site VPN creates a connection between two networks at different geographic locations.

Typically, headquarters set up Site-to-Site VPN with the subsidiary to provide the branch office

with access to the headquarters’ network.

Site-to-Site VPN

Branch

Oﬃce

Headquarters

Internet

Omada managed gateway supports two types of Site-to-Site VPNs:

•

Auto IPsec

The controller automatically creates an IPsec VPN tunnel between two sites on the same

controller. The VPN connection is bidirectional. That is, creating an Auto IPsec VPN from site A

to site B also provides connectivity from site B to site A, and nothing is needed to be configured

on site B.

•

Manual IPsec

You create an IPsec VPN tunnel between two peer routers over internet manually, from a local

router to a remote router that supports IPsec. Omada managed gateway on this site is the local

peer router.

■

Client-to-Site VPN

A Client-to-Site VPN creates a connection to the LAN from a remote host. It is useful for teleworkers

and business travelers to access their central LAN from a remote location without compromising

privacy and security.

The first step to build a Client-to-Site VPN connection is to determine the role of the gateways and

which VPN tunneling protocol to use:

•

VPN Server

The gateway on the central LAN works as a VPN server to provide a remote host with access to

the local network. The gateway which functions as a VPN server can use L2TP, PPTP, IPsec, or

OpenVPN as the tunneling protocol.

•

VPN Client

Either the remote user’s gateway or the remote user’s laptop or PC works as the VPN client.