[QUESTION] host ice candidate socket and srflx ice candidate socket stay open until the peer connection is closed. Is it intended?

[wei-zhang-simplisafe]

When webrtc KVS SDK is doing the ICE negotiation, it opens multiple UDP/TCP, one for each host ice candidate, one for each srflx ice candidate, and one for each turn server.

After an ice candidates pair is chosen, a.k.a. a remote ice candidate and a local ice candidate have exchanged stun packets, the not-in-use TURN sockets are closed,

But, SDK doesn’t close not-in-use host ice sockets and srflx ice sockets when an ice candidate pair is chosen, and only closes them when the peer connection is closed. Therefore, while live streaming is running, there are sockets open and idling. Is this intended behavior? Is there any network security concern? Is there any system resources wasting concern?

[unicornss]

Thank you for your observation. To better understand your camera module implementation, could you please provide additional details (or send email to [email protected]) on the following aspects:

• How many network interfaces are utilized in your camera?
• What is the method you are using to identify the open sockets in the camera?
• Are you leveraging the SDK's capability to filter out unused or unnecessary network interfaces?
• Is there any maximum duration of the streaming session (PeerConnection) allowed in the camera?

[wei-zhang-simplisafe]

How many network interfaces are utilized in your camera?

One

What is the method you are using to identify the open sockets in the camera?

Running Linux command "netstat -uantlp" And also by reading the SDK source code

Are you leveraging the SDK's capability to filter out unused or unnecessary network interfaces?

We know how to use the filtering, but not using it for the camera, because there is only one network interface

Is there any maximum duration of the streaming session (PeerConnection) allowed in the camera?

No

[github-actions[bot]]

This is a very old issue. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one.