From owner-freebsd-net@FreeBSD.ORG  Tue Dec 25 19:48:04 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 39AE973A
 for <freebsd-net@freebsd.org>; Tue, 25 Dec 2012 19:48:04 +0000 (UTC)
 (envelope-from yanegomi@gmail.com)
Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com
 [209.85.214.179])
 by mx1.freebsd.org (Postfix) with ESMTP id ED1BD8FC12
 for <freebsd-net@freebsd.org>; Tue, 25 Dec 2012 19:48:03 +0000 (UTC)
Received: by mail-ob0-f179.google.com with SMTP id x4so7467763obh.10
 for <freebsd-net@freebsd.org>; Tue, 25 Dec 2012 11:48:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=yIRaPpfyJ1KVeExGD+w1B4a31O5XOjehQ5mFcsmyX4w=;
 b=StEFY3tKuDR7KbroUjsWlcfKOxikLwu/mPnPfAAvFvQ5hCIhe+QZVJWNRKNZ7+6hLt
 Hwd5xaqLLVNYdiAYqfidrdVGbHu6Q3cpv2NUHw2kVqe4hM+D0ZFCTCCwmYWbMlMQJPI9
 W4sykn9aO+D5fvWQYvm1Dp35oyKwV+a5UELMpLoBtz405l+LiujTVe0ajwRZ9xmSIJa/
 XSrJVEW8MT8SBDxET3d+W6KteCpIEX905kALbnibhM5dqjBLh0LCttXqBaWMAy5gezDw
 wjdjDvMh856JozG3nc4f0OpHWQwH24ZMXvOj5hMByWucJis1hXx4OwihXcKP0m2i2BgE
 ymbQ==
MIME-Version: 1.0
Received: by 10.60.6.226 with SMTP id e2mr9409999oea.56.1356464882939; Tue, 25
 Dec 2012 11:48:02 -0800 (PST)
Received: by 10.76.143.33 with HTTP; Tue, 25 Dec 2012 11:48:02 -0800 (PST)
In-Reply-To: <50D94D04.90302@rawbw.com>
References: <50D94D04.90302@rawbw.com>
Date: Tue, 25 Dec 2012 11:48:02 -0800
Message-ID: <CAGH67wRipaHgtznXcZuTZDg9HARp37D+t9zWRQNJiVvfKV__NQ@mail.gmail.com>
Subject: Re: Why chrome and firefox can't connect to almost any SOCKS4 proxy?
From: Garrett Cooper <yanegomi@gmail.com>
To: Yuri <yuri@rawbw.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-net@freebsd.org
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Dec 2012 19:48:04 -0000

On Mon, Dec 24, 2012 at 10:51 PM, Yuri <yuri@rawbw.com> wrote:
> I tried many SOCKS4 proxies from
> http://sockslist.net/proxy/server-socks-hide-ip-address and mostly I am
> getting this error:
> Error 120 (net::ERR_SOCKS_CONNECTION_FAILED): Unknown error.
> Only one of them succeeded.
> SOCKS5 however works ok.
>
> On firefox I am getting similar symptoms, it can't connect to most SOCKS4
> proxies and can connect to SOCKS5.
>
> What might be a problem? I was thinking that maybe some system or port
> library has some issue related to SOCKS4? Maybe libssl.so ?

    Try trussing/ktrace'ing the process to see if you can get a bit
more diagnostic information. If that doesn't yield anything helpful,
you might want to consider possibly going to the forums to ask this
question because this seems like something that is application
specific that wouldn't necessarily be well tied to -net@.
HTH,
-Garrett