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
It uses UDP over IPv4/6. The choice of using UDP was also so that an attacker could not probe a system to identify that the OpenSPA service is running. Using TCP would reveal that a service is listening on a port, even if the service would not send any data back. However it is not uncommon that in certain networks, the use of UDP is restricted to known protocols (e.g. DNS) in which case using TCP would circumvent such issues.
As far as the project is concerned, you could implement TCP support. From the top of my head there are no application layer limitations. You would essentially just need to refactor the transport layer of this project. With the ADK feature it gets a bit more complicated. The basic implementation which is implemented in userspace should work ootb. The XDP extension of ADK means that the ADK feature is implemented in eBPF/XDP. The XDP ADK implementation would need some work in order to support TCP. However the ADK feature is completely optional and the userspace implementation is already a great improvement over no-ADK feature enabled.
is this using udp or tcp? possible to force it to use tcp?
The text was updated successfully, but these errors were encountered: