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

getsockname missing? #668

Closed
nojb opened this issue Jan 14, 2024 · 3 comments
Closed

getsockname missing? #668

nojb opened this issue Jan 14, 2024 · 3 comments

Comments

@nojb
Copy link
Contributor

nojb commented Jan 14, 2024

There doesn't seem to be a way to figure out which port and address a socket is bound to when assigned by the operating system.

@nojb
Copy link
Contributor Author

nojb commented Jan 15, 2024

But it is easy enough to do this using the underlying file descriptor; sorry for the noise!

@nojb nojb closed this as completed Jan 15, 2024
@talex5
Copy link
Collaborator

talex5 commented Jan 15, 2024

Should be fixed by #555.

@nojb
Copy link
Contributor Author

nojb commented Jan 15, 2024

Should be fixed by #555.

Thanks. I left comment there (need to support datagram sockets).

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

2 participants