Droid OS can't access websites, iPhones & Laptops can
-
Tim,
Here's the response when I try to ping the gateway:
–- IP (wlan0) fe80::867a:88ff:fe77:a362%wlan0
--- IP (wlan0) 10.0.1.105And that's it. No idea why it's showing IPv6 in the first line.
-
Tim,
Here's the response when I try to ping the gateway:
–- IP (wlan0) fe80::867a:88ff:fe77:a362%wlan0
--- IP (wlan0) 10.0.1.105And that's it. No idea why it's showing IPv6 in the first line.
I am still an IPv6 newb myself, but my suspicions are the IPv6 address being first is the problem. I believe that particular IPv6 address is the Link Local one. Perhaps the Android devices are trying to do everything with the IPv6 address? Do you actually run IPv6 on your networks?
Bill
-
Bill,
I do not run IPv6 on my networks. Even if I set IP settings to static, that IPv6 address still shows up when trying to ping/traceroute.
Edit: When I connect the same access point to the LAN interface, that IPv6 address still exists in "wlan0", but I can connect to the internet/ping/traceroute/etc. So, for some reason the OPT Wifi interface doesn't like this traffic. I can't even see traffic from the Android device being blocked or passed, even though I can see pfSense assign it an IP address under status > system logs > dhcp.
-
Where is your DHCP being provided from? Can you completely disable IPv6 on your access point?
-
DHCP is coming from pfsense. I cannot disable IPv6 on the access point as it doesn't handle dhcp requests, pfsense does.
-
Set your IPV6 configuration on that interface to "None." It doesn't make sense that this issue would only affect Android devices.
-
IPv6 config on that interface is already set to "none". I agree that it doesn't make sense, but for some reason it's only android devices. iOS and Laptops work perfectly fine.
-
Ok so it's fixed now. Here's the problem, and I have NO idea why this was a problem, in case someone runs into it in the future.
I had the Opt interface handling DHCP requests with the range 10.0.1.100 - 10.0.1.130. The IP of the interface was 10.0.1.0.
I decided, for the heck of it, to change the IP on the Opt interface to 192.168.0.1, and change the DHCP server range to 192.168.0.101 - 192.168.0.130. Now, all is working.
wtf??? :o :o >:( >:(
-
Ok so it's fixed now. Here's the problem, and I have NO idea why this was a problem, in case someone runs into it in the future.
I had the Opt interface handling DHCP requests with the range 10.0.1.100 - 10.0.1.130. The IP of the interface was 10.0.1.0.
I decided, for the heck of it, to change the IP on the Opt interface to 192.168.0.1, and change the DHCP server range to 192.168.0.101 - 192.168.0.130. Now, all is working.
wtf??? :o :o >:( >:(
10.0.1.0 would not be a normal interface IP. The ".0" value denotes the subnet or network itself. Devices (such as the firewall interface and other physical assets) generally start at ".1" and count up to one less than the broadcast address. Could be the Android devices consider this an invalid IP address and ignore it ??
Bill
-
You're right. I didn't even think about that since other devices were able to connect, that was dumb… Thanks for your help
