[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: My tor exit node is STILL gone from the node list

To: or-talk@xxxxxxxxxxxxx
Subject: Re: My tor exit node is STILL gone from the node list
From: Lee <ler762@xxxxxxxxx>
Date: Mon, 20 Jul 2009 14:33:12 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Mon, 20 Jul 2009 14:33:17 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=lSA61S+qo0afzAqS/dx1Oz1bRYeNlA/qxaceZS1/ON8=; b=G7dO9yb7qdwMSNkEnsBapUSpyPMzx2Hy0vmJRuycIjQxZBdieMF0/QrrAsGgyG11xe ymLkO7G4tfZ69WVtZdw1+ImdiD3dtwAprbU9+Ua5DbezZwWGWJcrIxprJFZ4u/pOOh7y ACIxKniquK9KlP7k8P+5GpdaiYncfV7osDA0U=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=sVp7hVDSWuC9SnE8nnxFeLmxOjA1fA6MSR0AK9yBGoqnXHrxxmsoqbxjVDOEDF4GRv o3EqWqbIKqW9AQ1pxLw2+2kmntgifvewcOga5ThI4O7nfV2tvBdpSzsiZPz2ksCGVRvA nrRfEOCMKZt9X6z0e5VBhUdqK0cribcKJkxU0=
In-reply-to: <4A64B4D0.7070507@xxxxxxxxxxxx>
References: <9909e4a86274b69789f99f7c50ab106c15654a0bdce3eeea7@localhost> <d5d2e73f20778d739d210bccc9b925f4134004a64913b7299f@localhost> <4A649C93.8010905@xxxxxxxxxxxx> <dd5f2deb0907201013h557703f9n525a3538da2cb999@xxxxxxxxxxxxxx> <4A64B4D0.7070507@xxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

On 7/20/09, Olaf Selke <olaf.selke@xxxxxxxxxxxx> wrote:
> Lee schrieb:
>> Considering how many places block ICMP, traceroute is not a good way
>> to determine connectivity.
>>
>> telnet 89.248.169.109 80
>> works for me and traceroute doesn't:
>
> oops, you're right! The same here. I didn't notice that before.
> Nevertheless blocking icmp at peering points is very unusual. Maybe path
> mtu discovery is broken if icmp is completely blocked.

No maybe about it - if icmp is completely blocked path mtu discovery
_is_ broken.

89.248.169.109 doesn't answer a ping, so I don't know of an easy way
to check if that's the problem or no.

Lee

Follow-Ups:
- Re: Re: My tor exit node is STILL gone from the node list
  - From: Alexandru Cezar

References:
- My tor exit node is STILL gone from the node list
  - From: Alexandru Cezar
- Re: My tor exit node is STILL gone from the node list
  - From: Olaf Selke
- Re: My tor exit node is STILL gone from the node list
  - From: Lee
- Re: My tor exit node is STILL gone from the node list
  - From: Olaf Selke

Prev by Author: Re: My tor exit node is STILL gone from the node list
Next by Author: Re: Re: My tor exit node is STILL gone from the node list
Previous by thread: Re: My tor exit node is STILL gone from the node list
Next by thread: Re: Re: My tor exit node is STILL gone from the node list
Index(es):
- Author
- Thread