Very slow internet browsing
-
Is there a way to know if Intel cards have a problem with pfsense
With the latest version Anyhow
-
Just to clarify this, there is not any known bug in the Intel driver or card setup (that I know about at least). I mentioned this only because the symptoms described were very similar to those I had been reading about in another thread.
https://forum.pfsense.org/index.php?topic=74942.0
In that instance the high latency was seemingly solved by removing the loader.conf.local setting limiting igb to 1 queue.
Steve
-
I know I understood it the first time
My questions were just to rule out a network card problemWhat could it be
why is the latency go crazy
from 10 to 300
why all internet browsing so slow
Except from the upgrades i did not changed anything -
OK. I just wanted to be sure I hadn't mislead anyone.
Your interfaces all appear to be older cards, 2 fxp NICs and one dc. Are you seeing latency problems across all of them?
The driver changes I was talking about were for the newer Intel drivers (em. igb, ixgb) for gigabit NICs and they went into 2.1.1. I don't beleive there were any driver changes between 2.1.1 and 2.1.2.The temperature of the CPU is also higher than normal
This would indicate that the CPU is working hard on something which could be causing the latency. What do you see if you run 'top -SH'?
Steve
-
top -SHhere
$ top -SH last pid: 62178; load averages: 0.07, 0.14, 0.10 up 8+11:39:44 19:01:24 269 processes: 3 running, 248 sleeping, 18 waiting Mem: 463M Active, 52M Inact, 143M Wired, 16M Cache, 84M Buf, 50M Free Swap: 2048M Total, 49M Used, 1999M Free, 2% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU COMMAND 11 root 171 ki31 0K 8K RUN 166.9H 96.39% idle 80016 root 44 0 58740K 13392K piperd 0:06 0.39% php 12 root -68 - 0K 144K WAIT 132:21 0.00% intr{irq20: fxp0 fxp1} 0 root -68 0 0K 88K - 109:12 0.00% kernel{ath0 taskq} 12 root -32 - 0K 144K WAIT 96:06 0.00% intr{swi4: clock} 0 root -68 0 0K 88K - 40:43 0.00% kernel{dummynet} 79394 root 44 0 262M 230M select 17:08 0.00% clamd{clamd} 56758 root 44 0 8004K 4616K kqread 8:06 0.00% lighttpd 12 root -44 - 0K 144K WAIT 7:06 0.00% intr{swi1: netisr 0} 257 root 76 20 3352K 0K kqread 6:50 0.00% <check_reload_stat> 14 root -16 - 0K 8K - 5:03 0.00% yarrow 9389 proxy 44 0 43124K 36700K kqread 3:57 0.00% squid 23208 root 64 20 3264K 1104K select 3:43 0.00% apinger 22 root 20 - 0K 8K syncer 3:42 0.00% syncer 75378 root 44 0 3264K 804K piperd 3:24 0.00% logger 12 root -68 - 0K 144K WAIT 2:48 0.00% intr{irq22: dc0} 68925 root 44 0 3416K 1144K select 2:35 0.00% syslogd 0 root -68 0 0K 88K - 2:33 0.00% kernel{ath0 taskq}</check_reload_stat>Currently the temperature is about 53 ° C
and latency 18
It reached 56 ° CBefore the upgrade it was from 30 to 36 maybe 40 in an exceptional case
And the latency Was up to 30 maximum -
If you run it from the console you will see the line detailing how the usage breaks down, like this:
[2.1.2-RELEASE][root@pfsense.fire.box]/root(1): top -SH last pid: 99751; load averages: 0.02, 0.02, 0.00 up 2+08:39:49 01:57:30 107 processes: 3 running, 88 sleeping, 16 waiting CPU: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 61M Active, 47M Inact, 103M Wired, 1248K Cache, 59M Buf, 269M Free Swap: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU COMMAND 10 root 171 ki31 0K 8K RUN 55.1H 100.00% idle 11 root -32 - 0K 128K WAIT 8:00 0.00% intr{swi4: clock} 286 root 76 20 3352K 1192K kqread 6:55 0.00% check_reload_status 11 root -68 - 0K 128K WAIT 5:46 0.00% intr{irq18: em0 ath0 11 root -68 - 0K 128K WAIT 4:54 0.00% intr{irq17: fxp2 fxpYou have more than twice the processes I do, though I'm not running many packages on the above box.
A couple of things that have caused similar symptoms in the past come to mind. If you have any sort of CPU frequency scaling enabled and it's not quick enough responding to the load it cam start to appear like a large load. Doesn't really explain why it's running hot though.
The other thing is ASPM which can cause problems similar to this. Not sure if that's PCIe only though. Worth checking if it's an option in your BIOS and disabling it if it's there.Steve
-
pciconf -lvIt won't spell out the nic brand or model, you'll probably need to Google the chip number.
I always add the file that pciconf can use to translate device ids to descriptive device names on all my pfsense installs so that the list is much easier to read. I really wish pfsense would include that file by default. It is very useful but it is about 400 KBytes.
/usr/share/misc/pci_vendors
I just do a search for that file for whatever version of freebsd pfsense is running and manually put it in place. pciconf is so much easier to read after that.
This…
em2@pci0:4:0:0: class=0x020000 card=0x060a15d9 chip=0x10d38086 rev=0x00 hdr=0x00 class = network subclass = ethernetbecomes this…
em2@pci0:4:0:0: class=0x020000 card=0x060a15d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' class = network subclass = ethernet -
The other thing is ASPM which can cause problems similar to this
I do not have this Option
I checkednow the latency in 325
Heat 50 °Could be something on the network makes this
Perhaps improper connection of the network jack
Or improper cableDo not know what to check
-
If it were a hardware problem I would expect to see a load of errors in Ststus: Interfaces:
You aren't seeing a high interrupt load then if you run 'top -SH' at the console (or via ssh)?
Steve
-
What came out of this command
I posted earlier post -
If you look at my output from top -SH above I have an extra line the breaks down the usage by type. If you run it fro the console, rather then via the webgui, and allow it to go a few cycles you'll see that. It probably doesn't contain anything useful but at this point it's worth checking anything. :)
Steve
-
Here is the output of a command through ssh
But for some reason been a day and a half that it works well
Besides high CPU temperature*** Welcome to pfSense 2.1.2-RELEASE-pfSense (i386) on home *** WAN1 (wan) -> pppoe0 -> v4/PPPoE: 5.144.62.30/32 LAN (lan) -> fxp1 -> v4: 192.168.0.1/24 WIFI (opt1) -> dc0 -> 0.26, 0.32, 0.18 up 13+00:14:24 07:36:04 WAN2 (opt2) -> ath0_wlan0 -> 0.0 0.0 0.0 100 0) Logout (SSH only) 8) Shell 1) Assign Interfaces 9) pfTop 2) Set interface(s) IP address 10) Filter Logs 3) Reset webConfigurator password 11) Restart webConfigurator 4) Reset to factory defaults 12) pfSense Develope7.98ell 5) Reboot system 13) Upgrade from conso25 6) Halt system 14) Disable Secure She6l (sshd) 12ing host -68 - 0K 144K WAIT 150:39 1.17% intr{irq20: fxp 9929 45 0 370M 148M bpf 5:14 snort{snort} - nter an option: 8 72.1.2-RELEASE][admin@home.plex]/root(1): top -SH last pid: 25296; load averages: 0.26, 0.32, 0.18 up 13+00:14:23 07:36:03 188 processes: 2 running, 168 sleeping, 18 waiting PU: 23.6% user, 0.0% nice, 16.1% system, 2.2% interrupt, 58.1% idle em: 483M Active, 45M Inact, 142M Wired, 18M Cache, 84M Buf, 36M Free Swap: 2048M Total, 60M Used, 1988M Free, 2% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU COMMAND 11 root 171 ki31 0K 8K RUN 266.7H 76.07% idle 72612 root 76 0 57716K 11728K accept 0:04 8.50% php 65865 root 52 0 58740K 12240K accept 0:16 3.76% php 9929 root 45 0 370M 148M bpf 5:14 1.27% snort{snort} 12 root -68 - 0K 144K WAIT 150:39 1.17% intr{irq20: fxp 0 root -68 0 0K 88K scan 167:37 0.00% kernel{ath0 tas 12 root -32 - 0K 144K WAIT 140:35 0.00% intr{swi4: cloc 0 root -68 0 0K 88K - 57:49 0.00% kernel{dummynet 79394 root 44 0 265M 239M select 24:03 0.00% clamd{clamd} 56758 root 44 0 8004K 4852K kqread 14:38 0.00% lighttpd 9389 proxy 44 0 44148K 36372K kqread 14:19 0.00% squid 12 root -44 - 0K 144K WAIT 10:32 0.00% intr{swi1: neti 257 root 76 20 3352K 708K kqread 9:34 0.00% check_reload_st 14 root -16 - 0K 8K - 6:15 0.00% yarrow 22 root 20 - 0K 8K syncer 6:15 0.00% syncer 23208 root 64 20 3264K 1136K select 5:47 0.00% apinger 0 root -68 0 0K 88K - 3:46 0.00% kernel{ath0 tas last pid: 50139; load averages: 0.42, 0.52, 0.39 up 13+00:26:52 07:48:32 187 processes: 2 running, 167 sleeping, 18 waiting CPU: 6.2% user, 0.0% nice, 1.5% system, 4.6% interrupt, 87.7% idle Mem: 436M Active, 60M Inact, 140M Wired, 18M Cache, 84M Buf, 71M Free Swap: 2048M Total, 64M Used, 1984M Free, 3% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU COMMAND 11 root 171 ki31 0K 8K RUN 266.9H 79.39% idle 75084 root 55 0 57716K 12028K accept 0:12 8.40% php 63656 root 76 0 57716K 11812K accept 0:05 2.49% php 12 root -68 - 0K 144K WAIT 150:55 2.10% intr{irq20: fxp0 fxp1} 9929 root 45 0 370M 149M bpf 5:35 1.86% snort{snort} 0 root -68 0 0K 88K - 167:44 0.00% kernel{ath0 taskq} 12 root -32 - 0K 144K WAIT 140:41 0.00% intr{swi4: clock} 0 root -68 0 0K 88K - 57:52 0.00% kernel{dummynet} 79394 root 44 0 264M 237M select 24:03 0.00% clamd{clamd} 56758 root 44 0 8004K 4808K kqread 14:42 0.00% lighttpd 9389 proxy 44 0 44148K 33280K kqread 14:21 0.00% squid 12 root -44 - 0K 144K WAIT 10:33 0.00% intr{swi1: netisr 0} 257 root 76 20 3352K 708K kqread 10:01 0.00% check_reload_status 14 root -16 - 0K 8K - 6:16 0.00% yarrow 22 root 20 - 0K 8K syncer 6:15 0.00% syncer 23208 root 64 20 3264K 1136K select 5:47 0.00% apinger 0 root -68 0 0K 88K - 3:46 0.00% kernel{ath0 taskq} 75378 root 44 0 3264K 804K piperd 3:40 0.00% logger 68925 root 44 0 3416K 1160K select 3:07 0.00% syslogd 12 root -68 - 0K 144K WAIT 3:03 0.00% intr{irq21: ath0} 12 root -68 - 0K 144K WAIT 2:58 0.00% intr{irq22: dc0} 60635 nobody 44 0 5512K 1664K select 2:35 0.00% dnsmasq 90715 root 76 20 3644K 592K wait 2:33 0.00% sh 13 root -16 - 0K 8K sleep 2:12 0.00% ng_queue 3 root -8 - 0K 8K - 1:48 0.00% g_up 74905 root 44 0 14060K 9176K bpf 1:40 0.00% tcpdump 4 root -8 - 0K 8K - 1:39 0.00% g_down 8 root -16 - 0K 8K pftm 1:18 0.00% pfpurge 48583 root 64 20 7200K 7220K select 1:14 0.00% ntpd{ntpd} 9935 root 44 0 7876K 1436K select 1:02 0.00% mpd5{mpd5} 16 root -16 - 0K 8K tzpoll 0:57 0.00% acpi_thermal 0 root -16 0 0K 88K sched 0:50 0.00% kernel{swapper} 12 root -64 - 0K 144K WAIT 0:41 0.00% intr{irq14: ata0} [2.1.2-RELEASE][admin@home.plex]/root(2): -
Nothing much there.
Kind of out of ideas here but I did notice that you are using some swap. That can cause serious performance issues. I wonder if a Snort rule update has pushed you over the limit of RAM and started swapping. Check your memory RRD graph to see if ran out of free memory at any point.Steve
-
I will check this with the snort Off
But i do not think that is the problem
it worked fine until now includes updates once a monthMaybe the new version a bit heavy for this computer
-
Hi,
I have configured Pfsense+Squid 2.3.1-RELEASE-p1 (amd64) for 90 users in our company.
now problem is pfsense is working fine without squid but when i install and configure squid+squidGuard Transparent then it's given very slow browsing so please tell me the best configuration of squid for 90 users.
My System configuration is i5 4 core, 8GB RAM, 500GB HDD. Squid configuration below mentioned.Cache Replacement Policy–-Heap LFUDA
Low-Water Mark in %--------85
High-Water Mark in %-------88
Enable Offline Mode----------checked
Hard Disk Cache Size--------102400
Hard Disk Cache System----ufs
Level 1 Directories-----------16
Hard Disk Cache Location---/squid_cache
Minimum Object Size--------0
Maximum Object Size -------20
Memory Cache Size---------4096
Maximum Object Size in RAM-256
Memory Replacement Policy--Heap GDSFI's Very Urgent please help
