|
could not see route tabble anymore when I typed route
Be sure to use "-n" options to route or netstat when looking at route tables
inside the cluster. Most of the time you'll not be able to resolve these
addresses with DNS and that's what "-n" means (don't resolve host names).
Just a guess... but maybe that is part of your problem here.
For example:
netstat -rn
--K
From: "Kim Le" <kiml@xxxxxxxxx>
Reply-To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Question about default gateway
Date: Wed, 15 Aug 2001 13:34:32 -0700
Hi All,
I am able to get LVS up and running using NAT. However I am having small
problem that hope any of you can help.
To have LVS NAT work for my setup, the server's default gateway need to be
LVS backend IP address. I configured default gateway using linuxconf but
it
didn't work (didn't see default entry in route table, sync_ack packet going
out).
I tried: route add default gw my_lvs_address
and could not see route tabble anymore when I typed route.
I am able to statically configure gateway for on individual client address
as:
route add client_address gw lvs_address (this one work)
Have any of you experienced default gateway problem before ? I appreciate
any help.
Kim
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
| 