Recent comments

Rambler wrote

Reply to comment by boobs in Requirement for a exit node? by Jogger

the primary requirement for an exit node that no one tells you about:

balls of steel.

Has anyone ever been arrested or held legally liable for running an exit node (in a modern country, like the US/CA/UK/Etc)?

I've thought about running one as well since my server provider is okay with it as long as I handle the abuse complaints which is basically copy/pasting a cookie cutter response on how it's an exit-node and not possible to tell the origin of whatever it is the complaint is about.

1

Rambler OP wrote

After a quick review I'll say: It's alright. A bit buggy. But hey, it's new. Hopefully in time it'll work those issues out.

It's never a bad thing to have options so I'm glad to see it regardless.

1

MrBlack OP wrote

Shoutout to the all the park rangers out there who leave people alone or humor them and listen to their incoherent ramblings about trees and waterfalls..

3

Rambler wrote

Per https://community.torproject.org/relay/relays-requirements/

A <40 Mbit/s non-exit relay should have at least 512 MB of RAM available.
A non-exit relay faster than 40 Mbit/s should have at least 1 GB of RAM.
On an exit relay we recommend at least 1.5 GB of RAM per tor instance.

Not sure about the control panel to manage it, but that'd add overhead to the RAM requirement. Hopefully someone will correct me if I'm wrong, but I'm pretty sure it's "set it and forget it". What are you wanting to do with a control panel? See network graphs and stats and stuff? Observium or Librenms will collect pretty much any server related stat that you could ever need. Those will chart and graph things like CPU, RAM, Disk IO, Network Graphs, uptime, etc all over time. From very recent to multiple years if you keep it running long enough.

1