Have you tried VIP type carp already?

Not really, this is all traffic on port 80/http. There is no proxy that is inspecting the packets to make a difference here. Also a single connection can only run at a single WAN, so unless you use a downloadmanager it won't help you with a single client and a single download. Multiple downloads or multiple clients of course can take advantage of the loadbalancing.

Please search the forum on how the multiwan does the loadbalancing. It has been extensively discussed before.

You have to make the clients to connect to different public IPs. This is not what pfSense calls inbound loadbalancing. Inbound is distributing requests that come in on one interface to multiple servers. What you need is making the clients use different WANs (public IPs) to connect to. You need a DNS-Server that resolves the DNS for the terminalserver each time to the next of your wan IPs. pfSense can handle different WANs but it can't do the job of the DNS that resolves the requests. You need a DNS solution for this on top of your multiwan pfSense.

From your original post your LAN and WAN is the same subnet and even interface IPs are the same IP.

@Sulti:

LAN IP: 10.100.1.1/24

WAN IP: 10.100.1.1/24
OPT1 as WAN2 IP: 10.100.2.1/24

Besides that I don't see a problem with your setup unless you have some typos somewhere.

@hoba:

Btw, you want to abuse your neighbours unsecured wireless accesspoint as additional wan?  ;D

OH NO, not me! That would be wrong. :-X

Hi.

Well, i did the following two things, don't really know which one solved the problem, but it's solved: upgrade firmware to RC2 (was running RC1) and the following setting checked in Advanced:
Bypass firewall rules for traffic on the same interface
(This option only applies if you have defined one or more static routes. If it is enabled, traffic that enters and leaves through the same interface will not be checked by the firewall. This may be desirable in some situations where multiple subnets are connected to the same interface.)
Best wishes.

64 megs does not run, period.  The webConfigurator is not designed to do so.

No it cannot be easily changed and we do not have plans to do so.

64 megabye machines need m0n0wall, period.

This is one possible solution to the problem. Other solution would be to add a route at the w2k server box and still use it as default gateway (which saves you one hop for clients in the intranet going to WAN and which also will make clients in intranet unaware of a failure of the pfSense when going to the internet). However if this works best for you or is the easiest way to configure it go along with it. Alternatively you could add routes at the single clients that need to talk to the servers behind the pfSense. A third not yet mentioned solution would be a 3 interface pfSense at the intranets WAN with the servers behind a 3rd interface. This way the pfSense would be the default gateway for every client/server and it has all the routes would route without touching anything at client or server side. I would prefer the 3 interface attempt with the pfSense sitting at the real WAN but like I said, what ever works best for you.

Yeah, the wiki is appropriate. We now generate outbound NAT automatically for all interfaces that have a gateway set. If you don't need advanced outbound nat for some special application you simply can skip this step. All you then need is a pool and appropriate firewallrules to utilize loadbalancing and/or policybased routing. I suggest first transferring your m0n0 install 1:1 to the pfSense setup without pool and loadbalancing. Make sure your pfSense setup works the way m0n0 did after that. Then add your OPT-WAN. Create the pool. If a a pool is not referenced by a rule it won't be used. Check status>loadbalancer if all gateways go online. Then create a rule at LAN with source a single IP of a testclient and destination any at the top of your LAN rules. Use the pool as gateway for this rule. Now you can test with that client if your setup works whereas all other clients/servers will still use a non loadbalanced setup. If you are satisfied with the way it works modify your rules at LAN so other machines make use of loadbalancing too.

Hi All,

I have configured my pf with vlans on Wan interface, and works perfectly, now i can add more wans without physical limits.

Regards

Diego

I have added 2 types of aliases for this at my dualwansetup. One portsalias and one hostsalias where I can add portnumbers or IP-Adresses that don't work well with loadbalancing. If I detect another external IP that doesn't work well with it I just add it to the hostslaias. https is added to the portsalias. Both aliases are referenced by a firewallrule as destination to go out to my faster WAN.

Thanks  :)
I thought , "Multi-wan is not supported", this mean necessity to select interface through ping

But pfsense ping IP OPT1 default router - this address isn't localy IP and is inaccessible through WAN interface …
And "monitored IP" - monitored (ping?) by pfsense, not through... ???

You can bridge the aireless card in AP mode to the wired LAN. For the wireless card  in infrastructure mode you have to use a seperate subnet (just don't bridge the interface and use a different subnetspace). pfSense will route between all directly connected subnets  automatically. You only have to set pass rules at the interfaces to allow traffic between them.

pfSense creates NAT for you out of the box (adds NAT to every interface with a gateway by default). You simply have to follow http://wiki.pfsense.com/wikka.php?wakka=OutgoingLoadBalancing

Btw, loadbalancing has been covered in detail for different scenarios already. Please search first.

@acarli:

If I configure the modems in router mode, they should monitor the line and reconnect automatically?
  (I am using 2 ADSL Thomson/Alcatel SpeedTouch 510)

Lol - In my happy days I rewote parts of theire firmware (the 510V3).
For saying : yes, they do. They don't need any help to do so.

Moving into IRC land, thanks for all the help :)

Switch your WAN2 firewallrule to gateway default (you have WAN2 there). You only use dedicated gateway/loadbalancerpools in rules for outgoing traffic.