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.

Sign up for GitHub

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

Jump to bottom

Socket API should use a random source port and sequence number in TCP connections #17

Open
bremoran opened this issue Jul 10, 2015 · 4 comments
Open

Socket API should use a random source port and sequence number in TCP connections #17

bremoran opened this issue Jul 10, 2015 · 4 comments
Assignees
@bogdanm
Labels
bug mirrored

Comments

@bremoran
Copy link
Contributor

With LwIP, the source port is always the same and the sequence number is always 0.
@bremoran bremoran added the bug label Jul 10, 2015
@yogpan01
Copy link

yogpan01 commented Aug 3, 2015

Hi Brendan,
Any update on this ? It is a blocker for DTLS feature in LWM2M Client. Reconnecting socket to mDS doesn't work because the source port number is always same. Its a blocker for Beta release.

@bremoran
Copy link
Contributor Author

bremoran commented Aug 3, 2015

Hi Yogesh,
I guess that there is an analogue requirement in UDP for DTLS, but this ticket is specifically for TCP.

@yogpan01
Copy link

yogpan01 commented Aug 3, 2015

Hi,
So should we create a new issue for UDP ?

@rainierwolfcastle
Copy link

ARM Internal Ref: IOTSFW-993

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bogdanm bogdanm

Labels
bug mirrored
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bogdanm @rainierwolfcastle @bremoran @yogpan01