Dual WAN (ADSL and Wireless WAN) to Single LAN
-
Hey guys,
I have searched through the forums and appear to have come up short. I have seen lots of posts relating to multihomed WAN setups using fail over and aggregation of multiple Internet links, which is not what im after, so, hopefully ive come to the right place!
The Setup:
pfSense 2.0.1 running bare metal on a P4 1.5ghz machine
3 seperate NICs
1x PPPoE ADSL Internet connection, Terminated as WAN on pfSense
1x LAN Connection, Terminated as LAN on pfSense
1x Wireless WAN, Terminated as OPT1 in pfSenseThe ADSL is being passed through to the LAN successfully from PPPoE via NAT. This has been working fine since Day 1. Now, I have connected to a community Wireless WAN (that spans quite alot of the metro area here in Adelaide), which is being terminated into a third NIC in pfSense as OPT1.
I have assigned the correct IP Address to OPT1 and can get pfSense to talk to the two networks that are out there (10.11.0.0/11, the wireless WAN and 192.168.1.0/24, the AP device that connects to the Wireless, added as a virtual IP in pfSense). I have added a route into pfSense for the WirelesWAN to talk out over there, which i can do only from the pfSense box.
Ideally, what I would like to have setup, is the single LAN (10.0.0.0/24) connected to both WANs and pfSense doing the routing out to both. In my perfect world, the pfSense should be able to act as the LAN Gateway and then route to either the Internet or the WirelessWAN as it needs to. Ideally, this would also have a layer of NAT as well to allow some form of access control for the Wireless side of things into services that are running on the LAN.
I guess the short version is, access both WANs, from my single LAN with no aggregation, failover etc. as they need to be treated as two seperate networks.
Hopefully, that is all the info but by all means, if you think you need more, please let me know!
Thanks for taking the time to read.
Cheers,
IceaTronic
-
Ok, so ive managed to get some sleep and it seems as though the only thing that I had to do to get this to work properly, is manually add in the gateway for the OPT1 link. Once I did this, I was then able to get out to the Wireless WAN from inside my LAN. Further more, settings up DNS Forwards for everything .wan (their TLD that they use) was a sinch!
So, thanks for giving me a space to write the issue out as it seems as ive managed to answer it my self. Hopefully it proves useful to others that may, or may not, find them selves in the same situation one day.
-
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.