Hello,
yes you're right. It looks like I accidentally routed all traffic
through tor due to a faulty firewall rule. It was a bit confusing,
because of the quickly updates with the right IP. It took me a while to
understand the background.
Thanks a lot for your help
Regards,
On 20.12.2016 19:35,
Hello,
sorry, it also was a bit confusing for me as I've seen the logs. Yes,
you are right. I am running a tor node and a ddclient on the same
machine. Tor client and relay is running in a jail. So, it might be
error, because of a faulty firewall rule. It looks like, I've routed all
traffic though
I'm familiar with DynDNS and the client. The client tries to detect your
external IP address in order to keep your dynamic DNS record pointed at your
current IP. It looks to me like you're running it on a machine that's routing
through Tor. So it picks up the IP address of the Exit you're routed
Hello,
I'm part of the abuse team of the mentioned Tor Exit.
Also I follow this mailing list.
I read you post several times but I'm not sure what you where doing.
It looks to me like you running a tor node and have also a dyndns update
process running.
Is this correct ? Please provide some more
Hi!
Yesterday I encountered a strange IP address update via DynDNS:
Dec 19 23:00:32.000 [notice] Your IP address seems to have changed to
176.10.104.240 (METHOD=RESOLVED HOSTNAME=my.dyndns.cc). Updating.
Dec 19 23:00:32.000 [notice] Our IP Address has changed from xx.xx.xx.xx
to 176.10.104.240; r
