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
Hi, I'm working on a project that's currently using the native Java implementation of DTLS. In it, we receive traffic on a well known port, but connect and transmit from a different port.
We're now re-implementing with BC because we need to be FIPS compliant. The issue I'm having is the UDPTransport requires the socket to be connected to the client. Is there a way other than having to redirect the clients to another port from the well-known port before starting the DTLS handshake?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I'm working on a project that's currently using the native Java implementation of DTLS. In it, we receive traffic on a well known port, but connect and transmit from a different port.
We're now re-implementing with BC because we need to be FIPS compliant. The issue I'm having is the UDPTransport requires the socket to be connected to the client. Is there a way other than having to redirect the clients to another port from the well-known port before starting the DTLS handshake?
Beta Was this translation helpful? Give feedback.
All reactions