-
QuestionDear, I have a main router at 192.168.0.1 My MediaMTX running on second router with VLAN 192.168.1.1 (192.168.0.2) and client run on VLAN 10.0.0.1 (192.168.0.3) If i move the mediamtx server to VLAN 10.0.0.1 (192.168.0.3) same with the client, it's able to make connection too. Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hello, when there are routers / NAT / firewalls between MediaMTX and clients, you have to make sure that routers are forwarding incoming requests to MediaMTX. If you're able to establish a contact (i.e. view the web page) of MediaMTX from a client, it means that you can already reach the server through an IP and through TCP port 8889. What you are missing is the ability to reach the server from the same IP and UDP port 8189 ( Another required thing is that you need to insert the server external IP (192.168.0.2?) inside webrtcAdditionalHosts: [192.168.0.2] No STUN or TURN servers are required, you don't need to use them unless any other method fails (mostly due to company firewalls that block all ports). For more informations, the README contains a full tutorial: https://github.com/bluenviron/mediamtx?tab=readme-ov-file#solving-webrtc-connectivity-issues |
Beta Was this translation helpful? Give feedback.
Hello, when there are routers / NAT / firewalls between MediaMTX and clients, you have to make sure that routers are forwarding incoming requests to MediaMTX.
If you're able to establish a contact (i.e. view the web page) of MediaMTX from a client, it means that you can already reach the server through an IP and through TCP port 8889. What you are missing is the ability to reach the server from the same IP and UDP port 8189 (
webrtcLocalUDPAddress
).Another required thing is that you need to insert the server external IP (192.168.0.2?) inside
webrtcAdditionalHosts
, because readers need to know it explicitly:No STUN or TURN servers are required, you don…