@marvosa: Are you getting internet on WLAN2? So on WLAN2, you have created a 2nd AP configured with the 192.168.3.0/24 subnet on the same card for people to connect to? (a network map would be helpful) Can you post the routing table on PFsense? One WLAN should be for internal use and the other one should be later a guest account with internet access only. But until now both are full functional with * rules and internet is working for both of them. The WAN1 sould be later the main internet connection & WAN2 the backup internet connection. WAN2 i also used later for the guest access. For testing I only have WAN2 connected, because our other router is still active :) IPv4 Destination Gateway Flags Refs Use Mtu Netif Expire default 192.168.1.1 UGS 0 7946 1500 vr2 8.8.8.8 192.168.1.1 UGHS 0 372 1500 vr2 10.17.60.0/24 link#1 U 0 734 1500 vr0 10.17.60.251 link#1 UHS 0 0 16384 lo0 1.2.3.224/30 link#2 U 0 0 1500 vr1 //  not used WAN1 IP modified 1.2.3.226 link#2 UHS 0 0 16384 lo0 // not used WAN1 IP modified 127.0.0.1 link#6 UH 0 155 16384 lo0 192.168.1.0/24 link#3 U 0 20687 1500 vr2 192.168.1.2 link#3 UHS 0 0 16384 lo0 192.168.2.0/24 link#9 U 0 4893 1500 ath0_wlan1 192.168.2.1 link#9 UHS 0 0 16384 lo0 192.168.3.0/24 link#10 U 0 8444 1500 ath0_wlan2 192.168.3.1 link#10 UHS 0 0 16384 lo0

I've experienced this with a Gennet Oxygen router and a Pirelli router. At least for the Pirelli one, replacing it is not an option - the router is provided and controlled by the ISP

Got it: set any username and password in the ppp connections, just don't leave the fields empty. leaving the fields empty fails ppp, but if i set any password and username, it works. took me quite a while to figure :( topic can be closed

No problem, that's a common setup, lots of people like to keep their VoIP completely separated from other Internet traffic. It's a good way to go. It's an easy setup too, generally takes me about 30 minutes start to finish to configure that from scratch, and anyone who's comfortable with similar classes of firewalls should be able to do it within a couple hours tops the first time.

Step By Step Screenshots… Filter Rules are very important. [image: Getways.JPG] [image: Getways.JPG_thumb] [image: Getways_Group.JPG] [image: Getways_Group.JPG_thumb] [image: Floating_Rule.jpg] [image: Floating_Rule.jpg_thumb] [image: Floating_Rule_ADV.jpg] [image: Floating_Rule_ADV.jpg_thumb] [image: LAN_Rule.jpg] [image: LAN_Rule.jpg_thumb] [image: Status.jpg] [image: Status.jpg_thumb]

Bump.  Anyone?  I'm going out to pickup a hub today.  I'm going to try to figure out which is the last device to pass the packets by running a packet capture through the hub at different points in the network.  Also, this network is a bit new to me and I've realized that I left one switch out of the equation.  There is a switch between the Fatpipes and the Sonicwalls. Cable internet&2 bonded T1s (these have a block of public IPs, xxx.xxx.xxx.161 - xxx.xxx.xxx.190) -> Fatpipe WARP 3.0 (Primary and Failover) -> Cisco 2950 Switch -> Sonicwall Pro 4060 (Primary and Failover) -> LAN

Pfsense not support both WAN on DHCP. Try one of with ststic ip.

Both have rules "Allow All-to-All" The problem is with the fragmented packets, that pfsense blocks by default (which is the correct thing to do)

Success! I had another NIC with an atheros chipset lying around. That's all it took. I guess that's what I get for blazing ahead without checking the compatibility list. It turned out to be the card even though it didn't seem like a driver problem. OPT1 is fully operational now that it's reassigned to an Airlink 101 awlh4130. thx, R9

@ManuelRighi: On the remote server farm, arriving with IP 100.100.100.0 (the WAN1 ip) Are you saying the remote server farm is seeing connections coming from your WAN1, and you want them to come from the LAN IP via WAN2? If so, then you need to follow this section of the how-to to create a LAN pass rule to direct LAN traffic to the remote servers via the proper gateway: http://doc.pfsense.org/index.php/Multi-WAN_2.0#Firewall_Rules @ManuelRighi: but I need to arrive with LAN IP If your LAN IP really starts with 10. then you can't route it to your remote servers. You will have to use Outbound NAT (automatic or manual), and the servers will see the requests coming from WAN2 IP.

If you setup firewall rules on LAN interface you are able to chose the gateway this traffic should use. In some cases you may need this.

K, thanx guys.  I'll try this once I get my pfSense working AGAIN. Second time it's broke on me. You can view my other thread about my pfSense wigging out here: http://forum.pfsense.org/index.php/topic,49331.msg261712.html#msg261712 Once I have it back in a working state I'll check this out again and work out the kinks of my ruleset. Thanx again for the help!

Thanks for the replies. I will try to recreate all the VLANs and rules because the previous setting is to complicated I think. I'm still learning pfSense and love the power so far  ;D

You can do multi-WAN. If you're looking for someone to write a comprehensive guide to doing multi-WAN based on a forum post that's so generic someone could write a 500 page book to cover your scenario as a response, sorry but it's not going to happen. Though the book has already been written. http://pfsense.org/book