|
from the real server:
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1
default via 192.168.1.254 dev eth0 src 192.168.1.1
from the director:
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.9
default via 192.168.1.254 dev eth0
result of ip route get 0.0.0.0 from 192.168.1.14:
director:
local 192.168.1.14 from 192.168.1.14 dev lo
cache <local> mtu 16436 advmss 16396 hoplimit 64
real server:
RTNETLINK answers: Invalid argument
So the data is most likely getting 'trapped' somewhere on the real server?
On 4/26/06, Joseph Mack NA3T <jmack@xxxxxxxx> wrote:
> On Wed, 26 Apr 2006, Matthew Story wrote:
>
> > ok, could you explain what you want then? Do you want the output of a
> > route statement? A bit confused.
>
> yes
>
> or the output of
>
> `ip route show [table] `
>
> (if you've set up your IPs with ip addr add).
>
> or the output of
>
> `ip route get 0.0.0.0 from VIP`
>
> one explanation for your symptom is that the packets aren't
> getting out from the VIP
>
> 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!
> _______________________________________________
> 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
>
--
regards,
matt
|
