Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using retransmission timer #26

Open
pokgak opened this issue Jan 15, 2020 · 2 comments
Open

Using retransmission timer #26

pokgak opened this issue Jan 15, 2020 · 2 comments

Comments

@pokgak
Copy link
Contributor

pokgak commented Jan 15, 2020

How is the retransmission of handshake messages done in tinydtls? Based on my testing (by dropping a handshake message manually on the client), there is currently no retransmission done automatically.

Do I need to call dtls_check_retransmit() after a certain period after sending the handshake message?

Also, I found the following in dtls.c. Does this mean that retransmitting handshake messages is still not supported?

tinydtls/dtls.c

Lines 1649 to 1651 in d99fb8c

/* FIXME: copy to peer's sendqueue (after fragmentation if
* necessary) and initialize retransmit timer */
res = CALL(ctx, write, session, sendbuf, len);

@peyton-li
Copy link

Do you resolve this problem?
i also find some problem in tinydtls when i use dtls_check_retransmit().

@mrdeep1
Copy link
Contributor

mrdeep1 commented Sep 7, 2020

dtls_check_retransmit() needs to be called periodically by a higher layer (unless if you have a CONTIKI environment which starts off a coap_retransmit_process thread) to see if any packet re-transmission is required. next returns the time dtls_check_retransmit() should next be called.

@peyton-li You need to be more specific as to what the problems are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants