Re: contradicting log entries regarding ExcludeNodes

[Tristan Helmich <Tristan@xxxxxxxxxxx>]

Roger Dingledine wrote:
> This is because you specified it both as a nickname and as a key. You
> should specify it just as a key, and this warning will go away:
> ExcludeNodes $3B1CD4DC4863DD1013E7C35A6F475C28946AB909
>   
Ok, no more Warnings.
>> Aug 14 03:43:00.345 [notice] Tor has successfully opened a circuit.
>> Looks like client functionality is working.
>> Aug 14 03:45:06.111 [notice] We tried for 15 seconds to connect to
>> '[scrubbed]' using exit 'nami'. Retrying on a new circuit.
>> Aug 14 03:45:06.115 [notice] We tried for 15 seconds to connect to
>> '[scrubbed]' using exit 'nami'. Retrying on a new circuit.
>>     
>
> You should add 'SafeLogging 0' to your torrc to see what the value
> of [scrubbed] is, but I suspect this is DirPort reachability testing.
> Are you *sure* you're looking at your Tor client's logs? It looks more
> like your Tor server's logs.
Yes, i am sure this is my clients log file. I added 'SafeLogging 0' and
found this:
Aug 16 14:43:52.170 [notice] We tried for 15 seconds to connect to
'84.145.85.140' using exit 'nami'. Retrying on a new circuit.

'84.145.85.140' is my own webserver at this time (dynamic ip-address),
the same as running tor node 'nami'. I also noticed my ip-address
several times while checking ipchicken.com and whatismyip.com. I made
sure the browser is configured to use tor (which apparently is working
fine or i would not be able to see the notice stated above).

I still do not understand why my tor client is building circuits ending
at node 'nami' even if forbidden by ExcludeNodes.

Best regards
Tristan