m1k1o / neko

A self hosted virtual browser that runs in docker and uses WebRTC.
https://neko.m1k1o.net/
Apache License 2.0
5.98k stars 449 forks source link

[request] Ability to set custom hosts file to prevent connection to local lan #177

Open Rami-Pastrami opened 2 years ago

Rami-Pastrami commented 2 years ago

Is there a way (or if not, could one be added) to prevent users within neko from connecting to local IPs within its hosted network?

for example - Neko is hosted on a docker instance on IP 192.168.1.10, is networked to a custom network directly to a reverse proxy and is in bridge network such that the UDP ports work correctly. A user within the neko instance can go to address 192.168.1.1. How can this be prevented?

m1k1o commented 2 years ago

You have multiple solutions:

Generally speaking according to best practices, neko should be installed in DMZ so that all of this should be handled by the server or your network.