You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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 🙌
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.
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
Feature Request Summary
If these requests are out of scope, no worries. Feel free to close the issue
Let me know if additional info is required.
Thanks!
The text was updated successfully, but these errors were encountered: