Thanks for answer. But main question was not about provider .. (is TOR
friendly).
I was surprised, that my IP is stored in Exit policy as reject.
I was afraid .. that all trafic is droped, but now seems all is OK. (IP is
still in exit policy, but chart showing traffic)
Thanks
cmar
On Mon, Mar 30, 2015 at 12:45 PM, Roger Dingledine a...@mit.edu wrote:
On Mon, Mar 30, 2015 at 12:23:21PM -0400, Zack Weinberg wrote:
The only way your exit node's own IP address could be in the exit
policy is if someone put it there.
No, this is fine and normal. Tor relays automatically add
Hopefully I won't be adding too much confusion into the conversation...
When you see reject 37.157.192.208:*, it means not to accept anything
sourced from your IP. For example, if you were to run a Tor client on
your server that's running the relay, you would not be able to exit the
Tor network
My torrc not contain my ipadress as exit policy.
But I can see it in globe.
I read somewhere, that TOR is reading some blacklists and implement this
blacklist to exit policy, like central management. Beacuse i was (my ip adress)
in the blacklist ...
But i cannot find now where .. ..Maybe was
On Mon, Mar 30, 2015 at 11:45 AM, Cmar433 cmar...@yandex.com wrote:
Thanks for answer. But main question was not about provider .. (is TOR
friendly).
I was surprised, that my IP is stored in Exit policy as reject.
Oh! I'm sorry, I did not understand what you were asking at first.
The only
On Mon, Mar 30, 2015 at 12:23:21PM -0400, Zack Weinberg wrote:
The only way your exit node's own IP address could be in the exit
policy is if someone put it there. Maybe you did that and you don't
remember doing it? If you didn't do it, then you might indeed have
had your node broken into,
Cool; I've been meaning to see if I could lend a hand with any of the
Tor-related codebases, I'll take a look into it and see if I can help
out when I get some time.
Sharif
--
PGP: 6FB7 ED25 BFCF 3E22 72AE 6E8C 47D4 CE7F 6B9F DF57
signature.asc
Description: PGP signature
Hi all,
I configured a new relay[0] yesterday, and recently tried to sign up for
the Weathermap[1], wherein I get a could not locate a Tor node with
that fingerprint error message. The node's definitely been up for more
than an hour, and Atlas can see it[2]. Is this expected behaviour, or
might
On March 31, 2015 12:41:42 AM Sharif Olorin s...@tesser.org wrote:
Hi Sharif,
Hi all,
I configured a new relay[0] yesterday, and recently tried to sign up for
the Weathermap[1], wherein I get a could not locate a Tor node with
that fingerprint error message. The node's definitely been up for
On March 31, 2015 1:12:21 AM Sharif Olorin s...@tesser.org wrote:
Hi,
It can take a while, just try again in the next 24-48 hours. Don't worry
right now.
Ah, thanks, good to know. Might it be worth updating the fingerprint not
found page to say a few days rather than an hour? The current
After months of trying to figure out where the bottleneck in my relay is
(I'm on gigabit down/up connection, but relay won't push more than
10mbps), I was poking through my NVG589 router's NAT Table and noticed
Total sessions available 2560
Total sessions in use 2048
Followed by a table
It can take a while, just try again in the next 24-48 hours. Don't worry
right now.
Ah, thanks, good to know. Might it be worth updating the fingerprint not
found page to say a few days rather than an hour? The current
version seems to imply that it's expected to be working inside that
Sharuf,
I completely forgot to welcome you and thank you for running a relay !
So, welcome and i hope you stay for quite a while :-)
--
Sincerely yours / Sincères salutations / M.f.G.
Sebastian Urbach
-
Religion is fundamentally opposed to
everything I
Am 30.03.2015 um 15:04 schrieb Cmar433:
Now i can see my IP in my server exit policy ...
Well you probably added that in the beginning, reject 37.157.192.208:*
will cause that you exit relay will reject any connections to the IP
37.157.192.208, which is the IP Tor is running on. That means
14 matches
Mail list logo
