-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
WebRTC: A small tool for testing UDP connectivity on UDP 8000. #2843
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello, author, I have also confirmed that it is an issue with the upd8000 port. I would like to ask how you modified the udp port. I changed the host port to 18000, but the container's port remained as 8000. As a result, the rtc cannot play properly, and the playback address, whether it is webrtc://host/live/livestream or webrtc://host:18000/live/livestream, keeps spinning. Thank you.
|
Currently, the host's port and the container's port are not supported to be different. You need to change the listening port of the container as well. Please refer to the WIKI for specific instructions.
|
Hmm, I understand now. The ones inside the container also need to be modified... Wishing you a happy new year in advance.
|
Uh oh!
There was an error while loading. Please reload this page.
Today I discovered a very strange issue, the UDP/8000 port is not accessible. There are no issues with the security group and listener, but after tinkering for a while, I had to raise a ticket with the cloud service provider for further investigation.
During the process of raising the ticket, I realized that troubleshooting the accessibility of UDP ports is a more complicated issue compared to checking if TCP port 22 is accessible. Unlike TCP, there is no commonly used UDP server to test the connectivity, making it difficult to investigate.
In the end, it was discovered that the UDP ports below 8000 were blocked by the company. There were no issues when using 4G or home WiFi, but changing to UDP port 18000 resolved the problem. This indicates that:
I found some simple UDP servers and clients that can be run on my own server, and then tested them on the client side.
OBS WHIP
See English or Chinese
NC
Start a UDP server:
Start a UDP client:
If success, you should see the message in the UDP server.
IPERF
Start a UDP server:
Start a UDP client:
If success, you can see the report of bandwidth.
Go
Code snippet: Gist
Start the server:
Execute the command to check if the listening is normal:
Execute the nc command, send the message
Hello
to the server, and then pressEnter
:Run the client on the local machine:
The result should be normal:
Run the client, specifying the remote server:
Below is the code to prevent everyone from accessing the gist. Other languages are welcome to contribute.
server.go
clieng.go
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: