lvs-users
|
To: | "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx> |
---|---|
Subject: | Re: [lvs-users] keepalived: SSH getting "No route to host" |
From: | Gerry Reno <greno@xxxxxxxxxxx> |
Date: | Thu, 20 Sep 2007 10:00:58 -0400 |
I looked through the howto's and did not see anything showing how to put ssh on an alternate port. If LVS-DR cannot be used to map from an alternate port back to 22 then is my only choice a firewall rule? I was hoping that I could leave sshd running on port 22 on the director and have an incoming port 33322 request translated by the director to port 22 outgoing to the realserver. But I can see that this is a problem because the director does not get the opportunity to remap the response back to 33322. So is there no way to do this and still have sshd on the director listening on port 22? Gerry |
Previous by Date: | Re: [lvs-users] keepalived: SSH getting "No route to host", Joseph Mack NA3T |
---|---|
Next by Date: | Re: [lvs-users] keepalived: SSH getting "No route to host", Graeme Fowler |
Previous by Thread: | Re: [lvs-users] keepalived: SSH getting "No route to host", Joseph Mack NA3T |
Next by Thread: | Re: [lvs-users] keepalived: SSH getting "No route to host", Graeme Fowler |
Indexes: | [Date] [Thread] [Top] [All Lists] |