@sullrich: Do this from a shell: touch /var/etc/use_pf_pool__stickyaddr It will use sticky address once the daemon is restarted. Sorry, I read it on the board a few days ago, but thought it was a server loadbalancing trick :) I will give it a try ! Thanks

I <3 u! ^_^

whoops, missed that one, sorry.

Now my Provider has confirmed that the subnetmask of 255.255.255.248 was and will correct assigned by the dialin router/server on provider side. Meanwhile my pfsense works with the mask 255.255.255.255 correct - mean the public ips on the bridged interface are working. 'Thanks

Hi All, I have been attempting to successfully configure Dual WAN connections to my PF Box. I have tried unsuccessfully for 4 months using every possible combination that I can find in the Forums and in Tutorials and WIKI and think of and I have not been able to get Dual WAN to route traffic correctly. Even in the Dual Wan configuration, only WAN1 passes traffic in both directions. Setup: LAN 1 IP: 192.168.1.1 (Default) WAN IP:  172.16.10.0 ROUTER1 IP: 172.16.10.0 ADSL: STATIC IP OPT1 IP: 182.165.20.0 (WAN2) ROUTER2 IP: 182.165.20.0 ADSL: STATIC IP The PFSense Box is NOT running as pppoe. ROUTER1 & ROUTER2 Configured to authenticate and NAT. If either are connected directly to a PC or Network, Traffic flows perfectly. With every attempt WAN2 ROUTER2 does not pass traffic through to ISP. I can ping the Router2 Ethernet Address, but not the ROUTER STATIC IP when WAN is disconnected. If WAN is connected to ISP and WAN2 is connected I can Ping the ROUTER2 STATIC IP and when doing a tracert its path goes through WAN1 and ISP account and back tracks to the ROUTER2 on the Internet side. If the ROUTER1 is Disconnected ROUTER2 Ethernet IP Can be pinged but No traffic is transferred and the Statci IP is unreachable. I looked at the Firewall Log but nothing unusual shown. For one brief moment after a new install Beta2, I was able to ping and tracert ROUTER2 Direct without going out to the internet. But as soon as I disconnected ROUTER1, ROUTER2 was unreachable. After a restart, neither Router1 or 2 passed traffic and a format and reinstall was necessary to enable traffic flow. I know that I must be missing something during the configuration that others are doing out of habit and not thinking to record the action. I have followed everything exactly and still dual wan / load balancing does not work for me. I dont know if others are having as much trouble as I am settinh up Dual Wan, but I would dearly like to see incorporated into PFSense a wizard to suit multiple config setups. EG: Select MultiWan, Failover, Carp, Load Balance etc during the initial setup so that it becomes fool proof and in the end a fully configured PFBox as the users needs. Just enter the details of the IPs of LAN / WAN / OPT1 / OPT2/ ETC and GW's and if it requires Load Balance. What am I doing wrong. CAN someone Please HELP? Kindest Regards, Craig Roy.

Prob fixed. I bridged the Lan to Wan and assign the first ipadress (Wan IP) on the Lan nic too. Now the static ips being routed.

did like You wrote, ping from LAN A to 10.x network is ok ping from LAN B to 10.x network destination host unreachable. i'll ask cisco gui to check routes also

Slightly offtopic in the same vein, anyone here have experience with OSPF on FreeBSD, in relation to pfSense I'm curious as to the difficulty level of whipping up a quick interface to it. (As though there is such a thing.  OpenVPN should teach me better than that….)

check out this article from the wiki: http://wiki.pfsense.com/wikka.php?wakka=OutgoingLoadBalancing you basically have to modify the rules and create rules for different traffic (like destination any ip port 25) and select the appropriate gateway at the bottom of the rules page of each rule. the loadbalancing pool is optional. you can skip this part from the wiki for what you want to do.

okay thanks, now the box is running already for 2 days… :)

i am getting back to my firewall project.  what is "next hop gateway (router) IP addres"?  i think that the answer is the IP address of either the aDSL or the cable modem.  The gateway shown by the interfaces page for the aDSL is a 10.x.x.x and its ip is 70.x.x.x(the interface page also lists DNS servers, curiously it shows 192.168.1.1 which is the ip address of LAN, why?).  For the cablem modem the interface page shows an ip address but no DNS servers. i want Lan1 and the DMZ to be assigned to the aDSL connection and the Lan to be assigned to the cable modem.  in the box that asks for "the next hop gateway (router) IP addres" what do i enter there?

i understand what ure trying to do, but with that what ure trying it wont go… This is to make subnetting a bit more understanding (if this is wrong, somebody correct me please): At first, you chose /30 (255.255.255.252) subnet, wich allows a maximum of 3+1=4 hosts (252 in bin is 11111100, so u have only 2 bits for hosts), i suggest u to use /28 (240) or smth like that, because i think u have more than 4 wifi clients a ? ;) So the easyest way would be to: 1.) But a atheros based wifi card ; 2.) But a Linksys wrt54gs, flash it with dd-wrt, set it in ap mode, disable wan, connect it to lan, set it up, and select AP isolation...

depending on what you have on the wan side. you could have two vlans tagged to the wan interface. then just tag your switch on a port for  each vlan and add a port for each of your wan connections. as scott said use two differnet subnets

LOL Fair enough.  I keep thinking ppl have these units right next to them, not on a water tower!

Doubt this will work at the moment.  You're stuck with FTP on WAN1.

I think I figured it out  ;D I now know why the dumb switch was dieing… I had 2 ports that were going to the same MAC address so it froze. the way to work around that would be to spoof a Mac on the Opt1 interface so the switch thinks it is a different device and doesnt get all confused. both vlan 10 and 11 pointed to the PF box even though the 2 ports couldnt talk to eachother the switch saw 2 ports with the same MAC. Yippy it works :) my AP is just being a transparent bridge. I can access both networks on the other side. the AP isnt even on the same network (the are in the 10.x network. thx alot peeps :)

Unhook pfsense and hook your machine up to the connection to see if the connection still goes down once a day.  You need to narrow down if pfSense is the issue or not.

monitoring does not work atm so it doesn't matter. it will be used for checking if the connection is still allive. you can ping the gateway for example or even an ip of google.com. if the ping fails the connection is assumed dead and will pe temporarily taken out of the pool until the ping is successfull again.