First login?
Lost password?
 
 
sctp-discussion AT lists.franken.de 
SCTP Discussions

Text archives Help


Re: [SCTP-Discussion] Sctplib 1.0.4 still not working on Windows XP


Chronological Thread 
  • From: dp AT ii.net
  • To: "Smedley, Mark" <mark.smedley AT logicacmg.com>
  • Cc: discussion AT sctp.de
  • Subject: Re: [SCTP-Discussion] Sctplib 1.0.4 still not working on Windows XP
  • Date: Fri Jun 30 06:52:03 2006
  • List-id: SCTP Discussions <discussion.sctp.de>
Hi Mark,

I can also get this test to work with with both servers on the same box.

Have you been able to get it work with 2 different PCs at either end of
the association ?

Short of compiling my own windows version and debugging it I will have to
stick to the linux sctplib implementation for testing my sctp stack.

cheers,
davidp.
--
David Pascoe,
mailto:dp AT ii.net,
Western Australia


On Wednesday, 21 June 2006, at 13:12:03 [GMT +0100] you wrote:
SM> Hi David,

SM> Pls also see my reply to Michael.

>>We are talking about sctplib for windows from sctplib.BE right -
>>from the Belgium site and not the German one ?

SM> Correct, the precompiled .exe installer.
SM> I did also try to compile it but that's a whole other story!

SM> So my problem with running server and client on the same box was
SM> down to the -i option (ignore OOTB packets).

SM> Using this I was able to successfully get client->server comms
SM> going as follows;
SM> test To(term a) From(term b)
SM> 1 combined_server -i -V terminal -i -V -d <ipaddr>
SM> 2 echo_server -i -V -s <ipaddr> echo_tool -i -d <ipaddr> -n 10

SM> Results
SM> 1. was able to type stuff in the terminal. This was received, length
SM> logged
SM> and echoed back to the terminal by the server
SM> 2. Observed significant CPU usage on the echo_server and echo_tool which
SM> implied the initial 10 packets where "ping-ponging" between the two as
SM> described in a test somewhere (sorry I cant remember what doc I found
SM> this in, wish I could there was some more useful info).
SM> I'll try multi next...

SM> I guess this does not assist in diagnosing the Win32/Linux missmatch
SM> in behaviour you described but "may" be of some help.

SM> Rgds,
SM> Mark.

SM> -----Original Message-----
SM> From: David Pascoe
[mailto:dp AT ii.net]

SM> Sent: 21 June 2006 04:09
SM> To: Smedley, Mark
SM> Cc:
discussion AT sctp.de
SM> Subject: Re: [SCTP-Discussion] Sctplib 1.0.4 still not working on
SM> Windows XP

SM> Hi Mark,

SM> We are talking about sctplib for windows from sctplib.BE right - from
SM> the Belgium site and not the German one ?

SM> I also tried the sctplib.exe from sctplib.be and found that it just
SM> wouldn't work either. Watching in ethereal I could see that it can
SM> generate sctp packets but would never seem to react to receiving any
SM> packets - as if they never arrived at sctplib or it dropped them all.
SM> The command line programs seem to ignore the verbose flags so I couldn't
SM> glean any clues.

SM> I one example the INIT would go out from the PC, and the INIT ACK would
SM> come back from my device under test, and that would be it. It stopped
SM> there.

SM> I tried various combinations of terminal, echo_server and it could never
SM> establish an association with my test device. By comparison my redhat
SM> box sitting right next to my PC is able to establish an association and
SM> send/receive echo packets (for eg) with my test device. The redhat box
SM> is running sctplib 1.0.4 and using the same command line test programs -
SM> terminal, echo_server (and indeed multiserver for dual-home testing).

SM> So sadly I can only concur that I couldn't get it to work either. A
SM> shame because a simple install on windows would be great as setting it
SM> up under linux does take a few fiddly steps to get it working.

SM> I agree with Michael - not sure that you want to run the echo server and
SM> echo_tool on the same PC ?

SM> cheers,
SM> davidp.
SM> --
SM> David Pascoe,
mailto:dp AT ii.net,
Western Australia


SM> On Tuesday, 20 June 2006, at 16:43:16 [GMT +0100] you wrote:
SM>> Hi folks,
SM>>
SM>> I have still had no success in running sctplib
SM>> 1.0.4 under windows.
SM>> There is no windows firewall running, I can ping my addresses
SM>> without issue.

SM>> Please? Can anyone help?
SM>> Has anyone successfully installed 1.0.4 on (A fully updated) windows

SM>> xp Has anyone else failed to get it working on XP?

SM>> I followed the instructions supplied i.e.

SM>> o Downloaded, and ran sctplib-1.0.4.exe o It installed normally,
SM>> with all defaults, and no errors.
SM>> o Downloded, and extracted the contents of glib-1.2.zip to
SM>> /Program Files/sctplib (the install dir) o Opened two cmd prompts
SM>> a & b o typed:
SM>> echo_server -s 158.234.65.22
SM>> in prompt a
SM>> o typed:
SM>> echo_tool -d 158.234.65.22 -n 10
SM>> in prompt b
SM>>
SM>> resulting in the following:
SM>> Prompt a:
SM>> C:\Program Files\sctplib>echo_server -s 158.234.65.22 Error Info:
SM>> 16:21:07.109 - mdi_readSCTP_control: association not set Error Info:

SM>> 16:21:07.109 - mdi_readSCTP_control: association not set Error Info:

SM>> 16:21:07.109 - sci_getCookieLifeTime(): read SCTP-control failed
SM>> Error Info: 16:21:07.125 - mdi_readRX_control: association not set
SM>> Error Info: 16:21:07.125 - rxc_buffer instance not set !
SM>> Error Info: 16:21:07.125 - mdi_readRX_control: association not set
SM>> Error Info: 16:21:07.125 - rxc_buffer instance not set !

SM>> Prompt b:
SM>> C:\Program Files\sctplib>echo_tool -d 158.234.65.22 -n 10 Error
SM>> Info: 16:21:07.109 - rxc_buffer instance not set !

SM>> I did a netstat before and after launching the echo server and there

SM>> were no new listeners started, oh, did I mention the windows
SM>> firewall is disabled?

SM>> The only thing I haven't tried is redownloading the files!
SM>> When I unzip the source the files...

SM>> 1. manual/commands.doc crashes word
SM>> 2. manual/commands.pdf cant be read by Adobe reader 7 3.
SM>> manual/sctp-api-1.0-1.pdf cant be read by adobe reader 7

SM>> Are these files corrupt or were they released in this state??

SM>> Mark.



SM> This e-mail and any attachment is for authorised use by the intended
SM> recipient(s) only. It may contain proprietary material, confidential
SM> information and/or be subject to legal privilege. It should not be
SM> copied, disclosed to, retained or used by, any other party. If you are
SM> not an intended recipient then please promptly delete this e-mail and
SM> any attachment and all copies and inform the sender. Thank you.




Archive powered by MHonArc 2.6.19+.

Top of page