Re: Resolving 0.2.1.7 issue

To: or-talk@xxxxxxxxxxxxx

Subject: Re: Resolving 0.2.1.7 issue

From: "Kyle Williams" <kyle.kwilliams@xxxxxxxxx>

Date: Fri, 5 Dec 2008 16:08:48 -0800

Delivered-to: archiver@xxxxxxxx

Delivered-to: or-talk-outgoing@xxxxxxxx

Delivered-to: or-talk@xxxxxxxx

Delivery-date: Fri, 05 Dec 2008 19:08:55 -0500

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=vSSv2jjFBrzr54iwnDV6PdBtOEwysT7Tt7xdHVcPCKc=; b=imRRYAZTFp5KUxhQSmCIrtD/0whK1Vw4MZiZf1X9tEPbsxXj9kbR092Kx0IiKb3WZA 9KX58zjPQIxzuQEfgh/0SGFYnuSz0urVu91jVi5408CAb1DZSQWC725HmFCmv06/4x9f Oz7p8Rt/WiC6Xtm55axvXbRCXDFFN6IpF/F7U=

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=sNuw5Obk6mBbfXH6UncBp6qHglhhVlpF/3vbSsLX3caY9ObHbV/vjVemxWsFzCv3mZ MFHo5awadAUSpoYwN3cUAmsocUoii5kUSmxPHvQk0lgpGOELK43KL7eD/L4FVUudwb1i d0OUdAySzcZdK+EElszQJLCYzuWQ61nPynxXM=

In-reply-to: <49392422.8070103@xxxxxxxx>

References: <49375057.7090905@xxxxxxxx> <20081204052318.GA18107@xxxxxxxxxxxxxxxxxxx> <49392422.8070103@xxxxxxxx>

Reply-to: or-talk@xxxxxxxxxxxxx

Sender: owner-or-talk@xxxxxxxxxxxxx

0.2.1.7

Verizon FIOS worked great. Tor was even cross-compiled for ARM architecture. I ran it for a few days. No problems here.

Comcast would catch any invalid DNS request and re-direct the request to their search site.

The way I solved this was to change my DNS servers to 4.2.2.1 and 4.2.2.2 and not use the DNS servers comcast gives out with DHCP.

Just my 2 cents.

- Kyle

On Fri, Dec 5, 2008 at 4:52 AM, Alessandro Donnini <alexdonnini@xxxxxxxx> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

0.2.1.7 in relay node configuration has been running apparently normally for the
last 30 hours.

The only message (recurring) in the log is:

Dec 05 07:45:26.964 [Notice] We stalled too much while trying to write 179 bytes
to address [scrubbed]. If this happens a lot, either something is wrong with
your network connection, or something is wrong with theirs. (fd 19720, type
Directory, state 1, marked at main.c:704).

My Internet connection is FIOS (fiber from Verizon), and I don't seem to be
having problems with it.

Alex

phobos@xxxxxxxxxx wrote:
> On Wed, Dec 03, 2008 at 10:36:55PM -0500, alexdonnini@xxxxxxxx wrote 0.8K bytes in 26 lines about:
> : So far, so good, Tor is configured to run as a relay node (nessuno), and seems
> : to be running normally. The logs appear to be normal (no warnings or errors).
>
> Great. If you see errors relating to nameservers, please keep us
> informed.
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkk5JCIACgkQ3ju7mowpX9VHAwCeMDZq9OVh00JXedosILn3E1oc
tjsAn0V/eEhm4yOJF4eqSBRyBpWfsA61
=FnTX
-----END PGP SIGNATURE-----