RE: https problem

I have no problems with https on both Ultramonkey 2.x and 3.x
Here is one part:

###   secure
virtual=172.16.60.184:https
        real=172.16.60.130:https gate
        real=172.16.60.150:https gate
        real=172.16.60.220:https gate
        real=172.16.60.230:https gate
        service=https
        scheduler=wlc
        checkport=443
        request="sjmonitor.html"
        receive="teststring"
        persistent=120
        netmask=255.255.255.255
        protocol=tcp

-----Original Message-----
From: John C. Amodeo [mailto:[email protected]]
Sent: Wednesday, October 05, 2005 9:23 AM
To: [email protected]
Subject: Re: https problem


Lam,

I had this problem just last week. What I found was I needed to change
"checktype=connect" in the ldirectord.cf file. For some reason, with an
SSL cert, ultramonkey cannot connect to a https service when
"checktype=negotiate"

Also, make sure you have virtual host configured for the web servers you
need to connect to. If your httpd.conf file is not correct, ultramonkey
will not be able to establish a connection.

Hope this helps you in some way...

-John

Lam Louis wrote:

> I set up a LVS with one director and two realserver. Using DR method,
> I successed to set up a http service.
>
> However, it failed to connect the realserver through https services.
>
> the Structure is as below:
>
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 10.0.58.136:443 rr
> -> 10.0.58.232:443 Route 1 0 2
> TCP 10.0.58.136:80 rr
> -> 10.0.58.230:80 Route 1 1 8
> -> 10.0.58.232:80 Route 1 0 7
>
>
> and after numbers of accesses of HTTPS, information has showed below:
>
>
> IP Virtual Server version 1.0.10 (size=65536)
> Prot LocalAddress:Port Conns InPkts OutPkts InBytes OutBytes
> -> RemoteAddress:Port
> TCP 10.0.58.136:443 15 76 0 4330 0
> -> 10.0.58.232:443 15 76 0 4330 0
> TCP 10.0.58.136:80 236 1868 0 333760 0
> -> 10.0.58.230:80 45 566 0 127198 0
> -> 10.0.58.232:80 191 1302 0 206562 0
>
>
> Althrough I can't accesses the https service, but the realserver
> showed the trace as below
>
> tcpdump -n -i any port 443
> tcpdump: listening on any
> 17:09:09.833127 10.0.58.93.2450 > 10.0.58.136.https: S
> 4012402657:4012402657(0) win 65535 <mss 1460,nop,nop,sackOK> (DF)
> 17:09:09.833142 10.0.58.136.https > 10.0.58.93.2450: S
> 4038977378:4038977378(0) ack 4012402658 win 5840 <mss
> 1460,nop,nop,sackOK> (DF)
> 17:09:13.630883 10.0.58.136.https > 10.0.58.93.2450: S
> 4038977378:4038977378(0) ack 4012402658 win 5840 <mss
> 1460,nop,nop,sackOK> (DF)
> 17:09:19.630883 10.0.58.136.https > 10.0.58.93.2450: S
> 4038977378:4038977378(0) ack 4012402658 win 5840 <mss
> 1460,nop,nop,sackOK> (DF)
>
>
> The web farm did not set any firewall , Can you help me to solve the
> problem?
>
> Thank You Very Much~1
>
>
>

-- 
______________________________________________________________
John C. Amodeo :: Associate Director of Information Technology
Faculty of Arts and Sciences
Rutgers, The State University of New Jersey
Voice: 732.932.9455 Fax: 732.932.0013


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.