For the scenario you presented, you do not need a layer 3 switch. In your original post, your heavy duty data was on VLAN 99. If you just buy a Cisco 2960 (or other switch that supports LAG and VLANs) and use LAGs to the ESX servers, you'll be OK. Do keep in mind that LAGs don't magically balance traffic across the links. You have to configure them to use bits in the source or destination addresses to determine which physical port in the LAG gets used.

It's wooooorking! For those that come after me with the same issue: the solution was to go into the WAN interface configuration, click the link for "Advanced and MLPPP" and in the "Link Interfaces" box select the right interface (there weren't any selected - that's never going to work!), then save. The problem was possibly caused by my having some settings carrying over from the old ISP, not sure if completely new pfsense-ers will have to do this.

Thanks a lot for help. So can I install phantomJs on  pfSense itself?

OpenVPN may do it. Discaimer:  I've NEVER architected a network with a need for a site-to-site VPN bridge.  Site-to-site bridge, sure, using L2 switches.  VPN, absolutely, but they have always been routed. I had initially started to write an "It can't be done" reply, but started reading openVPN's doc's and howtos.  OpenVPN supports a bridged VPN config, but I'm not clear if it works with site-to-site, or only in a road warrior scenario.. Regardless, a site-to-site bridged VPN would be a huge waste of network and processor bandwidth.

The process is similar though not quite exactly the same in 2.2x's services.inc. Two lines to change there for IPv4: $lighty_config .= "server.bind  = \"0.0.0.0\"\n"; $lighty_config .= "\$SERVER[\"socket\"]  == \"0.0.0.0:{$lighty_port}\" { }\n"; To change 0.0.0.0 to 127.0.0.1. Then after making those changes in services.inc, run /etc/rc.restart_webgui to reload. Check the output of "sockstat -4" and "sockstat -6" to check its IPv4 and IPv6 bindings afterwards.

making an overly complex network with extra overhead in performance for no reason is not fun ;) Why would you be using powerline adapters from different makers?  That they work at all is amazing actually.  Get powerline from the same maker if you want to encrypt their traffic. you could look to something like tcpcrypt or ipsec

@peterk: But in this case we have also installed packages and if im correct those wont be backup in the config.xml? Right ? Wrong.

you want to bound 2 different wifi connections with different ssids?  If you want to see if effects you speed, why don't you connect a device to it and download something large and then connect to your normal wifi and download, do you see any difference if the other wifi is being used?

I found the issue with Pings reading 500 using a speed test and Webpages loading slow prb was IP Do-Not-Fragment compatibility in Firewall advanced section checked Clear invalid DF bits and resolved the issue thanks for your help.

There is no such thing as gig without autonegotiation.  gig is always auto.  I don't know why pfSense shows 1000baseT and 1000baseT full-duplex.  There is no such thing as 1000baseT half-duplex.  My guess is both those selections do the same thing. The problem lies when the other end is hard-set at 100-full or 100-half.  Both sides have to be either hard-set to the same settings or both set to auto.

And, yes, it was the network card. As soon as I replaced it with an Intel (and fixed an "Interfaces not found" error) it was up and running in no time. Thank you.

fixed it

OK, many thanks.

First test ran for a couple of minutes, result approx. 500 MB I will check out FreeBSD too

The source of the high fragmentation was iperf testing, artificial traffic. Our IPsec connections normally don't generate that much fragmented traffic, the testing was not done through IPsec. I think this value should be adjustable, as the firewall should be able to handle the amount of fragmentation that is within norms for the connection without cutting connections off.

@torontob: Hi everyone, I have a Windows 2008 R2 in a datacenter which is serving as my VPN server for all users that is remote to our office. My office pfSense allows one of my users to connect to that Windows VPN server flawlessly - but the moment the second user tries to connect it fails. What could be the issue? and where can I look for the issue? It is clearly stated in the documentation and on the pfsense website that you are limited to one connection per remote IP for PPTP.

Yes I will and thanks. It works now. cheers