that's "normal" with multi WAN like you have. It's not a major issue, as everything will work as you desire, but I consider it a bug. I already have a ticket open on it.
http://cvstrac.pfsense.com/tktview?tn=1320,6

You can work around it by creating a rule permitting traffic to your OPT IP with no gateway selection, and move that rule to the top of your OPT ruleset.

1:1 NAT was only temporarily while testing.
Those rules were removed before getting this status. So it shouldn't do anything.

I'm assuming 154.5.78.254 is the provider end of your circuit. You might want to try using something else as a monitor IP- the provider's DNS server, a public webserver, etc.

Everything works fine, it was a problem with my switch & vlan.

Nope, since its a fresh install of pfSense I only did the basic routes + MultiWAN setup.. Works like a charm now.. Even without advanced outbound NAT…

I just wonder what hickup my modem/router had...

dupuyol: I saw your post previously about only getting one direction of traffic. I haven't had time to look into it yet, but plan to do so as soon as I get a chance (might be a week or two).

@LoZio:

Next step is to find a way to have balancing AND Squid.
Any ideas?

I'd like that too, but am no expert at firkling around inside packges, hopefully someone more expert can explain how it might be done…..

There's some talk about it here http://forum.pfsense.org/index.php/topic,737.0.html, but I'm not sure how this maps into the (beta) 1.2 build of pfSense.

I think your are right with this. But "sticky connection" will break LB with PPPoE WAN atm.

I have upgraded to the latest snapshot it seems to be working now.

Thanks

The term 'Multi-WAN' refers to having several broadband connections running through the same firewall, such as a DSL and a Cable connection. What you want is easily done by adding your additional static IPs under Firewall, Virtual IPs. Then you can use the IPs for port-forwards or 1-1 NAT.

my settings

Knipsel.JPG
Knipsel.JPG_thumb
Knipsel2.JPG
Knipsel2.JPG_thumb
Knipsel3.JPG
Knipsel3.JPG_thumb

@krull:

I think it's ill advised to go with the Alias route like the original wiki did unless it is explained a little further in-depth as alot of people here really screwed things up due to that.

Thanks for the feedback Krull, take your point, how about just 1 aliase for https etc. ports that tend to get upset by load balancing - the others are of les value, but without this one, several rules would be required?

I'll see what I can do about the other bits - DNS definitely, I do it that way myself, but bridge mode I have limited knowledge of  ::)

Hi Look at here:

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

Could give you a clue…

Cheers!

run a cable to your neighbors house or as hoba said …WiFi AP and get your neighbors to use your dual WAN network and split/share the cost with you.  Set up encryption on the AP so only those who share the cost can use it.

I personally have an open AP with no route to my LAN, so all my neighbors can freeload off me, but not access my LAN.  And they do use it.  I think they know it is mine but they don't say anything.  I have a tcpdump command to grab and log all useage just so I can see how often it is used.