|
Hello,
> Yesterday we stumbled on the problem with certain versions of
> 'ifconfig' not displaying the aliased interfaces (eth0:110)
> seperate from eth0.
Please read [1] to understand why things like that happen. In short:
ifconfig and route are a deprecated tools and are not 100% compatible
with iproute2 if mixed.
> This caused some problems in the remove_old_vip() function of the
> rc.lvs_nat script. I think I've stumbled onto a few more issues
> (some may be related). I am setting up VS-NAT with two NICS (two
> seperate networks).
I'm sure, Joe will be more than happy to help you here.
> 1) In setup_director_vip() the following fails. I think the $ROUTE
> command has a problem with the aliased device. Changing to
> $SHORT_DIRECTOR_VIP_DEVICE seems to have worked. $ROUTE add -host
> $VIP dev $DIRECTOR_VIP_DEVICE
Do you intend to route over a 'alias'd interface' IP (secondary IP)?
> 2) As mentioned in a previous thread, I am losing my default gateway
> on the director. Looking at the rc.lvs_nat script that was
> generated, the default gateway is removed but never put back in.
> Adding "DEFAULT_GW=<my gateway IP>" to the script works.
Again, this is something for Joe.
> 3) Finally, when I initiate a connection from my realserver out to
> the internet (because my service requires a connection initiated by
> the realserver), the packets are routed throught the director, but
> are not NATed. The clients are seeing packets with the RIP1
> address.
Care to show an output of ipvsadm -Ln?
[1]http://marc.theaimsgroup.com/?l=linux-virtual-server&m=100325252915919&w=2
Cheers,
Roberto Nibali, ratz
|
