|
On Wed, 2009-10-28 at 09:13 -0700, partysoft wrote:
> [root@linux 10.1.228.234]# arping 10.1.228.235 < from the director
> ARPING 10.1.228.235 from 10.1.228.234 eth0
> Unicast reply from 10.1.228.235 [00:24:5D:24:61:AB] 0.550ms
These are on the same network; the reply will come direct.
> from the external ip
> -bash-10.1.239.163 # arping 10.1.228.234
> ARPING 10.1.228.234 from 10.1.239.163 eth0 < doesn't match the real mac of
> the 10.1.228.234
> Unicast reply from 10.1.228.234 [00:0A:F3:82:3A:00] 1.179ms
>
> -bash-10.1.239.163 # arping 10.1.228.235
> ARPING 10.1.228.234 from 10.1.239.163 eth0
> Unicast reply from 10.1.228.234 [00:0A:F3:82:3A:00] 1.179ms < how can the
> reply be from the same MAC as the previous ping??? and it's not even the
> real one..
These are not on the same network; the reply will come via a router. The
source MAC in the reply packet will always be that of the router in this
context.
MAC addresses do not propagate beyond a device which separates switching
domains - this is a fundamental networking property.
I'm having some trouble understanding what you're trying to achieve, and
it appears that you're flailing around trying to get an LVS working
without really waiting for people to help. It's difficult for anyone to
help if you keep moving your setup around.
Very simple question: have you tried to setup a basic LVS with one
director and one realserver yet? If you do that, using ipvsadm, then you
will get a better feel for what's required and a better understanding of
the underlying principles.
Graeme
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
