Plan:
Configure relay on local cable connection (Century Link). The
idea
is
to have the relay proofed operational the way I want it and then
move
it (torrc) to a droplet after it has been in operation for three
days. Doing
this saves cost in downloading to the droplet.
Modem Zyxel C3000 was set to port forward on 9001, 9030, and 9050
IP 192.XXX.X.X
Turn off UpnP (plug and play) <relay fails with it on>
GUFW is set to allow the above ports – reload to allow changes
after much struggling/research to open ports 9001/9030
nc -zv 127.0.0.1 9001/9030
Connection to 127.0.0.1 9001 port [tcp/*] succeeded! <9030 also>
Alrighty then!
Tor –verify-config <many probs here, but cleared> No complaints
NOTE:
I know tor.Nyx should not be run as root, I get that. Tor/Nyx
are
running as root. I don’t know how to use debian-tor as usr. Nyx
shows in it’s configuration as usr debian-tor. Su debian-tor
produces
a rollover back to root usr prompt.
service tor start
Nyx
– No complaints, running as default. After just two minutes of
operation the relay was running at 2 MB/s with bursts up to 3
MB/s.
After the obligatory/frustrating twenty minute wait for
or/dirport
hand shaking I get: orport/dirport
unreachable…. Adnauseum!
Changed IP address to one given by tor,
still unreachable. Lastly,
I removed the 900l/9030 ports from the
modem and installed
6969 as the orport. Changed GUFW, verified the
changes took
place, changed ip to real world IP 63.xxx.xxx.xxx in
torrc. Hand
shaking to the orport was almost immediate. Right now,
the relay
after twenty
hours of operation is tortusing along at 20 B/s.
Which to me is pure
BS.
Can someone give me some idea’s as to what I am doing wrong?
Kathi
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays