Skip to content

Issues: ARMmbed/sockets

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

15 Open 11 Closed
15 Open 11 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

SOCKET_ERROR_ABORT (2) when closing stream at the end of test. mirrored
#65 opened Mar 4, 2016 by mazimkhan
1
Periodic interval should be managed by the network interface class enhancement
#59 opened Jan 25, 2016 by bremoran
Resolve should track queries and handlers mirrored
#58 opened Jan 25, 2016 by bremoran
1
resolve should not require an open socket mirrored
#57 opened Jan 25, 2016 by bremoran
1
Sockets should not be aware of the stack in single-stack environments mirrored
#56 opened Jan 5, 2016 by bremoran
1
UDPSocket issues mirrored
#55 opened Dec 31, 2015 by adbridge
1
TCPStream issues mirrored
#54 opened Dec 31, 2015 by adbridge
2
TCPListener issues mirrored
#53 opened Dec 30, 2015 by adbridge
2
class TCPAsynch is insufficiently documented mirrored
#51 opened Dec 29, 2015 by adbridge
1
Descriptions of the get addr and port in socket.h need to be updated mirrored
#46 opened Dec 18, 2015 by adbridge
1
TCPListener needs a reject helper member function mirrored
#44 opened Dec 16, 2015 by bremoran
1
Only a single sal-stack can be used with the socket API bug mirrored
#36 opened Nov 4, 2015 by adbridge
TCPStream::connect() does not return an error when there are no connections free mirrored
#34 opened Oct 27, 2015 by bremoran
2
Socket API should use a random source port when opening UDP sockets without bind enhancement
#21 opened Aug 3, 2015 by bremoran
@bogdanm
1
Socket API should use a random source port and sequence number in TCP connections bug mirrored
#17 opened Jul 10, 2015 by bremoran
@bogdanm
4
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.