How exactly should I get access to WiFi's actual name authentication?
NatShell has encountered this problem almost every day during 21 years of WiFi certification. In fact, the way WiFi authenticated is not complicated, but the core depends on one thing:
Existing network equipment, whether external Portal authentication is supported.
I.AC Support external Portal authentication: WiFi authenticated direct software docking
In the case of large and medium hotels, chains, and some new apartment projects, AC controllers are usually deployed to manage APs.
AC:
-
Support external Portal authentication
-
Support for RADIUS/ HTTP returns
-
Support for referring authentication results to a third-party system
So WiFi authenticated.Pure software docking mode。
How WiFi authenticated
In such cases:
-
NatShell WiFi Real Name Certification System as Accreditation Centre
-
AC traffic control and release
-
User authentication page provided by WiFi live name certification system
-
Certification logs are generated centrally by the system
Just on the side of the network.Deployment of an additional log serverThe public security requirements for WiFi's actual name are met.
II. WHY THIS MODEL IS READY TO THE LINKING HOUSE AND GROUP PROJECTS
With the AC support for external Portal authentication, WiFi authenticated has the following advantages:
-
No additional export of equipment is required
-
Network structure remains unchanged
-
It's easy to manage multi-storeys.
-
Authentication strategy can be centralized.
That's why I'm here.Hotel group, brand chain, apartment platformIn this context, WiFi authenticated the software system.
AC: WiFi authenticated must rely on Authentication Gateway
However, in actual projects, more frequently:
-
AC Old Model
-
AC does not support external Portal
-
There's no such thing as an AC.
-
AP is normal fat
In such cases, if software is still forcibly docked, WiFi's actual name certification will not really control user traffic and public security compliance will not be guaranteed.
The only correct way to do this is to deploy WiFi authenticated Authentication Gateway.
IV. The real role of Authentication Gateway in WiFi authenticated
Authentication Gateway“Over-respent equipment”But instead, it has three key roles:
-
User traffic must pass nodes
-
Name of the implementer of certification results
-
Collector of the web log
Only if all the online traffic goes through NATSHEL_AUTH_GATEWAY, WiFi authenticated.“Controllable”。
V. Authentication Gateway STANDARD PLACE
In the NATSHEL_BRAND implementation code, there are three types of deployment that are usually used:
1 ounces of stringing under the main router
-
Main router for outer access.
-
NATHHELL_AUTH_GATEWAY for physical and audit
-
Lower connection switch and AP
This is the most common and stable way of authenticating WiFi deployment.
2 x 2 deployed under the main switch
-
A network for the switchboard as a core node
-
All export flows are harmonized through Authentication Gateway
-
Without affecting internal VLAN structures
3 x side road deployment (specify scenario)
-
Network cannot be interrupted.
-
Through strategic mirrors or currents
-
Similarly, WiFi authenticated audit
In either way, there is only one core objective:
All online behaviour must be perceived and recorded by the WiFi authenticated system.
VI. WHY SHIFTS ARE READY“NATHHEL_AUTH_GATEWAY-type WiFi real name authentication”
In small hotels, hotels and hotel scenes:
-
Simple network structure
-
AC
-
Do not pursue complex functions
-
The core objective is to be examined.
At this point, a small WiFi-based audit gateway is used:
-
- Get out of here!
-
Minor changes
-
High stability
-
Minimum compliance risk
Bif“Re-organizing networks, changing equipment”It's much more realistic.
The results of WiFi's authenticated certification must be consistent, either way
Whether:
-
AC Direct External Portal
-
Or Authentication Gateway Control of Flows
Ultimately, WiFi authenticated must achieve the following results:
-
Real ID.
-
User-end binding
-
Retroactivity of Internet access
-
Logs can be retrieved at any time
NatShell All WiFi Real name certification programs, with the ultimate goal ofSame set of public security approvals for compliance resultsNot“Device form”。
VIII. WiFi authentication is not a selection of equipment, but an election“Suitability”
Many of the projects that have failed to adapt are not systemic failures, but:
-
Network conditions do not match
-
Wrong deployment method
-
The boundaries of responsibility are unclear.
NATSHEL_BRAND has always insisted on the following:
WiFi authenticated form is determined by judging network conditions.
This is also how WiFi authenticated can run in a steady, long time, not“One check to be performed”Keys.