From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: In-/Outbound firewall configuration for Tor relay
Date: Wed, 27 Jun 2018 22:53:25 +0200 [thread overview]
Message-ID: <7fc21243-349c-94b2-4c18-59121e356715@link38.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Hello,
for quite some time, IPFire includes Tor via Pakfire as an add-on.
Trying to set up a Tor relay there, I stumbled into several problems
regarding firewall rule configuration:
(a) Inbound
It turns out that Tor is not working correctly if GeoIP block is
active (this occurred after a reboot - strange). Of course, one
possibility is to disable GeoIP block at all, allow access to the
Tor relay ports, and deny any except those of legitimate countries
to other services on the firewall machine.
Since this enlarges the ruleset (already quite complex here :-| ),
I am wondering if there is a more simple way to achieve this.
(b) Outbound
For security reasons (surprise!), outgoing connections are heavily
limited here - only DNS, NTP and web traffic is allowed, and only
to a certain list of countries. Some call that "racist routing"...
This does not work with Tor since it needs to open connections to
almost any port on almost any IP address. Allowing outbound traffic
in general is out of question, so there seems to possibility left.
Besides from running a Tor relay in the local DMZ and apply the
firewall rules for this machine, is there another way?
Thanks, and best regards,
Peter Müller
--
"We don't care. We don't have to. We're the Phone Company."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-06-27 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 20:53 Peter Müller [this message]
2018-06-28 12:24 ` Michael Tremer
2018-06-28 17:14 ` Peter Müller
2018-06-29 21:26 ` Peter Müller
[not found] <d285bf5e6b378eaed27b8c2650fdc102be5d1a5b.camel@ipfire.org>
2018-07-01 6:00 ` Peter Müller
2018-07-01 9:39 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fc21243-349c-94b2-4c18-59121e356715@link38.eu \
--to=peter.mueller@link38.eu \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox