Update README.md

This commit is contained in:
Nasir Hafeez
2021-08-27 18:26:28 +05:00
committed by GitHub
parent 2dd2a3d190
commit 555c440c68

View File

@@ -2,7 +2,7 @@
This is an example of a PHP based external captive portal for TP Link Omada Controller. The code given here can be used to setup a basic captive portal for authorizing WiFi clients. The Omada Controller has to be reachable from the captive portal web server for client authorization to work.
For "External RADIUS Server" with "External Web Portal" the file `radius.html` will be used. It is taken from TP-Link's [website](https://www.tp-link.com/pk/support/faq/2912/).
For "External RADIUS Server" with "External Web Portal" the required files are located in the `RADIUS` folder and consist of the files `index.php` and `login.php`. The file `radius.html` is taken from TP-Link's [website](https://www.tp-link.com/pk/support/faq/2912/) and only a single modification is made in Line 17: hardcoding the public IP of Omada Controller as the IP received in query string might contain private IP which is not useful for connecting back to the controller for user authorization if portal server is located on the internet. This setup will only work when the portal is HTTP based as HTTP to HTTPS connection from client side is blocked by browsers. This problem is resolved in `index.php` and `login.php` by using PHP and CURL for initiating API call to controller from server-side.
Apache access log:
@@ -43,4 +43,4 @@ The basic code has been taken from [here](https://www.tp-link.com/us/support/faq
1. The time parameter's unit is milliseconds and not seconds as given on TP Link's website
2. The parameter `authType: 4` has to be included in the authorization request
This code has been tested on Omada Controller `v4.2.8` with EAP225 `v3.0 (Firmware version 5.0.0 Build 20200918 Rel. 58628)`
This code has been tested on Omada Controller `v4.2.8` with EAP225 `v3.0 (Firmware version 5.0.0 Build 20200918 Rel. 58628)`