@Solla-topee 

Thank you for your reply/questions.

 

One thing to clarify: When I talk about "remote" access it is not remote in the sense of outside the LAN. It is remote, meaning not from a device connected to the AP (through WiFi), but from another node in the LAN network (i.e. through the AP's Ethernet cable).

 

1. Yes. If I use it as a normal AP, it gets an IP address from my main router and from the LAN network anywhere I can access the AP using this IP.

2. This is not applicable. As said above, I do not try to access the AP from outside the LAN, i.e. no port forwarding is necessary. The AP has a local IP and I can even connect to it, but instead of giving the management UI, I get a 403 Forbidden reply.

3. The AP is currently in use, and as the main problem, I cannot enter it any more. Basically when I change to multi-ssid I loose the access through the Ethernet port. (This is the problem.) At that point I can still access it from a WiFi connected device. Once I also change the ssid-s to VLAN, the WiFi connected devices are in a separate network as the AP, so I cannot access it from WiFi either.) So the only way to give you a photo of the settings is to factory reset the device, but then you would not see the current setting. Nonetheless, I can tell you that dhcp server is switched off (WiFi devices get IP from the main router based on their VLAN id - works OK). The IP of the AP itself is through a dhcp client mechanism, and it also receives it OK from the main router.

4. The relevant part of the topology is very simple: (ISP - Media converter - ) Mikrotik RB2011/RouterOS v6.47.4 - TL-WA801ND - WiFi clients. It is worth mentioning that another TP-Link device (WR1043ND) with an openwrt OS is connected similarly (i.e. a hybrid trunc) to the main router (having VLAN cable ports as well, not only WiFi VLANs) and it works as intended.

 

I also attach two screenshots:

One from the main router DHCP client lease list, where you can see that the AP gets a proper IP from the router (just like the TP-Link router converted to an openwrt AP).

The other is the reply received when connecting to the AP. It can be seen that the device is connected (IP, etc. are all working) but the device refuses to accept the connection (as if the Allow Remote Access option was not selected, but IT IS.).

 

 

and the second (I am not allowed to attach two files in one post).

 

@Solla-topee 

Thank you for the firmware. Yes, I can confirm that it works as intended.

 

Actually, I replied to you in e-mail immediately for all the three mails you sent (to all the three addresses that were in your mail). Yesterday, all the three mails I sent on the 25th, 26th were bounced back from your ... .outlook.com server with "Server busy" error. So, sorry, but not I was unpolite; the e-mail system did not allow me to reply.

 

Best regards,

 

jt

@Solla-topee 
 

I have a problem with the same version and the same access...similar to the description here..also there is instability in the piece. I have purchased a lot of quantities, there are complaints

Solla-topee wrote

@jollytall Hello, 

 

Thank you for your update, we sent you a Beta firmware for TL-WA801N V6, please fell free to let us know if that works for you ~ 

Please Help ...

@fiing 

I can confirm again, that the solution I got works. It works ever since then with no problem. It has a beta watermark all over the software, so if you give it to a third party (you say you got many boxes), it does not look good.

I hope tp-link can send you a non-beta version of the same.

Thank you so much Tomorrow I will start installing the firmware for some devices... I trust TpLink ... and the developers. Greetings to all of you