Re: [SPAM] No communications to target machine

[Robert I. <cor...@gm...>]

Hi Alexander,

On Sun, Sep 21, 2008 at 9:21 PM, Bradley Alexander <st...@tu...> wrote:
>
> Hi,
>
> I'm having a problem with curl-loader. I have tried both 0.44 and 0.46. I did a default build of both on my test machine. I modified the https.conf file and pointed it to the target system, and am experiencing timeouts, as if it is not connecting. I ran a curl -k to the site, and the page loads fine, which leads me to believe it may be the way curl loader is mangling the URL.

Please, collect the facts prior to conclusions.

>
>
> If I run:
>
> curl -k "https://target.example.com/index.php?NASID=test-nsaid&NASIP=accessctlr.example.com&&CallerID=00:1C:26:19:0C:87&CustIP=192.168.2.248&VLAN=2&RD=http%3A%2Fen-us.start2.mozilla.com%2Ffirefox%3Fclient%3Dfirefox-a&LgnURL=https://accessctlr.example.com/goform/HtmlLoginRequest.php"
>
> it gives me the login page. However, my curl loader config has the following:
>
> BATCH_NAME= https
> CLIENTS_NUM_MAX=20 # Same as CLIENTS_NUM
> CLIENTS_NUM_START=2
> CLIENTS_RAMPUP_INC=2
> INTERFACE   =eth0
> NETMASK=24
> IP_ADDR_MIN= 10.56.57.1
> IP_ADDR_MAX= 10.56.57.254
> CYCLES_NUM=-1
> URLS_NUM= 1
> LOG_RESP_HEADERS=1
> LOG_RESP_BODIES=1
>
> ########### URL SECTION ####################################
>
> URL="https://target.example.com/index.php?NASID=test-nsaid&NASIP=accessctlr.example.com&&CallerID=00:1C:26:19:0C:87&CustIP=192.168.2.248&VLAN=2&RD=http%3A%2Fen-us.start2.mozilla.com%2Ffirefox%3Fclient%3Dfirefox-a&LgnURL=https://accessctlr.example.com/goform/HtmlLoginRequest.php"
> URL_SHORT_NAME="target"
> REQUEST_TYPE=GET
> TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by cancelling url fetch on timeout
> TIMER_AFTER_URL_SLEEP =1000
>
> I have run tcpdumps on the test box and the target box. The test box shows the curl-loader packets going out, but nothing coming back. The target box does not show any traffic from the test box at all.
>
> Can someone point out what it is that I am nissing?
>

First, fill the PROBLEM-REPORTING-FORM (PRF) in due course, since your
data is not enough.
Second, include to your curl-loader command line (unclear what is the line) -v
Third, try a non https , e.g. some http URL and for a single client.

Forth, read the FAQs at the web-site regarding the batch log file. you
may wish to collect such
file with option -v and to attach to you PRF in a gzipped form.
The filtered tcpdump or wireshark capture could be also helpful.


If your problem in some SSL/TLS handshake, we'll see a complain about
it in the log file.
Please, run curl-loader for the log with a single configured client,
single IP and single cycle.


>From curl man pages:
----------------------------------------------------------------------------------------------------------------
-k/--insecure

(SSL) This option explicitly allows curl to perform "insecure" SSL
connections and transfers. All SSL connections are attempted to be
made secure by using the CA certificate bundle installed by default.
This makes all connections considered "insecure" fail unless
-k/--insecure is used.

See this online resource for further details:
http://curl.haxx.se/docs/sslcerts.html

----------------------------------------------------------------------------------------------------------------------

What happens with your curl command line fetch, if you remove -k?

Vald Wainbaum has recently maid some patching for a similar issue.
Vlad could you guide us regarding your practice?


Thanks.Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................