If you’re serving DNS to the clients too, and you’re able to push updates to these devices regularly enough somehow, you can also use real certs with names unde

If you’re serving DNS to the clients too, and you’re able to push updates to these devices regularly enough somehow, you can also use real certs with names under some public DNS zone that you control. (Make it resolve to a public IP on the Internet so you can issue/renew the cert, and a private IP on the private network.) But yeah, one way or another, you need a secure context for WebRTC to work. That’s in the spec, and browsers follow it. Perhaps in your context it really is nonsense, but how is the browser to know that your network/physical layer is secure?