Facebook app images and Google Play store app opening very slow?
-
Hi all,
Before I had Asus N-16 set in AP mode with DHCP disabled on 192.168.1.2 and all routing was done thru pfSense. Even then I was noticing when while using Facebook app images would load very very slow, sometimes it would not open at all (I'm on Comcast 50/10). Couple of weeks ago I bought Asus RT-AC68U and did the same. Changed it to AP mode. Now I'm getting same problem.
It also happens when I open play store images would load very very slow.
Obvisoly using AC68U as a router everything works as it should.
Does anyone knows what can I change to fix this issue?
Fresh install of pfSense with just couple of port forwards.TIA
-
Did you ever figure out this problem? I am having the same issue exactly. I have an RT-AC68U also. When I put the AP on the WAN side of pfsense (bypassing pfsense), everything works fine and loads very quickly. If I put it on the LAN size of pfsense, my FB app images won't load and other content loads slowly. Everything through the browser on both my phone and PCs work fine, including facebook. I have also defaulted pfsense and am running 2.1.4. I have tried it with and without web proxy enabled and it simply doesn't work well behind pfsense. I have not had this problem behind pfsense with other wifi access points. I am using embedded pfsense on a netgate. I am on ATT Uverse if it matters.
Joe
-
Did you ever figure out this problem? I am having the same issue exactly. I have an RT-AC68U also. When I put the AP on the WAN side of pfsense (bypassing pfsense), everything works fine and loads very quickly. If I put it on the LAN size of pfsense, my FB app images won't load and other content loads slowly. Everything through the browser on both my phone and PCs work fine, including facebook. I have also defaulted pfsense and am running 2.1.4. I have tried it with and without web proxy enabled and it simply doesn't work well behind pfsense. I have not had this problem behind pfsense with other wifi access points. I am using embedded pfsense on a netgate. I am on ATT Uverse if it matters.
Joe
Honestly I don't remember how I got it to work.
Not sure but I think I was messing too much with changing router IP in my case I set it to 192.168.1.2 but last time I think I connected it to laptop only via cable and left default 192.168.1.1 and changed to access point mode and connected to pfSense switch and then went to DHCP leases and found that Asus router has new IP in my case 192.168.1.112 and that's how I access it's Web Interface.
Let me know if you need more info. -
I am all of the sudden having the same issue. I am using a wnr3500l as an access point to my pfsense. I think this issue started when I changed pfsense to run on port 8087. I am going to do some testing tonight and see if I can fix this. Facebook loads so slow over wifi but is fine on a wired connection. If anyone has any ideas what would cause this please let me know.
-
I want everyone to know I just fixed the problem I was having and hope it will help someone else. So Facebook and a lot of other connections were slow or not working at all when I was connected to my WIFI AP, specifically Android devices. Anyway I found under Interfaces, then LAN that "IPv6 Configuration Type" options was set to "Track Interface". I set this back to None and now I have fast access to everything again from my android devices… I don't even know how this changed as I don't have anything using IPv6. Maybe some one can explain to me what was going on with that? And why was it making most connections so slow on only android devices over WIFI. Laptops were fine over WIFI....
-
I guess the Android devices have both IPv4 and IPv6 enabled. They were getting an IPv6 address of sorts, and probably they prefer IPv6 if it is there. Since you have no real external IPv6 connectivity, the devices would have tried to access sites that have IPv6 addresses by using IPv6. That would timeout and it sounds like they are smart enough to try an IPv4 address after IPv6 has timed out.
Big sites (Facebook, Google…) are going to have an IPv6 address returned by DNS, so they would be effected.
Little sites are probably still on just IPv4, so there is no choice but to use IPv4 first, and it works straight away.
Windows systems probably only have IPv4 turned on, so they are only looking for IPv4 addresses for every site. -
Wanted to say thank you for this post, I was struggling to figure out why our new android devices suddenly couldn't load facebook on wifi, and it was draining our batteries trying.
I set it to "none" and off I went. Now I will go back and set up IPv6 locally since my ISP does support IPv6 (I have it getting an address on the WAN side, so I'll setup IPv6 on the LAN).
Thanks again!