[SOLVED] Second WAN will not work
-
Hello Chaps, my first post! YAY! :D
I am loving pfSense, really great stuff! I am just having one problem. I am trying to load balancing two WAN connections and I'm so excited! However, what ever WAN I set up second, it will not work.
What I mean is that I have two ADSL routers with static IPs:
Router 1: 62.173.77.65
Router 2: 62.173.79.105So when I create the first WAN and point it to the Router 1, all is good. When I create the second WAN and point it to Router 2, it won't connect to it. (I have restarted several times after doing this) I then delete the WANs and start again.
This time with the first WAN pointing to Router 2, and all is good. Then when I create the second WAN and point it to Router 1, it won't connect to it.
Catch my drift? What ever gateway I set up first, works. The second gateway I set up, will not work, no matter which router it is :( ???
Could someone please enlighten me?
Thank you!
-
Welcome! :)
More information is needed.
Are these routers doing NAT or bridging the public IP to pfSense? If they are doing NAT are they on different subnets?When you say 'won't connect to it' what exactly do you mean?
Steve
-
Welcome! :)
More information is needed.
Are these routers doing NAT or bridging the public IP to pfSense? If they are doing NAT are they on different subnets?When you say 'won't connect to it' what exactly do you mean?
Steve
Thanks Steve!
Well, instead of typing it all down, I have added some JPEGs to answer your questions. But, no NAT is being used and as you will see from the pics, I have 4 IPs my ISP has assigned to me, and by 'won't connect to it' I mean that it will not ping.
If I set up the 'PublicRouter' first, it pings, and then I set up the 'GrangeRouter'… won't ping. ???
Please (pretty) let me know what you think.
Ta,
PabloPS: This pfSense FW is replacing current Endian FW which are using the gateways just fine, so I know they work. :P
-
Hmm. OK.
I suspect the problem is that both WANs have the same gateway (at your ISP) which is unfortunately an invalid configuration.
Alternatively both monitor IP's could be the same. Not sure if that's a problem or not.
Edit: They aren't.Your setup is relatively complex.
Steve
Edit: Neither of those things seems true. Hmm.
-
So by the sound of things, my second router need to come from a second ISP? :-\
Am I SOL? :'(
-
Not necessarily.
You can work around the limitation by, for example, NATing one connection.As I said your connection is unusual. If you had two bog standard DSL connections, using dynamic, ISP assigned addresses then they would likely share a gateway at the ISP. This causes a problem with failover/load balancing. You can't have two routes to the same gateway.
The exception to this is if you're using PPPoE.Since you are using your own IPs things are different, and to be honest beyond my experience. It seems odd apinger can't ping your other router when it's on the same subnet. Likely it's trying to ping on the wrong connection for some reason.
Do you have DNS servers specified on both connections?How are the connection setup? Static?
Since you are using one ISP you might investigate if they offer DSL bonding which would both solve these problems and give you a much better connection.
Steve
-
Hi Steve,
Thank you so much for all your tips! And the good news is that now its working. I cycled through the IPs which my ISP provided and it seems that it is all working fine now. So you were right about the IPs!
Thanks so much again! pfSense FTW!
Cheers,
Pablo -
Hmm, well I'm glad you're up and running but I have no idea why it worked/didn't work. ::)
Steve
