Hi All,
I think we are deviating from the issue here. I have installed Tor.. Everything is good on my Pi 2 All i want to know is how do i open ports for Tor on my NetGear DGN1000 router Thanks, Bunty ----------------------------------------------------------------------------------------- > From: 12xbtm@xxxxxxxxx > Date: Tue, 23 Jun 2015 23:36:56 -0400 > To: tor-relays@xxxxxxxxxxxxxxxxxxxx > Subject: Re: [tor-relays] Raspberry Pi - Relay Setup > > Let me add to this since I have a raspberry pi 2 tor relay: > > First off, I run debian jessie on my pi2, but pi2 supports debian > wheezy. Make sure you harden your SSH to attack. You'll want to dedicate > as little ram to graphics as possible. You also want to have > AvoidDiskWrites and CPUNums in your torrc file as well, the details of > which can be found in the tor debian manual. > > As for performance: My stock Pi2 averages about 30-40% load when it > bursts to 25Mbit/s, which saturates the connection. Thus, scaling > somewhat linearly, a Pi2 overclocked could probably handle a > 50-100Mbit/s connection. But you'll want to monitor things closely in > the beginning since there isn't much wiggly room on the Pi2. For > example, my image of debian jessie had a irqbalance service that had a > memory leak and was eating all the ram, which plagued my stability in > the first few weeks. > > Also, you want a quality power supply, and, if it's a hot environment > and/or overclocking, a heat sink. Security and stability are the most > important, and the Pi2 can easily handle a residential connection as a > non-exit node, I only wish I had the connections to utilize my hardware. > > On 23.6.15 20:50, s7r wrote: > > Just install Tor: > > > > sudo apt-get -y install tor > > > > and edit the torrc file: > > nano /etc/tor/torrc > > > > make it a relay by adding this content (add your values and data): > > ORPort <port> > > Nickname <your nickname> > > ContactInfo <your email> > > ExitPolicy reject *:* > > > > *If you are behind NAT, make sure the ports are properly forwarded to > > your raspberry pi. Use a static internal IP for the raspberry pi so the > > port forwarding rules will remain active in case of a reboot. > > > > Note the raspberry pis are ok (if the internet connection speed is also > > good) but cannot handle as many concurrent Tor circuits as a real server > > would. If your internet bandwidth is capped, maybe try running an obfs4 > > bridge on the raspberry pi. > > > > On 6/23/2015 10:53 PM, Tor Zilla wrote: > >> I did not say i want to setup an exit relay. > >> > >> I am looking forward to setup a Non-exit relay > >> > >> =================================== > >> > >>> Date: Tue, 23 Jun 2015 21:39:01 +0200 > >>> From: tor@xxxxxxxxxxx > >>> To: tor-relays@xxxxxxxxxxxxxxxxxxxx > >>> Subject: Re: [tor-relays] Raspberry Pi - Relay Setup > >>> > >>> I don't know in which country you live but an exit relay with your > >>> private internet connection might bring you in legal trouble. > >>> > >>> On 06/23/2015 09:26 PM, CJ Barlow wrote: > >>>> What model of NetGear do you have? > >>>> > >>>> A static IP is not required. You may need to setup a Dynamic DNS if tor > >>>> has issues with your dynamic IP. > >>>> > >>>> > >>>> On Tue, Jun 23, 2015, 13:22 Tor Zilla <torzilla11@xxxxxxxxxxx > >>>> <mailto:torzilla11@xxxxxxxxxxx>> wrote: > >>>> > >>>> Hello All, > >>>> > >>>> I just bought a Raspberry Pi.. Wanted to setup as a Tor non exit relay. > >>>> > >>>> I have read so many instructions online on how to set it up but i am > >>>> facing issues with opening ports. > >>>> > >>>> I am using a NetGear Router and require your inputs with the same. > >>>> > >>>> Also is static IP mandatory for setting up a relay? > >>>> > >>>> > >>>> Thanks, > >>>> TorZilla11 > >>>> _______________________________________________ > >>>> tor-relays mailing list > >>>> tor-relays@xxxxxxxxxxxxxxxxxxxx <mailto:tor-relays@xxxxxxxxxxxxxxxxxxxx> > >>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> tor-relays mailing list > >>>> tor-relays@xxxxxxxxxxxxxxxxxxxx > >>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > >>>> > >>> _______________________________________________ > >>> tor-relays mailing list > >>> tor-relays@xxxxxxxxxxxxxxxxxxxx > >>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > >> > >> _______________________________________________ > >> tor-relays mailing list > >> tor-relays@xxxxxxxxxxxxxxxxxxxx > >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > >> > > _______________________________________________ > > tor-relays mailing list > > tor-relays@xxxxxxxxxxxxxxxxxxxx > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > _______________________________________________ > tor-relays mailing list > tor-relays@xxxxxxxxxxxxxxxxxxxx > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays |
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays