Hi Yogesh,
I have had a look at your modifications. There are some minor mistakes, but I
was also able to find a bug in OpenSSL, for which patch #2555 is submitted.
I have made some small changes to your code, but haven't revised everything.
Most important is the timer handling, which does not
Hi Robin,
I am using DTLSv1_listen() and calling it repeatedly the
difference (I believe) is I am using non-blocking sockets. Please
find attached the sample program from sctp.fh-muenster.de modified for
non-blocking sockets using select that demonstrates this problem.
You can
Hi Yogesh,
On 01.07.2011, at 00:59, Yogesh Chopra wrote:
The setup is same as before (where traffic from server is blocked to
client). The Server responds only once with a HELLO_VERIFY response
for a HELLO request and then never sends a HELLO_VERIFY response for
subsequent CLIENT HELLO
Hi,
I could only access the patch at the link:
http://sctp.fh-muenster.de/dtls-patches.html
as I do not have login credentials for
http://rt.openssl.org/Ticket/Display.html?id=2550
So I am not sure if the 2 places above have different patches.
Post applying this patch I acknowledge, I do
On Jul 1, 2011, at 12:59 AM, Yogesh Chopra wrote:
Hi,
I could only access the patch at the link:
http://sctp.fh-muenster.de/dtls-patches.html
as I do not have login credentials for
http://rt.openssl.org/Ticket/Display.html?id=2550
I think it is username guest, password guest...
So I
Hi,
Please look at the debug messages attached to the original message,
These were printf's added in the DTLS code and these were messages
captured on the server. We are seeing the server start a timer when it
sends back a HelloVerifyRequest. Based on your comments below it
appears that should
Hi Yogi,
could you try the patch in
http://rt.openssl.org/Ticket/Display.html?id=2550
and report if it fixes your issue?
Best regards
Michael
On Jun 27, 2011, at 10:58 PM, Yogesh Chopra wrote:
Hi,
Please look at the debug messages attached to the original message,
These were printf's added
On Jun 27, 2011, at 11:02 PM, Robin Seggelmann wrote:
Hi Yogesh,
Yes, I noticed that after I wrote the mail. The server starts a timer after
sending the HelloVerifyRequest, although it's not supposed to. A patch is
submitted already, but has not yet appeared on the OpenSSL request
Hi Yogesh,
I'm not sure what your problem is. If you drop all messages sent by the server,
then the client keeps repeating its ClientHello until max retransmissions is
reached, that is 12 times. The client starts a timer for every ClientHello it
sends, and if it expires because there is no
Hi Yogesh,
Yes, I noticed that after I wrote the mail. The server starts a timer after
sending the HelloVerifyRequest, although it's not supposed to. A patch is
submitted already, but has not yet appeared on the OpenSSL request tracker.
Best regards
Robin
On 27.06.2011, at 22:58, Yogesh
Hi,
We are using DTLS API to implement a DTLS Client/Server. We notice
when the client application uses dtls_handle_timeout to re-transmit
handshake messages. The DTLS server library seems to be invoking
dtls_handle_timeout for every CLIENT HELLO message.
In order to conduct some network
11 matches
Mail list logo
