@kejianshi: Well - I'm either not smarter than you or I'm just hoarding my arcane wisdom.  You decide  :P :|

@Lord_Palethorn: But wouldn't squid help lower the http traffic? (youtube / ustream / steam / ..) so there will be more bandwidth available for gaming? It will to a certain extent but Squid can cause problems for online games that authenticate through http but not for the actual game traffic (Many F2P games do so and I've had it break Blizzard Battlenet as well). Furthermore, you will only save the bandwidth if the data set is repeatedly accessed.

I also see this - could be related as well?: Sep 16 19:38:54 apinger: rrdtool respawning too fast, waiting 300s. Sep 16 19:38:54 apinger: Error while feeding rrdtool: Broken pipe

That will be a WAN interface, effectively, with a private IP. Have you unchecked 'block private networks'? Steve

Ok. Thanks a lot.

Yesterday I decided to do a clean install of 2.1-RELEASE on the same machine and restore a current config with all same settings.  I then reinstalled all same packages with same settings and the issue appears to have gone away for the time being.  Yes, I am using Aliases on a limited basis.

Okay, I might have found a solution for this. Add: dev.igb.0.enable_lro=0 dev.igb.1.enable_lro=0 to /etc/sysctl.conf and restart the pfSense. This solved my IPv4 speed problem.

Well, good to have it narrowed down. Quite some packages have been untouched for years and definitely need polishing for 2.1 (or even 2.0)

a quick search turn up with those:- Squid + SquidGuard Hope this helps

pfSense was originally the 'maxi' version of m0n0wall so you could argue that that's pfSense lite. Doesn't have the flexibiloity of pfSense but has a much smaller footprint. http://m0n0.ch/wall/ Steve

Not mentioned in that guide is the firewall rule: @https://doc.pfsense.org/index.php/IGMP_Proxy: You also need a firewall rule on the downstream side (typically LAN) that matches/passes this traffic which has the advanced option checked to allow packets with IP Options. This is different (I think) to the 239.255.255.250:1900 logs you are seeing. Those are probably a server on your LAN trying to announce itself via UPNP. Steve

can someone help me with this? this issue makes 2.1 completely unusable i think this happens because both PPPoEs get the same gateway IP from the server, but that is common

Thanks  ;) and well poo the's packets are killing my net man >:( , ill get a hold of my ISP and see what they can do.

Oups, just found myself… I can reach the Gigabit by increasing the tcp windows size. At least could be usefull for others :)

It's more than a convention. What you are entering in that box is gateways for pfSense to use that are on that interface. For a WAN interface that will be the upstream gateway, usually your ISP but could be a modem if you're double NATing. For a LAN interface it will usually be left empty because there are no gateways on the LAN network that the pfSense box can use. But that's not always the case. If you have another router on the LAN side and it has another subnet behind it that pfSense will use that router as a gateway to the other subnet. Without it packets addressed to the other subnet will have no route. In that case you must enter the downstream router as a gateway on LAN. Steve

Oh yeah, I tired resetting the router to factory defaults and with nothing but the basic configurations it is still happening.

It really depends on your use case. Here at home I could use a really long password that I couldn't type reliably blind because viewing as I type it isn't ever a problem. If I'm logging in remotely over a VPN that might not be suitable as I could be overlooked as I type. That very rarely happens to me but that's just my own usage. As I said I can't really see any drawbacks to having more options (as long as it's hidden by default) but I have no idea how easy it would be implement. Steve