Status: Traffic Graph
-
I noticed an interesting thing!
I put the download on any client computer that goes to the Internet through pfSense, a large file (700m).
I went to another computer on page Status: Traffic Graph.
Downloading stops.
I switched to the Interface: LAN.
Downloading restored.
I switched to the Interface: WAN.
Downloading stops.
So you can do a lot of time!
It's only me that?pfSense 2.0-BETA1
built on Tue May 4 19:57:02 EDT 2010
FreeBSD 8.0-STABLESorry for machine translation.
-
Non-machine translation.
PC is connected to Internet via pfSense and downloading large file.
When I go to pfSense's web-interface Status->Traffic graph the download stops. if I go to any other page of web-interface the download resumes.
this behavior is 100% reproducible.pfSense 2.0-BETA1
built on Tue May 4 19:57:02 EDT 2010
FreeBSD 8.0-STABLE -
if I go to any other page of web-interface the download resumes.
Or rather on the same page, select Interface: LAN.
If we again choose Interface: WAN download stops. -
The rate package that creates the per IP bandwidth tables there puts the selected interface into and out of promiscuous mode frequently. On weird/broken NICs that could imaginably cause connectivity issues. I've never seen that, I can leave mine up all day long no problem, but that's with Pro/1000 NICs.
What type of NICs are in your system, how do they show in dmesg?
Going into promiscuous creates unnecessary log noise too, I opened a ticket to see if we can reasonably disable that behavior for these reasons.
http://redmine.pfsense.org/issues/581 -
@cmb:
What type of NICs are in your system, how do they show in dmesg?
I have very little experience with FreeBSD. Please specify the complete command line you are interested and I'll show what they brought.
-
reboot pfSense and run command from console
dmesg -
-
Look at CPU usage when you hit Traffic Graph.
top -SH -
Doesn't surprise me to see two different Realtek cards in there, those have hardware problems with promiscuous mode on a small number of cards. I didn't see an association of which NIC is assigned to which interface, and if it's only one interface in particular that's affected.
Ermal changed rate today to not put the interface in promiscuous mode, which I expect will fix this (though ultimately it's your hardware that's broken). Try a snapshot from May 14 or newer.
-
VIA VT6105 Rhine III 10/100BaseTX is OTP1 (not used)
RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet is LAN
RealTek 8139 10/100BaseTX is WANUnfortunately this server is more inaccessible to experiments (is replaced on Windows 2003 (and normally works with the same hardware)).