add a rule to the top of your LAN rules, protocol any, source any, destination LAN IP, gateway default.

If you have the same IP on a different NIC, the router could have the old MAC cached in the ARP table. Turn the router off, wait a minute and power back on.

I know i opened up a very old topic, but i see Google is indexing this as nr #1 and this will definitely help people configuring IPv6 on pfsense boxes. I wrote an article at http://remcobressers.nl/2009/08/configuring-native-ipv6-pfsense/

in ur case, do u want this? in simple word, your LAN client, want to bind an IP (WAN1) then if WAN1 disconnected, u want LAN client bind to WAN2 IP, is that correct? if yes, try add NAT-Rule….

You can find at http://forum.pfsense.org/index.php/topic,10407.0.html I was folow this guide but speed is not perfect now i find solution to increase speed

End of story : Now my 5 WAN balance like a charm. All I had to do is to remove the default rule on the WAN firewall… Maybe a good thing to a in tutorials.

New developments: I only have this problem when sticky connections is on, otherwise, it works fine.

Hmm… it's in my 1.2.2 as well.  :-\

This forum provides an excellent search function: http://forum.pfsense.org/index.php?action=search http://forum.pfsense.org/index.php/topic,17915.0.html http://forum.pfsense.org/index.php/topic,13815.0.html http://forum.pfsense.org/index.php/topic,11685.0.html edit: cheesyboofs is faster :D

Yes. If you've set up multiWAN loadbalancing you already know how. Just set the type of the balancing pool to "server" instead of "gateway". After that create a "virtual server" and use the created server-pool.

If you are using schedules and polict-routing rules it should be fixed in last snapshots.

VERY far. It doesn't sport the "ALPHA" in it's name just for the looks ;)

You can not change the default route, but you can create a load balancer pool that monitors the wan and the cisco isdn router lan link. So then if the wan fails it will actually route all traffic from the LAN out through the cisco ISDN. This will actually work, it does not need to live on the wan interface perse. Alternatively create a opt interface on the pfsense box with the ISDN router stuck behind that. Then it will work in mostly the same fashion. Handling DNS in a working fashion will be a tad bit more difficult though since your failover link is not a always on.

@GruensFroeschli: Can you show a screenshot of your firewall rules? Your text doesnt help much.

slbd is gone in current 1.2.3 snapshots for multi-WAN, replaced with apinger to work around a different issue.

Both approaches sound promising.  Even with a single web page on 1.2.x, I guess images can be fetched across both links if the web browser uses several TCP connections. Thanks for getting back to me. Martin.

You could use the loadbalancer and use failovered policy routing. (instead of weighted routes)