OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue
OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue
2019-10-21 10:35:13
Model: EAP110-Outdoor  
Hardware Version: V3
Firmware Version: 3.3.0 Build 20190301 Rel. 37118

From the beginning we use OMADA v3.0.5 with an EAP115 operating in a Portal Server environment. Our main goal is to gather several info from the client in the authentication phase via the surface given by our external Portal Server. There are several forms to fill next to each, the forms are posted with an asynchronous xmlHttpRequest request, similar like this:

 

var xhttp= new XMLHttpRequest();
xhttp.onreadystatechange = function() {
...
}
xhttp.open("POST", "main", true);
xhttp.setRequestHeader("Content-type", "application/x-www-form-urlencoded");
xhttp.send('...data...');
 

The portal worked fine without any issues. Now we have to change the EAP to an outdoor version, so we replaced the EAP115 with EAP110. Normally the two device should be compatible an identical to use. But we experienced a strange issue with the new EAP: everything works well like formerly, but sometimes (often) the post request fails - when the client clicks the send button on the form nothing happens, our webservice does not receive the request. To find the problem we put some debug line into the js source code. Normally the onreadystatechange function is called four times per posts (with readyState 1,2,3,4 - in the last event with readyState=4 + status=200 on success). But when the post fails we can see that the readyState goes only to 1, which means, that the Open() method has been called. State 2,3 never occurs and about 70 secs later the readyState changes to 4 with a status=0, which means: the request failed. We have no idea what is happening in the backgorund.

 

We tried both changing to the latest OMADA version (v3.2.1) and also to update the firmware of the EAP110 to newest one (3.3.0 Build 20190301 Rel. 37118), but the issue was not solved. Any idea?

 

  0      
  0      
#1
Options
7 Reply
Re:OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue
2019-10-21 11:29:49

Digizoli wrote

when the client clicks the send button on the form nothing happens, our webservice does not receive the request.

 

If I understand correctly, this state changes should happen on your webserver's portal, right? Does your server use a private IP or a public IP?

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options
Re:OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue
2019-10-21 12:05:45

@R1D2 our external portal server is within the local network so it is accessed by the client with a local ip address (like http://192.168.0.72:2050/main?...). Because the client is still not authenticated (and also would be never), the client has no internet access at all, and only can see the portal server in the local network, nothing else.

  0  
  0  
#3
Options
Re:OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue
2019-10-21 16:35:00 - last edited 2019-10-21 16:36:52

 

Digizoli wrote

our external portal server is within the local network so it is accessed by the client with a local ip address (like http://192.168.0.72:2050/main?...).

 

O.k., just a guess:

 

Did you turn on »Guest Network« in Omada Controller? If yes, turn it off temporarily. If it then works again, create an ACL to exclude your webserver and turn on »Guest Network« again to have wireless client isolation.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#4
Options
Re:OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue
2019-10-22 06:07:45

@R1D2  thanks, I tried your suggestion, but did not helped. Please notice, that the portal worked perfectly with the indoor EAP, so I'm afraid this is rather an EAP related issue (there might be a bug in it's firmware or there is a minor incompatibility problem between the outdoor version and OMADA - or simply our device is defective). I also tried to check the logs (turned logging into the level of trace) but nothing relevant entry found yet.

To simplify the test, I made the following proc: turning on the wifi the client is redirected to a simple site which periodically (with 1 sec interval) initiates post requests to the local webservice of the portal server. I count the posts and also count the responses while dumping out the changes of states. 10-20 posts are sent and recd without problems, then the send fails ones, twices, etc. Normally the readyState change order is 1-2-3-4 --> status=200, in the case of a failure readyState remains 1 for over a minute, then goes to 4 with status=0.

 

 

  0  
  0  
#5
Options
Re:OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue
2019-10-22 08:45:25 - last edited 2019-10-22 08:45:59

Hi Digizoli, it just was a guess since this did screw up our external portal. If your indoor EAP still works (you wrote "worked"), then yes, it might be a firmware change. The API for external portals has changed recently, see https://community.tp-link.com/en/business/forum/topic/156625.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#6
Options
Re:OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue
2019-10-22 10:08:45

@R1D2 thank you for all your help! 

  0  
  0  
#7
Options
Re:OMADA v3.2.1 + EAP110-Outdoor(EU) + PortalServer issue
2019-11-06 12:30:05 - last edited 2019-11-06 12:31:39

@Digizoli We have bought another piece of this product and experienced that the problem is the same - so I think only a TP-link technician could help me - is there anybody of them here? I can present more details or can do further tests if necessary. We have to solve this issue ASAP in order to make our client to be satisfied. Thanks for all help in advance.

  0  
  0  
#8
Options

Information

Helpful: 0

Views: 1272

Replies: 7