Hi heper. I quickly found a couple: https://www.youtube.com/watch?v=omuklZrzopM http://www.tecmint.com/how-to-setup-failover-and-load-balancing-in-pfsense/ Initially, I tried exactly the way you said below but it did not worked so I had to dig deeper, read more…and things got even more complicated. Now, the "new" setup: one GW group, one FW rule, unchecked GW switching, reset states, reboot. Still not working. I tried to ping the dns servers assigned to failover GW (UPC) and they reply back. I got no other ideas. Edit: it seems it switched to failover (UPC) after 10 minutes and now is staying to it although I brought back main Wan (RDS) [image: FailoverToUPC.PNG_thumb] [image: FailoverToUPC.PNG]      

@Derelict: Ugh.  So OP is trying to MultiWAN by using two different IP subnets on the same LAN segment.  Instead of laying into me why don't you lay into that in your usual manner. Or is there an L3 switch/downstream router we weren't told about? OP what is LANGW? yes there is L3 switch and routing between these networks are working fine. 10.238.81.0  network that pfsense server exist 10.238.56.0  users VLAN1 10.238.59.0  users VLAN2 LANGW is LAN  network (10.238.81.0) that pfsense server exist

In a certain way you are actually combining bandwidth if you have multiple connections, MLPPP (MPLS) can do this and yes also pfSense is able  to do so, but the certain point is, that your ISP must also offer you this ability as a service!!! I know it's not possible to archieve it on a single connection and I don't claim that either. As said we always have multiple connections. Load Balancing or fail over set up would be the other abilities that makes it happen to use any connections together.

I've thought about this also. I can't give you a solution, but my initial thought is that it might be doable with the port of OpenBSD's ifstated. You can install this via 'pkg install ifstated' I have not had time to work out the config, but I was looking at strongswan's 'ipsec' command line interface. This would obviously get clobbered if you touched anything in the gui.

There are lots of things wrong with apinger; dead garbage code. Also, there's been a bug filed about the obnoxious "Could not find IPv6 gateway for interface" for quite a while. Leave things alone if you don't have real issues.

ok, problem solved. in routing -> routes I have defined the default route for pfsense.And i also find a possible bug.There's no option to define route 0.0.0.0 /0 I defined it like : 0.0.0.0/1 + 128.0.0.0/1 to achive 0.0.0.0/0 Now it works fine. thx

Looks like this one for the books because I was able to get everything working from a fresh install.  I'm guessing there was an inherited setting from all the past upgrades that we weren't seeing in the WebConfigurator.  All the settings are now identical to the configuration I posted earlier with Automatic NAT and it worked right away.  Same configuration, same rules, same subnets, same connections on nearly identical hardware. Thanks for  your help.

But u can use a Downloadmanager like "downthemall", most websites support multiple segments, so u can get speed like on big line.

Is your switch0 in L3 mode or does pfSense do all the routing?

atm pfsense only runs on pc architecture (cpu's). maybe someday it'll run on different cpu's

Yeah some simple screenshots would make this much easier to read. If you don't want guest_lan to ping lan – then rules would go on guest_lan.. From what you posted doesn't look like you have any rules on guest_lan for anything.  So it wouldn't be able to do anything at all.

Hi heper, thanks for your reply. The reason we have a gateway is, that the network LAN2 is operated by another company (we are their customers and use their servers) the gateway does the firewalling. In the meantime we did some testing and found out, that active FTP actually works fine - just passive FTP hangs. We decided, that we can live with this behaviour - although even passive FTP should work. (If we disable the firewall (System > Advanced > Firewall/NAT  "disable all packet filtering") even passive FTP works as expected)

nailed it..only had firewall blocking public networks so our internal 192.2 was working fine..doh! Thanks!!

Same network i mean same network as the pfsense fw,  its local network And then on the linux machine i install openvpn server and it will be able to talk to the other networks,  as i will add the static routes to the other networks on the linux machine