|
For now I am just trying to get a simple html page to load. I am
listening on all IP's and I did restart apache after adding the Virtual
IP to my apache real server just to make sure it was listening on that
IP now as well.
I am using a virtual server setup (many sites on one IP) in apache, if
it matters.
Anyone have any thoughts about my direct routing concerns and the setup
for that?
On 3/30/2010 5:11 PM, Anoop Bhat wrote:
> I also had this issue at one point in time.
>
> Are you trying to do SSL virtual servers?
>
> I thought I fixed my issue by ensuring that the real apache servers were
> listening on all IP addresses on port 80/443.
>
> Anoop Bhat
> Systems Administrator
> Trustwave
> 70 W. Madison
> Chicago, IL, 60602
> O: 312.873.7446
> C: 312.925.3271
>
>
>
> ________________________________
> From: James Chase<james@xxxxxxxxxxxxxxxxxxx>
> Reply-To: "LinuxVirtualServer.org users mailing
> list."<lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
> Date: Tue, 30 Mar 2010 16:03:57 -0500
> To:<lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: [lvs-users] CentOS 5 apache real servers don't respond
>
> I am trying to setup LVS on CentOS 5.4 using piranha/pulse. Ideally (I
> think) I would like to do direct routing so that I can still have my
> real servers (apache machines) able to connect directly to the internet.
>
> However, I'm not able to get the apache servers to respond correctly to
> the Virtual IP requests. From tcpdump it seems like the requests are
> being forwarded to the real server from the LVS but I don't get the page
> returned to me in my browser, and I don't see the request being sent out
> in tcpdump on the apache real server. I believe I have the virtual IP
> setup correctly on the real server.
>
> As a caveat though, if the real server responds and the apache server
> response goes out on it's external IP (which would be different than the
> Virual IP) -- isn't my firewall going to block that connection since it
> is not the IP of the connection I originally tried to establish?
>
> I also tried NAT briefly but was not able to get a connection there
> either. Is NAT the suggested way of doing this? It seems like indirect
> routing would be inconvenient/difficult if you had many virtual servers
> on the real apache servers and multiple SSL sites running as well.
>
> Thanks,
> James
>
>
> _______________________________________________
> 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
>
>
>
>
> _______________________________________________
> 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
>
_______________________________________________
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
|
