It's not possible with pfSense. But you can put multipe cheap router in front of pfSense so they handle the DHCP stuff and forward their traffic to the pfSense which handles the multiWAN-stuff.

What is the advantage of using 2 w/ CARP over the setup illustrated above?  I assume I would lose the ability to have a transparent proxy, but I'm not sure what I gain by using 2 w/ CARP (other than needing one less server)

I have put those 2 routes into the table with my 2 isp gateways as destination. I also put those 2 dns servers in the general tab. I put my 2 internal dns servers for local resources in the DHCP tab. I enabled the DNS forwarder. I put my pfsense ip adress in the dns forwarder of my 2 internal dns servers. Now it works! THANKS PERRY!!

Forget that four NIC stuff- that's crazy talk. You setup four tunnels just like you set up one- but four times. Each tunnel will be unique due to the endpoint being different. The sites will have different identifiers, so the 'concentrator' box knows how to setup the tunnels. If you can get one setup, you shouldn't have a problem with the others. There is an IPsec tutorial here: http://doc.pfsense.org/index.php/Tutorials and the m0n0wall docs are also helpful, as the IPsec settings are similar: http://doc.m0n0.ch/handbook/

Posting multiple threads to get some input from you guys. I have had VERY limited time to do research in the past few days. I am wanting to cram everything together in one day, and thats not happening. My apologies, I will make sure I research before I post in the forum.

Only in 1.3. The standard work around in 1.2 is to run PPPoE on a router in front of pfSense.

A quick test during lunch tio show that m0n0wall 1.3b doesn't even boot my actual generic pc, that run pfSense … Bummer, I tested it on VMWare and yes there is place to configure the IPv6 Tunnel in the WAN configuration, than you have the option to enable radvd on the LAN and this actually works pretty well, all my test IPv6 clients Workstation got their IPv6 address within the range instantly ...Since my VMWare test was behind a router that doesn't support IPv6-to-IPv4 Protocol 41 (the test was conducted at work) I could not test actual connectivity to my broker, but I was gettin a reply from m0n0 then nothing obviously blocked by the work router. If m0n0 did it, it should be very hard to port their setup into pfSense... MageMinds

This problem is solved.  I rebooted the FW and now everything is working fine.  I never reboot and for once it seemed to help.

got it thanks

I can´t do this via command line? Create a rule to redirect the web traffic starting from localhost? @ermal: Only possible in 1.3 or the special build of 1.2 for traffic shaping!

Possible feature request for 1.3???

Hi, maybe it would work if I fix this part of the dhclient script for my needs add_new_routes() {         $LOGGER "Adding new routes"         $ROUTE add $new_ip_address $LOCALHOST >/dev/null 2>&1         # Only allow the default route to be overridden if it's on our own interface #      DEFAULTROUTE_IFACE=`route get default | grep interface | awk '{print $2};'`         #if [ -z "${DEFAULTROUTE_IFACE}" -o "{$interface}" = "${DEFAULTROUTE_IFACE}" ]; then                 #for router in $new_routers; do                         #if [ "$new_ip_address" = "$router" ]; then                                 #$ROUTE add default -iface $router                                 #>/dev/null 2>&1         #                      echo $ROUTE add default -iface $router | $LOGGER                 #              echo $new_routers > /tmp/${interface}_router                 #      else                         #      $ROUTE add default $router                         #      echo $ROUTE add default $router | $LOGGER                         #      #>/dev/null 2>&1                         #      echo $new_routers > /tmp/${interface}_router                         #fi                         # 2nd and subsequent default routers error out, so explicitly                         # stop processing the list after the first one.                         #break                 #done         #fi But I am not so sure how I can recognise and separate the second default gatway… which is - as I was told today - isn't a second default gateway at all, it's a win2k proxy server whose pdc thinks its a failover dhcp server... I don't know why they don't do anything about it... buts it's absolutely worthless to get mad about it...

OK, after playing around some more I managed to get this working proper.  The documentation I listed above says to create the failover pools backwards. Perry, thanks for all of your help!

@Creighton: @Stoutman: You may be hitting some bandwidth limits by increasing your 'neighborhoods' total download bandwidth by increasing it due to using two lines instead of one. So your ISP may be kicking in some bandwith limiter now. Unfortunately that's not the case, as I can download files via HTTP from rapidshare at a continuous 1.5MB/s (maxing out both WANs) without problem. So maybe as familyguy hinted at above, RoadRunner is 'limiting' the bittorrent download speeds. That still could be the case though that you're hitting a neighborhood limit of some sort, just that it's one only limited to bittorrent. Since your download speeds didn't really improve with both WANs that is certainly feasible.

i cant seem to get my setup working how he did in the first place… can anyone tell me what im doing wrong ? i have my modem connected to my pfbox's wan and my wireless router connected to my pfbox'sw lan.. yet nothing is really working on the wireless router when i set it up like that =0

Resolved:  The paperwork I was getting my IP information from was one digit off the actual IP.  Pfsense was pulling an IP from Covad, and correctly displaying the IP.  The paperwork I was going off of to enter my A records was one digit off.  No big deal, a simple error, and an easy fix.  I apologize to whoever I was wrongly directing my traffic to :)

search for packet generator.