I am happy to inform all that the above configuration is working great on the new update of pfSense. Thanks for all the help. Now, I regularly will check for any latest Snapshots here. Thanks again…

Search for ftp helper and portforwarding. This has been discusse a lot in detail. ftp is tricky.

i think i understand this better now so you have to ensure that you put default rules to allow to the subnets that are local so that they do not fall into to poolgateways like source lan destination loadbalance_lan_ip default gateway the source lan desintiation * loadbalance gateway. so now i have load balacned carp routed on bgp thanks very much

This limitation might be dropped in an upcoming version but don't take this as a promise. If it is doable the next major version might support multiple PPPoE-Clients. Not much tested so far.

@almedin: when we can expect OSPF at least? There are no plans to do this.  Start a bounty.

Correct. You just have to make sure (in case all Lines are from the same ISP) that the gateway for each WAN is different or it won't work.

It works thanks a lot  ;D

FAQ.  Multi-wan does not work with FTP. NO, there are no workarounds.

I've logged a "pass" rule binded to Opt1. As soon as Wan goes up I'll paste the logs here ( I've the problem right now and I can't access the router from the outside)..thanks for now  ;)

You have to build yourself an hostsalias for this. Do an nslookup of the specific sites and add the IPs that they resolve to to this alias. Then reference it with a firewallrule. This won't work for sites that change their IPs frequently though.

@hoba: 1:1 NATs won't work for multiwan. This would be a 2:1 nat which is just not possible and is a conflict. Use portforwards on the WANs. This way the state will handle everything. Also, fyi, you should be able to port forward ports 1-65535 w/out a problem.  No need to do individual ports if you don't want to. –Bill

do a hd install of the last snapshot of pfsense then install the freeradius package replace freeradius.xml and freeradius.inc on location /usr/local/pkg with the same to file from this link http://wlelystad.homeip.net/pfsense/freeradius go to the freeradius setup and setup freeradius on the lan port now setup a freeradius client with the ipadress of the lan port remember the shared secret this is needed on the captive portal now setup youre kid as a user with the online time function of freeradius now go to the pfsense captive portal setup set the portal to the lan port set Idle timeout to 6 min Hard timeout blank Authentication to RADIUS authentication Primary RADIUS server IP address to the ip of youre lan Shared secret  to the secret you put in with freeradius Accounting send RADIUS accounting packets eneable this Reauthentication Reauthenticate connected users every minute eneable this Accounting updates interim update  enable this save it and you have a time controled user

thank you very much Bill for the reply ill try this senario as soon as i get my dsl available (it will be wireless speed touch with router) , at the moment i have the sattelite connection ready and  running connected to windows 2000 professional (i beleive it is the least headache form microsoft) i which there is a way to do it with out widows box, any ways the sat company said they'r working on a box to elimiate windows and just use as simple box (probably linux based) with lan connetion soon. thanks again hadi

It's been merged into RELENG_1 and should show up in a snapshot soon. Whenever soon is.

Man… You have one off the wall setup.... You're not utilizing pfSense to its full capabilities.

A solution would be to leave the main WAN out of the pool and keep the other 4 in the pool. This way game and some other normal traffic like http etc. can be excluded from the pool which services all the game clients.

@hoba: No, it's hardcoded in the slbd binary afaik unless Bill tells you something else. I'm still sure it's 3 pings.  But I'm probably catching the exit code wrong.  This is in the C code for our variant of slb - it's not going to be a quick PHP change. –Bill

Clarification 1. The virtual IP are Layer 3 IP's (they are not CARP or ProxyARP form) 2. Virtual IP with PPoE is referred to as configured VIP on Pfsense and pfsense WAN interface is configured as PPoE type. ( Sorry if I was not clear) 3. The purpose of creating the scenario 2 is, when I use PPoE as WAN interface on PFsense the internet connection is very slow and when I start ntop on the WAN interface, the WAN interface is turned off and on… This downtime is longer than what I have imagined (4 to 5 min) 4. In scenario 1 PPoE connection parameters (username and password) are configured on the pfsense WAN interface. But in scenario 2 the PPoE is initiated by the Netgear Modem (username and password are configured on the modem). and I have the link form Netgear modem to Pfsense(WAN Interface). This link is configured on 200.100.3.10/30 network. That is modem Management IP 200.100.3.11 and Pfsense WAN IP (STATIC) 200.100.3.12. 5. This setup brings stability on my wan interface... and when I run ntop, the down time is reduced to 1 sec..or less. This is the reason I want to make the second setup work.

It's not a file. It's just firewall>aliases in the webgui. You can use aliases in all inputfields with red backgrounds.