# exit node

Published articles for exit node.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Using a Tailscale Exit Node on Sketchy Hotel Wi-Fi

DevFeed: [Using a Tailscale Exit Node on Sketchy Hotel Wi-Fi](<https://devfeed.tech/articles/on-the-node-while-on-the-road-with-tailscale-31212.md>)

Original publisher: [Read original article](<https://tailscale.dev/blog/on-the-node-while-on-the-road>)

Author: Claire Wang

Published: 2023-08-18T00:00:00Z

Content type: article

Language: en

Sources: [Tailscale Community](<https://devfeed.tech/sources/tailscale-community.md>)

Topics: [tailscale](<https://devfeed.tech/topics/tailscale.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [networking](<https://devfeed.tech/topics/networking.md>)

Tags: [exit-node](<https://devfeed.tech/tags/exit-node.md>), [hotel-wifi](<https://devfeed.tech/tags/hotel-wifi.md>), [tailscale](<https://devfeed.tech/tags/tailscale.md>), [vpn](<https://devfeed.tech/tags/vpn.md>), [wifi](<https://devfeed.tech/tags/wifi.md>)

### AI overview

The article describes using a Tailscale exit node to circumvent sketchy hotel Wi-Fi.

### Source excerpt

Circumventing sketchy hotel wifi using an exit node.

## Running a Tor relay with Docker

DevFeed: [Running a Tor relay with Docker](<https://devfeed.tech/articles/running-a-tor-relay-with-docker-35192.md>)

Original publisher: [Read original article](<https://blog.jessfraz.com/post/running-a-tor-relay-with-docker/>)

Published: 2015-08-23T16:02:01Z

Content type: tutorial

Language: en

Sources: [Jessie Frazelle](<https://devfeed.tech/sources/jessie-frazelle.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [container](<https://devfeed.tech/topics/container.md>), [Docker Container](<https://devfeed.tech/topics/docker-container.md>), [Docker Image](<https://devfeed.tech/topics/docker-image.md>), [hosting](<https://devfeed.tech/topics/hosting.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [bridge](<https://devfeed.tech/tags/bridge.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-container](<https://devfeed.tech/tags/docker-container.md>), [docker-image](<https://devfeed.tech/tags/docker-image.md>), [exit-node](<https://devfeed.tech/tags/exit-node.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [linux](<https://devfeed.tech/tags/linux.md>), [network](<https://devfeed.tech/tags/network.md>), [tor](<https://devfeed.tech/tags/tor.md>)

### AI overview

A tutorial on running Tor bridge, middle, and exit relays in Docker containers. It covers creating a minimal Alpine-based Docker image with separate Tor configurations, running each relay type, and checking whether an exit node has registered.

### Source excerpt

This post is part two of what will be a three part series. If you missed it part one was How to Route Traffic through a Tor Docker container. I figured it was important, if you are going to be a tor user, to document how you can help the Tor community by hosting a Tor relay. And guess what? You can use Docker to do this! There are three types of relays you can host, a bridge relay, a middle relay, and an exit relay. Exit relays tend to be the ones recieving take down notices because the IP is the one the public sees traffic from Tor as. A great reference for hosting an exit node can be found here blog.torproject.org/blog/tips-running-exit-node-minimal-harassment. But I will go over how to host each from a Docker container. My example will have a reduced exit policy and limit which ports you are willing to route traffic through. If you don't want to host an exit node, host a middle relay instead! And if you want your relay not publically listed in the network then host a bridge. Creating the base image I have created a Docker image jess/tor-relay from this Dockerfile. Feel free to create your own image with the following Dockerfile: FROM alpine:latest # Note: Tor is only in testing repo RUN apk update && apk add \ tor \ --update-cache --repository http://dl-3.alpinelinux.org/alpine/edge/testing/ \ && rm -rf /var/cache/apk/* # default port to used for incoming Tor connections # can be changed by changing 'ORPort' in torrc EXPOSE 9001 # copy in our torrc files COPY torrc.bridge /etc/tor/torrc.bridge COPY torrc.middle /etc/tor/torrc.middle COPY torrc.exit /etc/tor/torrc.exit # make sure files are owned by tor user RUN chown -R tor /etc/tor USER tor ENTRYPOINT [ "tor" ] As you can see we are copying 3 different torrc's into the container. One for each a bridge, middle, and exit relay. I used alpine linux because it is super minimal. The size of the image is 11.52MB! Crazyyyyyyy! Running a bridge relay A bridge relay is not publically listed as part of the Tor network. Th

## Using Tor to Circumvent Country Origin Restrictions

DevFeed: [Using Tor to Circumvent Country Origin Restrictions](<https://devfeed.tech/articles/using-tor-to-circumvent-country-origin-restrictions-30132.md>)

Original publisher: [Read original article](<http://www.netmeister.org/blog/tor-exit-node.html>)

Published: 2014-02-28T03:23:11Z

Content type: article

Language: en

Sources: [Signs of Triviality](<https://devfeed.tech/sources/signs-of-triviality.md>)

Topics: [tor](<https://devfeed.tech/topics/tor.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [exit-node](<https://devfeed.tech/tags/exit-node.md>), [location](<https://devfeed.tech/tags/location.md>), [tor](<https://devfeed.tech/tags/tor.md>), [using](<https://devfeed.tech/tags/using.md>)

### AI overview

This article explains how to use Tor by forcing traffic through an exit node in a specific location to circumvent country-based content restrictions.

### Source excerpt

Sometimes content hosted in one country is restricted from viewing in another. This article describes how you can use Tor to circumvent such restrictions by forcing the use of an exit node in a specific location."