On Wed, 26 Apr 2006, Matthew Story wrote:
result of ip route get 0.0.0.0 from 192.168.1.14:
real server:
RTNETLINK answers: Invalid argument
this was what I was after
So the data is most likely getting 'trapped' somewhere on the real server?
yes. The traceroute output shows your networking isn't
correct.
The commands you ran to set up the routing etc on the
realserver looked like typical distro commands to make setup
of IP look like Windows setup. eg
http://www.austintek.com/LVS/LVS-HOWTO/mini-HOWTO/#ifup
there's a script in the mini-HOWTO for setting up
realservers for LVS-DR
http://www.austintek.com/LVS/LVS-HOWTO/mini-HOWTO/#lvs_dr_by_hand
try running it after bringing up only the RIP and the RIP
network.
Since no-one is using the hidden method anymore for
controlling the arp problem, you'll have to substitute your
arp_ignore equivalents
There's an equivalent script for the director if you need
that.
Joe
--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!
|