Florian Kulzer wrote:
On Wed, Jun 03, 2009 at 18:31:43 +0100, AG wrote:
AG wrote:
Hello
I am attempting to get Tor and Privoxy working with Iceweasel, but it
keeps throwing up errors.
[...]
The following is my /etc/privoxy/config file (without the commented
sections):
[...]
listen-address localhost:8118
[...]
I purged tor and privoxy, adjusted my sources.list to lenny and
reinstalled both tor and privoxy, amended privoxy/config and restarted
privoxy. Then I fired up Iceweasel and viola! I now have an active tor
and privoxy arrangement.
I have now managed to reproduce your problem by configuring privoxy to
listen on the ipv6 address of localhost, i.e. by making this change to
/etc/privoxy/config:
listen-address [::1]:8118
As soon as I restart privoxy after that, the iceweasel/privoxy/tor
combination stops working.
This means that the problem is definitely related to the ipv6 patch. The
error message that you posted in one of your previous messages also
suggests that your communictaion problem was between iceweasel and
privoxy.
So, the version of privoxy that appears to work best for me is 3.0.9-1,
whilst the one that didn't was 3.0.12-2_i386 I don't know why or how,
but there you go.
That makes sense because the Lenny version does not have the ipv6 patch.
(The patch was disabled in version 3.0.5-beta-3 and reenabled in
3.0.10-2.) I bet that you now find privoxy listening on 127.0.0.1:8118
if you run the "netstat -plant" command again.
It seems that "localhost" resolves to the ipv6 address on your system,
at least as far as the privoxy configuration is concerned, while for me
it still yields the ipv4 address. The following might therefore be a
workaround for the 3.0.12-2 version of privoxy on your installation:
listen-address 127.0.0.1:8118
It would probably be better to find out why "localhost" is interpreted
differently on your box. To this end, I would like to see the output of
getent hosts localhost
and the contents of your /etc/hosts file.
Florian
Your assumption looks spot on about defaulting to ipv6, as can be seen
below:
Working from the bottom back up:
/etc/hosts
127.0.0.1 localhost
192.168.1.40 owndomain.org owndomain
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
and then ...
$ getent hosts localhost
::1 localhost ip6-localhost ip6-loopback
This is a new machine with a SATA drive, although I did install the same
ethernet card that I had in my previous box (which worked fine with Tor
and Privoxy), so I don't know if I inadvertently configured it that way
when I did the fresh install on Saturday last.
And as you suspected, Iceweasel does indeed listen in on 8118, as seen by:
$ netstat -plant
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address
State PID/Program
name
tcp 0 0 127.0.0.1:3306 0.0.0.0:*
LISTEN
-
tcp 0 0 0.0.0.0:111 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:7634 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:8118 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:631 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:25 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:9050 0.0.0.0:*
LISTEN
-
tcp 0 0 0.0.0.0:54779 0.0.0.0:* LISTEN
At this point I am okay with having the Lenny ipv6-non-patched tor and
privoxy arrangement. However, if you are recommending that I do attempt
the workaround then I will do so. This will presumably mean allowing
the two packages to be updated as the Update Notifier wants to keep
doing? If not, then I need to figure out how to stop the UN from
insisting that these packages need upgrading.
Once again, many thanks Florian.
AG
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org