R1D2 wrote

Taggit774 wrote

1) So I am wondering is this normal behavior meaning the AP cannot be managed wirelessly if the guest network function is enabled?

 tp-link.com

2) I am wondering if this is also normal behavior or could this be a NAT/Port Forward issue or something else?

 

Re 1) see the release notes of firmware v2.4.0:

2. The SSID isolation function is promoted to the Guest Network Function. Wireless Clients connected with Guest SSID can’t communicate with each other and the local network.

 

So, yes, it's normal behavior.

 

Re 2): should work if network routes are in place, the firewall allows traffic between those two subnets and gateways are defined on the AP and PC, but I'm not familiar with pfsense and its default routing policies, sorry.

Might be something going on with the AP inregards to my second question. I've noticed a similiar behavior with my laptop. The other night I ran into an issue where my laptop would also timeout trying to reach the AP's web login page. After 5 or 6 failed attempts it would suddenly load the login page (slowly). Once logged in all I could see was the admin page header containing the logo, logout and help buttons. I then had to log out and back in several times before the admin pages would display correctly. During this time the laptop showed I had a good connection to the AP and could also open web pages without issue.

Given the issue with the laptop this would seem to be atleast some what an AP issue as both are on the same subnet so the firewall doesn't even see the communication between the two.

I also forgot to mention in my first post that I do have the mac addresses for the laptop and desktop pc added in the AP for managment access.

Since my last post I have tried a couple of things.

Ran windows 10 network diagnostics from the pc having issues with the AP. It reported "Resource (192.168.20.10) (the AP) is online but not responding to connection attempts.

Made a wired connection on a third subnet with my laptop and that also times out.

I have also connected the same laptop to the switch which is also connected to the AP and I can login. It will however fail to connect sometimes. Seem rather random.

I'll run wire shark and see if that offers any hints.

Update: I have a solar envoy on the same switch as the AP and I can access the envoys web GUi by IP using the same pc that times out trying to access the AP's login page.

Also, I did run wireshark on the pc and I can see connection attempts and re-transmission, but no reply, nothing from the AP.

When I installed the AP I had to make a couple of new cat6 cables. Thought that maybe I might have made a mistake terminating the cables but thinking about it more I can access the AP's login with a laptop connected to the same switch as the AP and I don't seem to have any other issues like dropped internet from the AP. When I had the laptop connected to the switch it did have some timeouts before getting a successful login however. I should see more issues if one of my cables was improperly terminated shouldn't I?

Does the AP rely on IPv6? I have that turned off in the router.

Maybe I should ask, what requirments (such as ports and protocols) need to be met for a successful connection between subnets in regards to communicating with the AP?

I have tried allowing all traffic between the AP and pc with no luck.

Just to recap, when trying to connect to the AP from my pc in a different subnet I can see in the router/firewall that the pc does make a connection to the AP but there is no response from the AP and the webpage times out. Either the AP is dropping the LAN connection

I have to assume there is a problem with the AP but unsure. I think I might now need to install wireshark on the laptop and plug it into the same switch as the AP to do some testing.

Ok, looks like I have some what isolated the issue.

During the initial setup of the AP I enabled the "MAC Authentication" feature and added the MAC addresses for my laptop and pc. Turning this feature off is now letting me login from different subnets. The only issue now is the AP will only allow port 80 login when logging in from a different subnet. Trying HTTPS still times out.

If I am connected to the same switch or use a wireless connection to the AP I can login using HTTPS.

I double and triple checked my MAC addresses and they were without doubt added to the "MAC Authentication" correctly. I can only assume my pfSense router is masking or changing the pc's MAC address.

Given what I have found, when accessing from a different subnet is it normal behavior for the AP to only allow login using HTTP when "MAC Authentication" is disabled?

@Taggit774 

how did you resolve the HTTPS issue. Im having the ame issue.

thanks

@molika I never did get it working until just recently. About a week ago I checked to see if there was any new firmware for the AP and saw I was 2 updates behind. Long story short, I updated to the latested firmware and then gave HTTPS another try and it is now working.

If you update the firmware do not make the same mistake I did. I didn't save a config file to restore my settings for the AP and after I updated I lost all of my settings and had to redo everything.

@Taggit774 

thanks mate, ill try that.