|
> default 66.208.187.126 0.0.0.0 UG 0
> 0 0 eth1
> default 66.208.187.126 0.0.0.0 UG 0
> 0 0 eth1
> default 66.208.187.126 0.0.0.0 UG 1
> 0 0 eth1
Well this is no good. Somehow you've got two default routes setup by one
process (metric 0) and one route setup by another process (metric 1). The
metric 1 is probably incorrect, and the extra metric 0 route is superflous
and should be gotten rid of.
When in doubt, tcpdump. You can also turn up debugging in ipvs to find out
what is happenning inside the process.
http://www.linuxvirtualserver.org/docs/sysctl.html.
<snip>
The /proc/sys/net/ipv4/vs/* Variables:
debug_level - INTEGER
It is only available when IPVS is compiled with the IPVS
debugging option.
The default value is 0. The higher value is set to
debug_level, the more debugging information is output in the
kernel messages. See the doc/debug-levels.txt (shipped in ipvs
source code) for more information about the debugging levels.
</snip>
P
---
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.654 / Virus Database: 419 - Release Date: 4/6/2004
|
