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

Feature Requests: Support for UDP protocol and also details on network connections. #5

Open
puffyCid opened this issue May 18, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@puffyCid
Copy link

puffyCid commented May 18, 2024

Hey thanks for creating this really cool library!

In the README its mention that it supports TCP only. Is it feasible to include UDP as well?

In addition, currently it only includes processes that are listening on a port. Is it feasible to include all network connections, both listening and estblashied?
Similar to the netstat output below

Proto   Local Address          Foreign Address        (state)
tcp  10.123.123.123:54459   185.199.108.133:443    ESTABLISHED
tcp  10.123.123.123:54458   185.199.109.154:443    ESTABLISHED
tcp  127.0.0.1.8384          *.*                   LISTEN
udp  *.56612                 *.*

Feature Request Summary

  • Support for UDP protocol
  • Include details on all network connections

If these requests are out of scope, no worries. Feel free to close the issue
Let me know if additional info is required.

Thanks!

@GyulyVGC
Copy link
Owner

GyulyVGC commented May 21, 2024

Is it feasible to include UDP as well?
...
In addition, currently it only includes processes that are listening on a port. Is it feasible to include all network connections, both listening and estblashied?

Yes, it is feasible.
However, at the moment just TCP is included since UDP is connectionless and the concept of listener doesn't really apply.
And as the name of the library suggests, only connections in the listen state are reported (this is on purpose).
However, I could consider extending the scope of this library in the future.

I'll leave this issue open as a reminder, thanks 🙌

@Revertron
Copy link

UDP is connectionless and the concept of listener doesn't really apply.

But UDP servers "listen" for packets, like DNS-servers listen on port 53, for example. Don't they?

@GyulyVGC
Copy link
Owner

But UDP servers "listen" for packets, like DNS-servers listen on port 53, for example. Don't they?

UDP ports are either open or close, they don't have other possible states. So you could consider an open UDP port as "listening", but the concept is different since UDP just sends datagrams and doesn't establish connections.

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

No branches or pull requests

3 participants