|
Hello Graeme,
My provider does not allow private LANs. To make this work ASAP would
setting up LVS/Tunneling make a difference? At least it would solve the 24,
32 problem? Or would it be easier to get an IP range 91.121.xxx.xxx for the
VIP?
Thanks,
Antoni
-
I was just typing up a massive reply full of questions, but I think I
see your problem.
The DIP is 91.121.30.157/24
The VIP is 87.98.225.39/32
The RIP is 91.121.20.31/24
The director has a default gw of 91.121.30.254
The director *does not have a direct route to 91.121.20.0/24*. Therefore
the director sends the incoming SYN back to its' default gw; it is then
passed back to the director, back to the gw, back to the director (and
so on) until the TTL decrements to 0 and everyone gets "time exceeded
in-transit" errors.
In LVS-DR, the director *must have a direct route to the realservers* -
or, at the very least, one which does not re-traverse the inbound
gateway.
Please read http://www.linuxvirtualserver.org/VS-DRouting.html making
special note of the image which says that the director and realservers
"Must be in a physical segment".
Also from
http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.LVS-DR.html
"LVS-DR setup and testing is the same as LVS-Tun except that all
machines within the LVS-DR (ie the director and realservers) must be on
the same segment (be able to arp each other). This means that there must
be no forwarding devices between them i.e. they are using the same piece
of transport layer hardware ("wire"), eg RJ-45, coax, fibre (there can
be hub(s) or switch(es) in this mix). Communication within the LVS is by
link-layer, using MAC addresses rather than IP's."
Sort that out first. Then you'll work.
Graeme
|
