Re: hi..

Hi Felix

> primary = 148.213.22.201
> backup =  148.213.22.202
> nat_router = 192.168.1.254 eth1:1
> virtual vs1 {
>      address = 148.213.22.200 eth0:1
>      load_monitor = ruptime

> 1.  in the file log (router 1) . send me error.. why ?
> 
> router1 nanny[814]: bad load average returned: router1       up
> 7:07,     0 users,  load 0.00, 0.00, 0.00
> router2       up     22:14,     0  users,  load 0.00, 0.00, 0.00
> server1     down     22:20
> server2       up     2  2:15,     0 users,  load 0.00, 0.00, 0.00
> server4     down     21:48
> server5      up     22:14,     0 users,  load 0.00, 0.00, 0.00
> sever3        up     22:15,     0 users,  load 0.00, 0.00, 0.00

Piranha is broken when it gets to find out the avg load using ruptime.
Use an alternate method or dig the list to find out a patch I submitted
months ago.

> ping outside-InternetIP  not respond. or very very slow.

Real servers are not susposed to be able to access the internet. If you
do need this feature, you'll have to masquerade the appropriate traffic
on the directors (iptables -t nat is your friend).

> 3. in the gui-piranha interfacce. configure lvs and works find, but i
> not understend, the seccion
> 
> CURRENT LVS ROUTING TABLE
> 
>  IP Virtual Server version 0.9.7 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
>   -> RemoteAddress:Port          Forward Weight ActiveConn InActConn

Ooops, no real server. From the director (148.213.22.201), can you
access (http) your real server. I mean, does lynx http://server[1234]/
work ?

> 4.  the router NAT is 192.168.1.254  is set to

fine

> if real server set router wich ip 192.168.1.254 why not work.

What do you mean ? Can all real servers ping 192.168.1.254 ?
Did you echo 1 > /proc/sys/net/ipv4/ip_forward ?

> when type command  route in the router1  view this
> 
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref Use Iface
> router1         *               255.255.255.255 UH    0      0   0   eth1
> cluster1        *               255.255.255.255 UH    0      0   0   eth0
> 192.168.1.0     *               255.255.255.0   U     0      0   0   eth1
> 148.213.22.0    *               255.255.255.0   U     0      0   0   eth0
> 148.213.0.0     *               255.255.0.0     U     0      0   0   eth0
> 127.0.0.0       *               255.0.0.0       U     0      0   0   lo
> default         148.213.22.1    0.0.0.0         UG    0      0   0   eth0
> default         192.168.1.254   0.0.0.0         UG    1      0   0   eth1

What the hell is this ? 192.168.1.254 should not be a default gateway on
the directors. Why do you have twice 148.213 with different netmasks ?
What is cluster1 ? Why if router1 routed thru eth1 ?

-- 
Sébastien Bonnet
  Centre de contacts - Experian France