AP Isolation

MandM01 wrote:

How do I turn off AP Isolation?  I can not use my Google devices with this network.

 

I had the same issue but resolved it by changing my WPA Version to "WPA/WPA2"

Mychoice wrote:

MandM01 wrote:

How do I turn off AP Isolation?  I can not use my Google devices with this network.

 

I had the same issue but resolved it by changing my WPA Version to "WPA/WPA2"

This setting can be found within the T-Mobile Internet App under network settings.

Ok so i hope this might help. i was trying to connect my Chromecast device to my home internet but it keep saying to turn off ip isolation, anyway i check on the t-mobile internet app but i didn't find no clues then i went to my phone settings i tap on my internet to open the settings and where u see ip settings it had DHCP so i switched it to STATIC witch is the second option it gives u. So i start all over again i reset my Chromecast and start from the beginning and this time it work perfectly, now my phone is an android idk if iPhones are the same but i hope this can help someone out  

Yes this is a problem for me as well as i tried to integrate my network with the device wifi clients and can't reach each other. There us no settings for this on the gui please help

MandM01 wrote:

How do I turn off AP Isolation?  I can not use my Google devices with this network.

 

This is not on by default and there is no setting for it. If you had everything working before on a router just plug that into one of the ethernet port and you are done.

I can't see them

1rst can't route to the ip. I have an i termal address  of 192.168.2.X and the the gateway gives me  192.168.12.X there is no way to route and i can't ping to any of the devices on the wifi.

2nd i have a network fax that uses wifi which connects and a separated scanner and none of the devices can see each other on wifi

Either you have a typo or you have configured the device on the wrong network scope.

"1rst can't route to the ip. I have an i termal address  of 192.168.2.X and the the gateway gives me  192.168.12.X”

The 192.168.12.x/24 network is what the local LAN is working on. The 192.168.2.x/24 network will never communicate to the 192.168.12.x/24 without a gateway/router between the two. Configure all your clients to be on the 192.168.12.x/24 network. Just allow DHCP to provision the IPv4 address or static address outside the scope that the router provisions for. Any and all devices upon the 192.168.2.x/24 segment will only be able to see one another but not communicate to the 192.168.12.x/24 network. In order to communicate to the devices on the 192.168.2.x/24 net configure your device with an IP on that segment, ping one of the known clients on that segment and then once you know you can reach it make the appropriate application level connection to it. If the scanner only has a webUI interface use that to reach it and alter its IP address to the proper network. It will then no longer be reachable on the 192.168.2.x/24 segment but it will be where it needs to be. After devices are configured to the proper IP address rebooting or restarting them might be necessary. When the are configured on the LAN properly and their interface stands up it should ARP and be seen. If you dont see it right away ping the broadcast address of 192.168.12.255 and then look at the ARP table of your device. 

No its not a typo. I should be to route from 192.168.2.X to 192.168.12.X. i am trying to link the 2 networks. And concerning wifi . Two devices on the same network which is on the gateway .12.x don't see each other .

I will take a look at my routing table again on my network side but there is no way to set routing tables on the gateway 

Routing is a two way street. The router interfaces on both networks must be aware of one another. Sure you can't influence the router gateway as it is set to communicate to the external public net via the NAT translation. You need to establish a network router interface on 192.168.12.x/24 for the communication to 192.168.2.x/24 and have that router have directly connected interfaces on both networks. For router on the 192.168.2.x/24 & 192.168.12.x/24 it need the next hop gateway on that to be 192.168.12.1 to reach the internet. The any network 0.0.0.0/24 to go to 192.168.12.1 i.e. any network it does not know can only be available via the 192.168.12.1 gateway address. I would guess you have a asynchronous routing issue right now. 

So, you have both wireless clients on the 192.168.12.x/24 network and they cannot ping one another? Are these MS Windows clients? If so I would guess the firewall is blocking the pings. You may have to provision an exception in the firewall interface OR just temporarily disable the FW on the two clients to confirm the suspicion. If you have IPv6 enabled on the clients then you could check and see if they are aware of one another in the multicast domain. The clients on the same segment don't need the gateway address to talk to one another but they should both have ARP entries to be aware of one another. I would guess FW blocking pings.