Load balancer configuration problems
-
Hi All,
I install pfSense inside Hyper-V on Windows Server 2008 R2 Enterprise.
I try to configure the load balancer on pfSense, but it doesn't work.Here's my configuration.
My local computer IP address: 192.168.0.55
Web server 1: 192.168.0.74
Web server 2: 192.168.0.87
Default gateway: 192.168.0.1LAN IP address: 192.168.0.16 /24
WAN IP address: 192.168.0.17 /24
After finishing configuration, I try to connect to 192.168.0.17, which is the address for load balancing, I get no response from the load balancer.
I check out the states log which presents as the following.
I can use telnet 192.168.0.74 80 and telnet 192.168.0.87 80 commands to connect to the web servers from my local computer.
However, I CANNOT use telnet 192.168.0.17 80 command to connect to the load balancer.
Any idea?
-
Don't configure LAN and WAN on same subnet unless you are using bridge.
configuring a balancer on same subnet you are will not work.
The web server will receive your request via firewall and will try to respond directly to you…
192.168.0.1(you) -> 192.168.0.17(balancer) -> 192.168.0.74(server)
the response will be
192.168.0.74(server) -> 192.168.0.1(you) -> reject! You asked 192.168.0.17 for a page, not 192.168.0.74.
-
Don't configure LAN and WAN on same subnet unless you are using bridge.
configuring a balancer on same subnet you are will not work.
The web server will receive your request via firewall and will try to respond directly to you…
192.168.0.1(you) -> 192.168.0.17(balancer) -> 192.168.0.74(server)
the response will be
192.168.0.74(server) -> 192.168.0.1(you) -> reject! You asked 192.168.0.17 for a page, not 192.168.0.74.
Now I configure WAN of the load balancer to 192.168.2.2 with the default gateway 192.168.2.1.
However, I still get no response from 192.168.2.2 and I get the following in the states log.
tcp 192.168.0.74:80 <- 192.168.2.2:80 <- 192.168.2.1:51333 CLOSED:SYN_SENT
tcp 192.168.2.1:51333 -> 192.168.0.74:80 SYN_SENT:CLOSEDI check the web server (192.168.0.74), there's a connection between it and the default gateway (192.168.2.1).
Any suggestion?