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
I'm working with pion/ice and encountered an issue when trying to connect multiple devices using a single UDP connection with Shared UDP Mux. Currently, UDPMux identifies each connection by the remote IP/Port, which works well for two pears. However, when I attempt to add a third device, the connection cannot be established as all agents on the device are sharing the same port.
I discussed this with Sean DuBois, who confirmed that the current implementation does not support this setup. However, I believe it could be improved by allowing UDPMux to identify connections in a more flexible way.
For example, the quic-go library provides a mechanism called ListenEarly and DialEarly, which allows for 0-RTT connections, enabling the opening of streams and sending of data before the handshake completes. Implementing a similar approach in pion/ice could allow for multiple devices to share the same UDP port while maintaining individual connections.
Proposed Solution:
Implement a more intelligent way for UDPMux to identify connections, possibly using early connection techniques like those found in quic-go.
Allow for the establishment of multiple connections over the same UDP port, ensuring that each connection is correctly identified even when sharing the same IP and port.
By enabling this feature, pion/ice would be able to handle scenarios where more than two devices need to communicate over a single port, thus enhancing its flexibility and usability in more complex network setups.
The text was updated successfully, but these errors were encountered:
I'm working with pion/ice and encountered an issue when trying to connect multiple devices using a single UDP connection with Shared UDP Mux. Currently, UDPMux identifies each connection by the remote IP/Port, which works well for two pears. However, when I attempt to add a third device, the connection cannot be established as all agents on the device are sharing the same port.
I discussed this with Sean DuBois, who confirmed that the current implementation does not support this setup. However, I believe it could be improved by allowing UDPMux to identify connections in a more flexible way.
For example, the quic-go library provides a mechanism called ListenEarly and DialEarly, which allows for 0-RTT connections, enabling the opening of streams and sending of data before the handshake completes. Implementing a similar approach in pion/ice could allow for multiple devices to share the same UDP port while maintaining individual connections.
Proposed Solution:
Implement a more intelligent way for UDPMux to identify connections, possibly using early connection techniques like those found in quic-go.
Allow for the establishment of multiple connections over the same UDP port, ensuring that each connection is correctly identified even when sharing the same IP and port.
By enabling this feature, pion/ice would be able to handle scenarios where more than two devices need to communicate over a single port, thus enhancing its flexibility and usability in more complex network setups.
The text was updated successfully, but these errors were encountered: