LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: transparent bridging ?

To: Joseph Mack <mack.joseph@xxxxxxx>
Subject: Re: transparent bridging ?
Cc: Joseph Mack <mack.joseph@xxxxxxxxxxxxxxx>, <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>, "John P. Looney" <john@xxxxxxxxxxxxx>
From: Julian Anastasov <ja@xxxxxx>
Date: Tue, 23 Apr 2002 20:01:08 +0300 (EEST)
        Hello,

On Tue, 23 Apr 2002, Joseph Mack wrote:

> Julian Anastasov wrote:
>
> > > will this solve the problem of the original posting (allowing clients
> > > to access a server, while the server is being built into a working
> > > LVS without breaking service to the clients)?
> >
> >         Yes, if I understand correctly the goal. Serge Sozonoff may be
> > was one of the first who tried bridging for something like this. But
> > note that I don't see that the Bridging can help something to the LVS
> > setups. Remember, it is transparent. You can do the same without
> > bridging.
>
> do you mean by the methods we use now in LVS-DR
> (eg sending the packets directly to a
> router from the realservers, or by using your martian patch)?

        If DIP is used as GW in real servers then even with
bridging you have to use the forward_shared flag. If uplink router's
IP is used as GW then we can run Bridging on the director if we want
to split the segment.

        Where is the trick: the real servers resolve with ARP their
GW IP and later send the packets to the resulting MAC. If GWIP is
a director's IP then we receive director's MAC and the traffic
reaches routing.

        So, if we want to put director physically between uplink
router and real servers and to use DR or TUN methods without
forward_shared flags we can do it by using Bridging and by using
the uplink router's IP as GW in the real servers. The only thing that
Bridging gives us is that we can use the uplink router's IP as GW
in real servers. The Bridging connects the two network segments.

> Joe

Regards

--
Julian Anastasov <ja@xxxxxx>



<Prev in Thread] Current Thread [Next in Thread>