Muchas gracias, Perry, it works!

If you are only routing, and not doing NAT, make sure you have the NAT rules disabled (Firewall > NAT, switch to manual, delete any rules that show up).

I don't think what you want is possible by disabling firewall/NAT.
With a bridge you would have on your LAN side the public subnet from the WAN.

When you want failover you also need firewall rules, since the firewall rules determine to which gateway (or in your case failover-pool) the frames are sent.

–> You need to enable the firewall/NAT part again.

Follow the guides on loadbalancing/failover on the wiki.
http://doc.pfsense.com/index.php/MultiWanVersion1.2

Thanks Jimp you are really my hero. Thanks for teaching so many stuff. Really appreciate it.

When you have multi-wan setup, you can direct traffic however you want. You can force all traffic from LAN2 out WAN2 if you want, or mix and match, or make them do failover for each other: LAN1 would go into WAN1failstoWAN2, and LAN2 would go into WAN2failstoWAN1, then when both WANs are operating it does what you want, and nobody would have downtime if a WAN fails.

Yes it make sense. Thanks for your explanation. Cheers.

Hi Guys,

At last i get better understanding for it. Does it mean also if isp does not support mlppp i could not do wan aggregation? What i want to do is having a big upload pipe for my website. Which i don't really understand how do other big website did it. For example doing a nslookup for google.com it report back with few public ip does it mean is a dns round robin? Could we determine that with multiple public ip is dns round robin?

Need expert to solve my curiosity. :)

A correction!

After insertion is possible to ping the gateway on this subnet, but to use devices (like print on a printer) is indeed necessary to insert a rule like the friend had earlier reported.

Many people reported the same problem:

http://forum.pfsense.org/index.php/topic,33554.0.html

For others who may land on this thread, you probably just needed to define the load balancer gateway on that first firewall rule. All your LAN traffic would match that rule and use the default gateway, and your second rule would never be hit. So the easiest thing to do would be to delete that second rule, edit the first, and set the gateway there.

I got it to not kernel panic while I had the device in Infrastructure mode but it still didn't work. And I'm sure if I put it back into Adhoc it'll panic again. I don't like my router going down so this isn't a thing I would like to try testing again if at all possible.

Here's one:
http://forum.pfsense.org/index.php/topic,33895.0.html

Google search works on the forum, too.

Here is an image of the main Dashboard

Is someone of developer aware of this problem? Should i open a new ticket on issue tracker?