Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux Virtual Server: Users
Re: [lvs-users] One realserver must connect to services to other realservers (routing problem).
 

Index | Next | Previous | View Flat


hofmarkus at gmail

Aug 26, 2011, 2:58 AM


Views: 495
Permalink
Re: [lvs-users] One realserver must connect to services to other realservers (routing problem). [In reply to]

Hello Léon,

>>/ REALSERVER (A) REALSERVER (B)/
>/> (192.168.0.10) (192.168.0.10)/


Yes i have made a typo. Correct is:

Loadbalancer (LVS) (IP 192.168.200.15)
^ |
| |
| |
| |
| V

REALSERVER (A) REALSERVER (B)
(192.168.0.10) (192.168.0.20)



>You probably made a typo here since they both have the same RIP. Anyway,
>in LVS-NAT you indeed set the default gateway to the VIP of the
>director. On a /24 network you would set it to 192.168.0.x


>/> The problem is, that realserver B see that the question for the service/
>/> comes from the network 192.168.0.10 and then goes/
>/> directly to A, but couldn't work out the answer, because realserver A/
>/> ask 192.168.200.15 and not 192.168.0.10./

>That's odd. Why would rs A 'ask' 200.15? Why not simply connect to rs B?
>In that case the SRC IP would be the RIP from rs A.

>Or maybe i'm misunderstanding your question and you actually want to
>connect from rs A to VIP:service, which then redirects it to a rs?


The problem is that we have a lot of different services and DNS-Names
in our REALSERVERs. We have more than 10 Realservers and more than 50 different
DNS-Names (VIP:service) (with different VIP-IPs) on that.

For example:
Realserver A must go to meteo.example.com (192.168.200.15) (VIP: service), which then redirects it
to the realserver B, but i do not receive on realserver A answer from realserver B.
I go from outside the realserver-range it isn't a problem.
Alredey my trick is to insert a different DNS entry in the hostfile of realserver A for meteo.example.com (192.168.0.20)
and then i haven't problems.
My problem is that for me isn't easy to insert for all our services on every realserver hostfile a diffent DNS-entry.
Exist not some ohter way to work around for this problem, like

------
If the realserver go outside for services i have insert a SNAT on
POSTROUTING on the LVS.
Like:
http://www.duffau.net/LVS/LVS-HOWTO.LVS-NAT.html#client_on_LVS-NAT_realserver
Insert PREROUTING something??
-----

Thanks in advance!
regards,
Markus


<http://lists.graemef.net/mailman/listinfo/lvs-users>

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users [at] LinuxVirtualServer
Send requests to lvs-users-request [at] LinuxVirtualServer
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

Subject User Time
[lvs-users] One realserver must connect to services to other realservers (routing problem). hofmarkus at gmail Aug 25, 2011, 6:03 AM
    Re: [lvs-users] One realserver must connect to services to other realservers (routing problem). leon at linux Aug 26, 2011, 12:56 AM
        Re: [lvs-users] One realserver must connect to services to other realservers (routing problem). jmack at wm7d Aug 26, 2011, 5:26 AM
            Re: [lvs-users] One realserver must connect to services to other realservers (routing problem). leon at linux Aug 26, 2011, 5:44 AM
    Re: [lvs-users] One realserver must connect to services to other realservers (routing problem). hofmarkus at gmail Aug 26, 2011, 2:58 AM
        Re: [lvs-users] One realserver must connect to services to other realservers (routing problem). graeme at graemef Aug 26, 2011, 4:06 AM
        Re: [lvs-users] One realserver must connect to services to other realservers (routing problem). jmack at wm7d Aug 26, 2011, 5:21 AM
    Re: [lvs-users] One realserver must connect to services to other realservers (routing problem). hofmarkus at gmail Aug 26, 2011, 7:41 AM

  Index | Next | Previous | View Flat
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.