|
I guess I thought that's what I was doing with ssh.
-A -t w.x.y.z:22 -s wlc -p 10360
-a -t w.x.y.z:22 -r 192.168.1.3:22 -m -w 1
-A -t w.x.y.z:4444 -s wlc -p 10360
-a -t w.x.y.z:4444 -r 192.168.1.3:4444 -m -w 1
-A -t w.x.y.z:1099 -s wlc -p 10360
-a -t w.x.y.z:1099 -r 192.168.1.3:1099 -m -w 1
-A -t w.x.y.z:8080 -s wlc -p 10360
-a -t w.x.y.z:8080 -r 192.168.1.3:8080 -m -w 1
Those are some of the rules I have in /etc/sysconfig/lvs. Runninb
ipvsadm -Ln shows they are in effect. If I try to ssh from a machine on
the 192.168.1.0/24 (192.168.1.5) subnet to w.x.y.z, I never get a login
prompt. Is there something inherently different about this using telnet
instead of ssh? (I don't have a telnet server, so would have to set that up)
Joseph Mack wrote:
Justin Georgeson wrote:
If I'm reading it right, I think we already tried that.
have you recreated the problem using telnet as the LVS'ed service?
Joe
--
Justin Georgeson
UnBound Technologies, Inc.
http://www.unboundtech.com
Main 713.329.9330
Fax 713.460.4051
Mobile 512.789.1962
5295 Hollister Road
Houston, TX 77040
Real Applications using Real Wireless Intelligence(tm)
|
