Samsung Tab A slow internet browsing
-
Hi there. Hopefully I mentioned that I'm a noob!!!
I used the pfsense diagnostics/packet capture and put the ip address of my Tab in the "host address field" (192.168.1.147). I started the capture, then loaded www.CNN.com into the Firefox browser on the Tab. After CNN (finally!) loaded, I stopped the capture. Below is the output. It's all Greek to me! Help!
20:10:54.610995 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.625534 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.643070 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.662169 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.675744 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.694308 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.713484 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.724851 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.741378 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.758057 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.774651 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.791028 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.808365 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.824617 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.840549 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.847409 IP 192.168.1.147.52462 > 151.101.125.67.80: tcp 0
20:10:54.847440 IP 151.101.125.67.80 > 192.168.1.147.52462: tcp 0
20:10:54.850828 IP 192.168.1.147.52462 > 151.101.125.67.80: tcp 0
20:10:54.850858 IP 192.168.1.147.52462 > 151.101.125.67.80: tcp 331
20:10:54.850874 IP 151.101.125.67.80 > 192.168.1.147.52462: tcp 0
20:10:54.857049 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.873119 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.889984 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.892453 IP 151.101.125.67.80 > 192.168.1.147.52462: tcp 544
20:10:54.902083 IP 192.168.1.147.52462 > 151.101.125.67.80: tcp 0
20:10:54.906403 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.920000 IP 34.194.199.4.443 > 192.168.1.147.58301: tcp 31
20:10:54.923382 IP 192.168.1.147.58301 > 34.194.199.4.443: tcp 0
20:10:54.923392 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.939797 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.956653 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.973317 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:54.990039 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.006911 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.023467 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.040602 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.057310 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.074288 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.089681 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.105814 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.123477 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.138494 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.154836 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.163480 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.174290 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.174433 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 0
20:10:55.177712 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.177722 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 188
20:10:55.188419 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.205754 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.210553 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 0
20:10:55.211090 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.211098 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.211107 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.211114 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.211122 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 596
20:10:55.219397 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.219410 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.219488 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.219495 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.219511 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.225413 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.237928 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.254551 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.270897 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.280106 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 93
20:10:55.280116 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 177
20:10:55.280123 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 285
20:10:55.288224 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.290365 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 0
20:10:55.290597 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 242
20:10:55.290871 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 66
20:10:55.291154 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.291162 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1340
20:10:55.291170 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.291178 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.291186 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.291194 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.293724 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.293733 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.293810 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 38
20:10:55.294130 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.294138 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.304324 IP 192.168.1.147.55892 > 192.168.1.1.4886: UDP, length 0
20:10:55.321802 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.322008 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.323135 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.323144 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.332218 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.336499 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.336507 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.336584 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.336591 IP 192.168.1.147.44306 > 151.101.125.67.443: tcp 0
20:10:55.340888 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.340897 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.341887 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.341896 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.343390 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.343399 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448
20:10:55.344887 IP 151.101.125.67.443 > 192.168.1.147.44306: tcp 1448 -
Did I do it right? Can anyone help me?
-
Did I do it right? Can anyone help me?
Well, you captured a lot of data, but it doesn't tell us much. The pfSense Packet Capture doesn't show a lot of detail It's better to download the capture and display it in Wireshark. But even that wouldn't likely show your problem
-
Hi, there. Thanks for the advice. I downloaded the capture into WS. Very colorful, lots of red (bad?). Not sure how I would display the results here, but you said that it won't likely show my problem, so I guess I'm back to square one.
Every other device works fine, even my Roku. This is the only android device in the house, maybe pfsense is incompatible with android? That would see bizarre to me.
Hope someone can offer further advice!
-
People often display screen captures here. Also, you can attach a file to posts, if needed. Red in itself is not an issue. Wireshark uses a variety of colours to denote various things. What you'd be looking for are things like repeats, lost packets, ICMP error messages, etc.
-
OK, I attached the capture data here. I hope someone is willing to have a quick look and give me some advice. Unfortunately, it was all over my head.
[Tab A packet capture.pcap](/public/imported_attachments/1/Tab A packet capture.pcap)
-
The red in that capture is probably the firefox wifi tickler, nothing to worry about. The black however, are retransmits, something to look into. You might want to do another packet capture of all traffic and see if you have lots of broadcasts. Just a start.
-
OK, here is a packet capture of around 5mins or so with all traffic. Hope this helps!
Sound like you don't think this is an android incompatibility issue?
[packet capture.pcap](/public/imported_attachments/1/packet capture.pcap)
-
OK, here is a packet capture of around 5mins or so with all traffic. Hope this helps!
Sound like you don't think this is an android incompatibility issue?
What would it be incompatible with? IP is IP and Android is build on Linux. I have a couple of Android devices and Linux computers and no problems with pfSense on either. However, the retransmissions indicate a problem somewhere. Is it with just one site? Or several?
-
This is a single site (home network).
Many thanks for your help!
-
This is a single site (home network).
Many thanks for your help!
When you use that Tab, are you trying to access different sites on the Internet?
-
Yes, that's right. Access to my local LAN assets seems to be fine, it's just the monster delays when accessing different sites on the internet. Also using speed tests like Speedtest and Fast.com
-
OK, here is a packet capture of around 5mins or so with all traffic. Hope this helps!
Sound like you don't think this is an android incompatibility issue?
Only 100 packets captured in this one, 0.47s, (check your settings), and looks like you did it on WAN? Lots of broadcast noise there.
Do another capture with 'count' set to 0 and give it a few minutes. Try to access several sites with your tab during the capture. -
Hi there. Sorry to say that when I went back to my Tab to perform another packet capture, everything was working fine. I gave it 24 hrs and things are still fine with speedy internet browsing on the Tab. I've been living with the terrible performance for about three weeks and have not made any changes to pfsense or the network hardware. I hate unsolved mysteries!!
Thank you all for your help and suggestions. Looks like I'm good for now and will report back if things fall back to the previous conditions.
