Dual wan and lan, load balancing makes routes wacky

hirschma

Can't make load balancing work - probably something simple that I'm missing…

My settings:

WAN: IP: ww.xxx.86.9/24 gw: ww.xxx.86.1
WAN2 (opt2): IP: ww.xxx.77.14/24 gw: ww.xxx.77.1

Note: this is how my ISP does it - 8 bit mask for one static IP address.

LAN: 192.168.1.1/24
LAN2 (opt1): 192.168.2.1/24

All of this works great with one WAN connection; hosts on each LAN segment can ping each other, etc.

I tried the docs at http://doc.pfsense.org/index.php/MultiWanVersion1.2 best as I could translate them to my setup. When I set either lan segment to use the loadbalancing gateway, the following happens:

I cannot ping the router from any client on the lan segments - it tries to ping what appears to my ISPs router (same on the 192.168.1.0 network):

#ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
From ww.xxx.64.1 icmp_seq=6 Destination Host Unreachable
From ww.xxx.64.1 icmp_seq=9 Destination Host Unreachable
From ww.xxx.64.1 icmp_seq=16 Destination Host Unreachable
From ww.xxx.64.1 icmp_seq=18 Destination Host Unreachable

Note that if I do a traceroute when things are working, the first hop looks like this:

Traceroute output:

1 r1-n64.myisp.com (ww.xxx.64.1) 174.883 ms 184.424 ms 178.195 ms

load balancing works for http accesses out to the internet,
ftp gets various errors. directories cannot be displayed half the time. Hmmm...

Anyone have any clues on how to set this config up?

bobabc

I'm having a similar problem. Although instead of having routers connected in front of each wan. I have two cable modems. I've changed the lan ips on the cable modems. One is 192.168.100.1 and the other is 192.168.100.2. I'm trying to get the router to use one wan connection whenever I try and connect to one of the modems and the other when I try and connect to the other. However when I try and setup the rules. It doesn't seem to work. However I'm not exactly sure what I'm doing.

I can connect the the modems sometimes by trying to connect over and over again until it trys and connects using the right wan. This has proven to be a headache.

Can anyone tell me how I need to configure the rules so that the router knows which wan port to use for which modem.

Hirschma > I believe your ftp issue can be solved by going to Advanced settings and enabling sticky connections.

Pootle

@bobabc:

I'm having a similar problem. Although instead of having routers connected in front of each wan. I have two cable modems. I've changed the lan ips on the cable modems. One is 192.168.100.1 and the other is 192.168.100.2.

bobabc, you need to get your 2 modems into separate subnets: something like
modem 1 192.168.100.1
modem 2 192.168.101.1

both with /24 mask . Then it should all work fine.

deresistance

I have delt with this to a great degree.

With FTP it is best to force FTP through 1 pipe or the other. I found that with "passive' FTP connections the load balancer pushes port 21 out 1 pipe and then the other ports try to connect on the other pipe. The remote server doesnt like this obviously.

Some services do this. I have no idea if there is a fix or not.