Outbound loadbalancing beta 3

charles.regan · Apr 17, 2006, 10:25 PM

doesn't works and/or works like ****

gateway1 201.120.48.1
gateway2 201.120.134.1
gateway3 201.120.51.1

if I ping 201.120.48.1 I can see the traffic passing in gateway3 to get to it.

Apr 17 18:18:27 slbd[32073]: Switching to sitedown for VIP 127.0.0.1:666
Apr 17 18:18:25 php: : There were error(s) loading the rules: /tmp/rules.debug:170: syntax error pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [170]: pass in quick on $lan route-to { } round-robin route-to ( Loadbalance ) from 10.0.0.0/16 to any keep state label "USER_RULE: Load Balance"
Apr 17 18:18:22 last message repeated 9 times
Apr 17 18:18:02 last message repeated 14 times
Apr 17 18:17:27 slbd[32073]: Switching to sitedown for VIP 127.0.0.1:666

hoba · Apr 17, 2006, 10:28 PM

We just fixed some things and it really SHOULD work with beta3. If there are no last minute bugs found in the next hour beta3 will be released.

charles.regan · Apr 17, 2006, 10:58 PM

big problem here.

rules.debug:
pass in quick on $lan route-to { ( rl3 201.120.51.1 ) , ( rl3 201.120.51.1 ) } round-robin from 10.0.0.0/16 to any keep state label "USER_RULE: Load Balance"

if i go into loadbalancer my pool is gateway2 201.120.134.1 and gateway3 201.120.51.1

something is wrong

charles.regan · Apr 17, 2006, 11:06 PM

what i can see is that it only takes the last gateway in the pool

billm · Apr 17, 2006, 11:23 PM

@charles.regan:

what i can see is that it only takes the last gateway in the pool

What are the monitor IPs?

–Bill

hoba · Apr 17, 2006, 11:25 PM

Please wait for beta3. I tested that under several conditions and this feature should now really work as expected (several fixes where made even after the latest snapshot).

billm · Apr 17, 2006, 11:28 PM

@billm:

@charles.regan:

what i can see is that it only takes the last gateway in the pool

What are the monitor IPs?

Also, what does your routing table look like?

–Bill

charles.regan · Apr 17, 2006, 11:40 PM

I think i'Ve found the problem.
my monitor ip where all the same for all gateway.

i've checked the routing table and the route for the monitor ip was rl3.
that should explain the problem. weird that it worked since version 0.6.

what should be the monitor ip ?
if my gateway is 201.120.51.1, can I use 201.120.51.1 as the monitor ip ?

thanks

charles.regan · Apr 17, 2006, 11:45 PM

works good now / monitor ip same as gateway.

thanks folks

hoba · Apr 18, 2006, 12:11 AM

@charles.regan:

I think i'Ve found the problem.
my monitor ip where all the same for all gateway.

i've checked the routing table and the route for the monitor ip was rl3.
that should explain the problem. weird that it worked since version 0.6.

what should be the monitor ip ?
if my gateway is 201.120.51.1, can I use 201.120.51.1 as the monitor ip ?

thanks

It will add a route for the monitor IP to the refferenced gateway. If you enter always the same monitor IP for all gateways it will overwrite the previous route and you'll end up with only one route. The monitor IP should be different for each gateway. You should set the monitor to a hop near you at the appropriate interface. Depending how your connection is set up the gateway IP or the first hop after your gateway might be a good choice.