Re: [tor-relays] Faravahar messing with my IP address

2015-11-15 Thread Tim Wilson-Brown - teor
> On 9 Nov 2015, at 23:02, teor wrote: > > On 9 Nov 2015, at 20:45, Roger Dingledine > wrote: > >> On Mon, Nov 09, 2015 at 08:04:55PM +1100, Tim Wilson-Brown - teor wrote: >>> Subsequent queries get the same IP address for several tens

Re: [tor-relays] Faravahar messing with my IP address

2015-11-09 Thread Tim Wilson-Brown - teor
> On 9 Nov 2015, at 18:56, Matthew Finkel wrote: > > Which version of Tor were you previously running? Have you seen these > messages within the last few days, after you upgraded? > Hi SiNA, Matthew, I can reproduce some unusual behaviour from Faravahar simply using

Re: [tor-relays] Faravahar messing with my IP address

2015-11-09 Thread Roger Dingledine
On Mon, Nov 09, 2015 at 08:04:55PM +1100, Tim Wilson-Brown - teor wrote: > Subsequent queries get the same IP address for several tens of seconds > afterwards. Woah. Are we setting the Expires: http header in our Tor answer based on how long we think the *payload* will remain valid, and the

Re: [tor-relays] Faravahar messing with my IP address

2015-11-09 Thread Matthew Finkel
On Sat, Oct 24, 2015 at 03:09:00AM +0300, s7r wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello, > > Unfortunately this is not the first time we see this, and it did > happen before Faravahar IP address change and before it was > experiencing very high latency ( >

Re: [tor-relays] Faravahar messing with my IP address

2015-11-09 Thread teor
On 9 Nov 2015, at 20:45, Roger Dingledine > wrote: > On Mon, Nov 09, 2015 at 08:04:55PM +1100, Tim Wilson-Brown - teor wrote: >> Subsequent queries get the same IP address for several tens of seconds >> afterwards. > > Woah. Are we setting the Expires: http

Re: [tor-relays] Faravahar messing with my IP address

2015-11-08 Thread Matthew Finkel
On Wed, Nov 04, 2015 at 08:00:52AM +0100, Logforme wrote: > Happened again tonight: > > Nov 04 05:23:43.000 [notice] Our IP Address has changed from > 84.219.173.60 to 185.99.185.61; rebuilding descriptor (source: > 154.35.175.225). > Nov 04 05:23:43.000 [notice] Self-testing indicates your

Re: [tor-relays] Faravahar messing with my IP address

2015-11-03 Thread Logforme
Happened again tonight: Nov 04 05:23:43.000 [notice] Our IP Address has changed from 84.219.173.60 to 185.99.185.61; rebuilding descriptor (source: 154.35.175.225). Nov 04 05:23:43.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server

Re: [tor-relays] Faravahar messing with my IP address

2015-10-24 Thread Aeris
> I just got something strange too: > > Oct 22 20:42:24.000 [notice] Guessed our IP address as 77.206.60.235 > (source: 154.35.175.225). > Oct 22 20:42:25.000 [notice] Our IP Address has changed from > 77.206.60.235 to 149.18.2.82; rebuilding descriptor (source: > 199.254.238.52). Hello guys,

Re: [tor-relays] Faravahar messing with my IP address

2015-10-23 Thread teor
> On 23 Oct 2015, at 09:30, Green Dream wrote: > > I see this from time to time as well. Here's another example: > > Oct 17 23:02:44.000 [notice] Our IP Address has changed from 52.64.142.121 > to [CORRECT IP]; rebuilding descriptor (source: 86.59.21.38). > >

Re: [tor-relays] Faravahar messing with my IP address

2015-10-23 Thread Green Dream
Sina, the ticket 16205 regarding incorrect IPs coming from Faravahar is 5 months old [1]. Have you had a chance to look into the possible explanation Nick Suan mentioned earlier in the thread? It's not exactly confidence-inspiring to see multiple unresolved tickets about Faravahar going back

Re: [tor-relays] Faravahar messing with my IP address

2015-10-23 Thread s7r
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, Unfortunately this is not the first time we see this, and it did happen before Faravahar IP address change and before it was experiencing very high latency ( https://trac.torproject.org/projects/tor/ticket/17338 ). See:

Re: [tor-relays] Faravahar messing with my IP address

2015-10-22 Thread Nicholas Suan
Aren't the iptables rules going to change the source address of the forwarded traffic to the IP of the old server, causing it to misreport IP addresses? On Thu, Oct 22, 2015 at 1:38 PM, SiNA Rabbani wrote: > Dear Relay Operator, > > I am the operator of Faravahar, It has been

[tor-relays] Faravahar messing with my IP address

2015-10-22 Thread Logforme
I run the relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC34) Saw this in yesterday's log file: Oct 22 03:17:55.000 [notice] Our IP Address has changed from 84.219.173.60 to 154.35.32.5; rebuilding descriptor (source: 154.35.175.225). Oct 22 03:17:55.000 [notice] Self-testing indicates your

Re: [tor-relays] Faravahar messing with my IP address

2015-10-22 Thread SiNA Rabbani
Dear Relay Operator, I am the operator of Faravahar, It has been having some network issues, specifically very long latency. But this is the first time I hear of an issue like this. 154.35.32.5 is Faravahr's older IP addresses which was replaced with and 154.35.175.225 is the new IP (current).

Re: [tor-relays] Faravahar messing with my IP address

2015-10-22 Thread Pascal Terjan
On 22 October 2015 at 19:22, Logforme wrote: > I run the relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC34) > > Saw this in yesterday's log file: > Oct 22 03:17:55.000 [notice] Our IP Address has changed from > 84.219.173.60 to 154.35.32.5; rebuilding descriptor (source: >

Re: [tor-relays] Faravahar messing with my IP address

2015-10-22 Thread Green Dream
I see this from time to time as well. Here's another example: Oct 17 23:02:44.000 [notice] Our IP Address has changed from 52.64.142.121 to [CORRECT IP]; rebuilding descriptor (source: 86.59.21.38). 52.64.142.121 appears to be an instance on Amazon's EC2. I don't run any nodes on EC2.