TCP DNS requests will be allowed and will be routed through the Tor network but will not be able to resolve.onion addresses to a virtual address in the range 10.192.0.0/10. All UDP DNS requests will be handled by the Tor DNS resolver and will be able to resolve.Setting -dns 127.0.0.1 for the router is not required but makes configuration of containers attached by routing with shared network stack simpler.
onion addresses and should not be used on any attached network. When this is complete, it will be possible to create Docker networks that utilise this image as a router, at which time this documentation will be updated with the relevant instructions. Routing over Docker networkĪ container routing driver is currently in development. If the container runs any process with UID 9001, this process will completely bypass the transparent routing. Warning: Containers attached to the router in this way should never be given -privileged or -cap-add NET_ADMIN. This means that requests being routed through each instance will appear to come from a distinct IP address.
Using this device, you can browse the internet anonymously and defeat NSA’s snooping. The image will run multiple Tor instances, each of which will (in general) have a different exit node. Short Bytes: By investing some time and money, now you can make a portable Raspberry Pi TOR proxy router. Tor Tor provides an anonymous SOCKS proxy. The new container will share the networking stack of the tor-router which has been configured to transparently route all outbound TCP traffic via the Tor Proxy. Components in the Medusa Proxy (single headed configuration). Docker run -rm -net=container:tor-router flungo/netutils \
0 kommentar(er)
