|
The only ip_vs modules listed were ip_vs
Also, if you can't connect to the port on the director it most likely means
somethings not setup right. I could never connect to ports unless everything
was setup properly on the director and the real server.
Can you telnet from 192.168.1.2 to 192.168.2.5:25 successfully ?
Kris
-----Original Message-----
From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Andy Shinn
Sent: Friday, 5 November 2004 3:07 PM
To: LinuxVirtualServer.org users mailing list.
Subject: Re: LVS-Tun not working correctl. No listening sockets?
Oh thanks Kris!
That makes me feel better =)
What ip_vs modules do you have listed in lsmod if you don't mind me asking?
Also do you use LVS-Tun with realservers on seperate networks?
Just trying to track down why my simple telnet to the smtp server doesn't
work.
Thanks!
-Andy
Kris wrote:
>I have working IPVS-TUN and it does not list listening host:port in
netstat.
>
>Kris
>
>-----Original Message-----
>From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
>[mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Andy
>Shinn
>Sent: Friday, 5 November 2004 2:51 PM
>To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
>Subject: LVS-Tun not working correctl. No listening sockets?
>
>Hello,
>
>I just setup a 2.6.9 kernel and followed Joseph Mack's mini-HOWTO. I
>pretty much got everything compiled and running correctly, no errors.
>But here is the problem I am having. When I add the service and server
>to forward to using ipvsadm I don't get anything listed in netstat -na
>as listening on that host and port. For example:
>
>ipvsadm -A -t 192.168.1.2:25
>ipvsadm -a -t 192.168.1.2:25 -r 192.168.2.5 -i
>
>I was under the impression that this would create a listening host:port
>under netstat. Is this true?
>
>The only modules loaded are ip_vs and ip_vs_wlc. Are there more modules
>I need to load?
>
>Also, my realserver is on a different network (192.168.2.0). They are
>both routed and able to talk to each other. Should this be possible
>with my realserver tunl0 device setup with:
>
> ifconfig tunl0 192.168.1.2 netmask 255.255.255.255 broadcast
> 192.168.1.2 up
>
>192.168.1.1 is the real IP of the director. When I try to telnet
>192.168.1.2 25 i get a connection timeout fairly quickly.
>
>Any advice would be appreciated. I have the feeling I am missing one
>crucial step somewhere.
>
>Thanks!
>
>-Andy
>
>_______________________________________________
>LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
>Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
>or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
>_______________________________________________
>LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
>Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
>or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
>
>
>
>
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx Send
requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
