Fit-pC2i Hardware and Pfsense 2.0
-
Holly s…!
Nice stuff ;D I think U mean: 12Mbit/s ;) -
I also have same hardware and have same issues as you with wifi. :-\
-
Holly s…!
Nice stuff ;D I think U mean: 12Mbit/s ;)No I mean 12 Megabyte per second (120Mbit/s). It actually does more.. :):
Great consumer internet connections here in Holland.I also have same hardware and have same issues as you with wifi. :-\
Does your pfsense crash as wel? I'm not sure if it's the WIFI. I can't be 100 % sure, I would have to disable it a couple weeks and test without it and see if it crashes or not.
-
Holly s…!
Nice stuff ;D I think U mean: 12Mbit/s ;)No I mean 12 Megabyte per second (120Mbit/s). It actually does more.. :):
Great consumer internet connections here in Holland.I also have same hardware and have same issues as you with wifi. :-\
Does your pfsense crash as wel? I'm not sure if it's the WIFI. I can't be 100 % sure, I would have to disable it a couple weeks and test without it and see if it crashes or not.
Yes it crashes aswell.
-
Holly s…!
Nice stuff ;D I think U mean: 12Mbit/s ;)No I mean 12 Megabyte per second (120Mbit/s). It actually does more.. :):
Great consumer internet connections here in Holland.I also have same hardware and have same issues as you with wifi. :-\
Does your pfsense crash as wel? I'm not sure if it's the WIFI. I can't be 100 % sure, I would have to disable it a couple weeks and test without it and see if it crashes or not.
Yes it crashes after few minutes and when i disable wlan interface problem is gone.
-
The device crashes every now and then when you login on the wifi, otherwise it's stable. Check the crash report here :
http://pastebin.com/iEyBktp3
I use the same type of WiFi interface on a system with VIA 800MHz C3 system running pfSense 2.1 snapshot builds and when I actively use the WiFi it sometimes (maybe a couple of times a week) crashes reporting a crash PC in the run driver. It hasn't yet annoyed me enough to get serious about debugging it.
-
Well, I faced problem with different hardware type, when built-in processor was unable to encrypt data for WPA2 encryption:
2 Mbit/s -> WPA2
6 Mbit/s -> LAN
6 Mbit/s -> wifi open network (no encryption)
Maybe this is problem? Or just incompatiblity between device and WLAN card.
12 MB/s = 96 Mbit/s
13,7 MB/s = 109.6 Mbit/sWe have VERY slow links here.. I'm unable to get at least 10/10Mbit.
-
The device crashes every now and then when you login on the wifi, otherwise it's stable. Check the crash report here :
http://pastebin.com/iEyBktp3
I use the same type of WiFi interface on a system with VIA 800MHz C3 system running pfSense 2.1 snapshot builds and when I actively use the WiFi it sometimes (maybe a couple of times a week) crashes reporting a crash PC in the run driver. It hasn't yet annoyed me enough to get serious about debugging it.
Here is a recent crash report (from today):
http://pastebin.com/FuwnPPaqHad a crash almost daily when the wifi (run0) interface was enabeld ( my wifi is being used allot though) Pretty annoying. I am using a router now and disabled the wifi interface and it's been rock stable for weeks.
I do really hope somebody can debug this, I'm willing to chip in some cash if needed.This fitpc is by far the most awesome pfsense device I have ever used (even without wifi). Performance is awesome. Getting 200 MEGABYTE per second transfer speeds between two lan subnets ( traffic goes through pfsense) with a 9% cpu load!
I'm sure it can do much more, but my windows file transfers / harddrive /network can't ;)
-
This fitpc is by far the most awesome pfsense device I have ever used (even without wifi). Performance is awesome. Getting 200 MEGABYTE per second transfer speeds between two lan subnets ( traffic goes through pfsense) with a 9% cpu load!
That's impressive but I think you must have a calculation error there somewhere since that would be 1.44Gbps on 1Gbps NICs. ;)
Steve
-
See the screenshot, windows 7 must of made an error :D
It does actually drop down after 30 seconds to 118-121 Megabyte per second, I think jumbo frames causes this :) Still awesome windows file transfer speeds and a great performing pfsense box (with only 7 watt power usage and the size of my iphone :D!) Let's hope the 10gb switches become affordable soon.. so I can test max performance ;) Atleast my SSD's are not the bottleneck
ontopic: I started a bounty to fix the wifi adapter : http://forum.pfsense.org/index.php/topic,52033.0.html
-
See the screenshot, windows 7 must of made an error :D
It does actually drop down after 30 seconds to 118-121 Megabyte per second, I think jumbo frames causes this :) Still awesome windows file transfer speeds and a great performing pfsense box (with only 7 watt power usage and the size of my iphone :D!) Let's hope the 10gb switches become affordable soon.. so I can test max performance ;) Atleast my SSD's are not the bottleneck
ontopic: I started a bounty to fix the wifi adapter : http://forum.pfsense.org/index.php/topic,52033.0.html
Naw, shouldn't be a jumbo-frames artifact, Windows does this, has for a long time. Once in a while it takes a while for the portion of code that updates the gui to get the clue that data has started transferring, then it tries to catch up on the speed calculation, but the "stop watch" started late. So, you get a situation where it's trying to calculate speed when the data's already been given a head start. Looks good, but certainly not reality.
-
Yes probably a windows artefact.
Impressive performance none the less. 9% CPU load is surprisingly low. Almost suspiciously so.
I don't get anything like that from my Pentium-M box which is of similar computing power in other tests.Other Atom boxes cannot get close to that either. Are you sure that traffic is being routed?
Steve
-
Yes, because I see the interface rdd graphs go up and the transfer is between two separate interfaces (subnets) and network segments (switches).
I did check it through the web interface, maybe buggy or slow refresh?I can get it to go higher when using more transfers/connections at once with torrent and WAN. (Got it up to 37% cpu usage)
-
Fair enough. :)
Steve