@Swicago 

When you are authenticated, you will not be asked to authenticate again before the time has expired. You must go to hotspot management and log the user out of the portal if you want to be authenticated again before the time you have set has expired. The users should probably have one of the profiles so it is probably not a problem, but if you are going to test, log yourself out of the hotspot portal,

  @MR.S , so there is no way for a user to log themselves out, in order to use a faster voucher?

pfSense for example allows for user to be auto logged off, if idle for a set amount of time. It does not mean their voucher is invalid, they can log in again and continue using it. This makes sense when a voucher is time based where time only counts as user is connected.

In my case I would have customers connect to free voucher, only later decide they want faster speed, maybe to watch netflix or something. That can only be accomplished, if they have a way to log off somehow or the voucher expires. The normal "portal.tplink.net/portal/logout" does not appear to be working for new EAP625 APs, as such my customers have no way to log off and switch vouchers.

Are their API commands I can use from a remote host on the same subnet that can be used to send a log off signal on behalf of the customer?

Thanks for your reply...much appreciated.

Followup reply.... I updated my EAP625 to latest firmware, turns out they do support logout command, however after logging into port and then visiting " portal.tplink.net/portal/logout " it does not work. I assume I need to change this URL to actually hit my OC200 controller. Any info on how to do that? Allowing a way to logoff of the free voucher would allow my customers a quick way to re-auth for faster speed vouchers.

  @Vincent-TP 

Yes, it is EAP625-outdoor HD, hardware version v1.6 on latest 1.3.1 Build 20240929 Rel. 44649

OC200 is running latest stabile 2.17.6 Build 20241101 Rel.44787

The URL portal.tplink.net/portal/logout  does nothing, even though it is enabled in the voucher.

I even made sure firewall has given full access to clients connected to EAP-625, to rule it out. I confirmed by being able to load the OC200 config page from my connected client, andriod.

Per OC200 my EAP625 should support the feature. It is not listed as the unsupported per the  Devices->Configuration Results->Incompatable section. It was before the firmware updates.

Is there a direct URL for the logout page? Like a direct URL to the portal page? OC200_IPADDRESS:8088/portal/logout ??? This URL does not work, so it must be something else.

Is there a way to change to URL on the OC200? tplink.net is a real domain and redirects to /www.aerial.net/shop/ .. Maybe that is the issue, Once logged into portal, the DNS sees this as a real domain. DNS is not controlled by Omada, but by a pfSense router. Per OC200 config page under voucher, it says the URL can be changed in omada.properties, but how. is there an SSH login for OC200 to change the URL? Seems pretty bad to have left out an easy way to change this url to a custom branded one.

As for visiting the URL, it does nothing. Chrome just says the following

We can’t connect to the server at portal.tplink.net.

  @Vincent-TP 

I just got back from holiday. I have upgraded the OC200 formware to 2.18.5 Build 20241211 Rel.56161 (Beta)

There is still no where a place to change the portal logout URL. It is still stuck with portal.tplink.net/portal/logout and a message stating "You can change the default URL by editing portal.logout.domain in the omada.properties file. Some devices may require firmware update to support Portal Logout. Please refer to Configuration Result for details." However, there is no where on the OC200 I can doanload or upload omada.properties

And the URL portal.tplink.net/portal/logout does not work, even though ,my AP ( EAP625-Outdoor HD(US) v1.0 ) running latest firmware 1.3.1 Build 20240929 Rel. 44649  says it supports portal logout.

I even tried direct IP to logout, but it either says cannot access page or just hangs

Tried the following {CONTROLLER_IP}:8088/portal/logout
{CONTROLLER_IP}:8843/portal/logout

Ports are not blocked, for testing I allowed full acces across all tcp/udp for IPs coming from AP and was able to load controller page via {CONTROLLER_IP}, so nothing is preventing me from reaching the controller.

Portal signin and voucher system works fine, I just cannot log out, which I need to work.

Thanks

Vincent-TP wrote

Hi  @Swicago 

 

Thanks for your reply.

 

Can you please answer questions below:

 

1. What kind of clients are connecting to the portal network? 

2. What kind of web browsers are these clients using?

3. Does the logout URL never work on your side? It sometimes works in our local lab.

  @Vincent-TP 

1) Android clients using latest Andriod OS

2) Chrome for Andriod using latest version

3) Never works, ever.

Not really a good system, if even your local lab only sometimes works.
Again, is there no way to use a direct link to the controller???

{controller_IP:PORT}/portal/logout

  @Swicago 

Hello, I'm coming back to you, is there any way to disconnect it from the captive portal?