From owner-freebsd-net@FreeBSD.ORG  Sat Sep  6 15:52:07 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id AC7CA25B
 for <freebsd-net@freebsd.org>; Sat,  6 Sep 2014 15:52:07 +0000 (UTC)
Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com
 [IPv6:2a00:1450:4010:c04::22e])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 37FD615B4
 for <freebsd-net@freebsd.org>; Sat,  6 Sep 2014 15:52:07 +0000 (UTC)
Received: by mail-lb0-f174.google.com with SMTP id n15so5259985lbi.19
 for <freebsd-net@freebsd.org>; Sat, 06 Sep 2014 08:52:04 -0700 (PDT)
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=QZ71zr8JYUSlTnT04zhKP1w66c6QLk9Tc2TGtP3RFyA=;
 b=OBykHmqBMhunmed88vDVc9LYStM40joqb+YLob+LydGAXXIDyeS8B5lVD7impfWSkB
 Uh7mDyeHJ/4xm9JwDuG7zZ5tRNJM77aH7Lt7tGE66LXB5u+iWaYDIh7ziOn6PLcu2gso
 bL96VltoSM47tuF+TG+uRmw/1f9+8NyzdL8ieH/Ze9dM9OzVLmz7OcoO1wpmA4ei6AeB
 ht4dQ6C4TKwP3uxdk5cySZGG1iBaG54H/MyKA+e1ao/u0GfvuNVhr2DJlUXNQKfolL8W
 mlXdXSIvjgEuSvUp5G4gsBvYwn2W1QDlHUCDIBgtR7gKf0YSvyifJK/PVyfn61G8BX5a
 dtqA==
MIME-Version: 1.0
X-Received: by 10.112.33.74 with SMTP id p10mr17379294lbi.0.1410018724577;
 Sat, 06 Sep 2014 08:52:04 -0700 (PDT)
Received: by 10.25.20.165 with HTTP; Sat, 6 Sep 2014 08:52:04 -0700 (PDT)
In-Reply-To: <Pine.NEB.4.64.1409060233080.2500@faeroes.freeshell.org>
References: <Pine.NEB.4.64.1409060233080.2500@faeroes.freeshell.org>
Date: Sat, 6 Sep 2014 11:52:04 -0400
Message-ID: <CAFMmRNwHiF9DcMaGuQDWxwZNN1YnwhTC1nekv1HjUuhO_Bz_pw@mail.gmail.com>
Subject: Re: How can sshuttle be used properly with FreeBSD (and with DNS) ?
From: Ryan Stone <rysto32@gmail.com>
To: John Case <case@sdf.org>
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-net <freebsd-net@freebsd.org>
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
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: Sat, 06 Sep 2014 15:52:07 -0000

I'm unable to get sshuttle to redirect DNS traffic even on a machine
that doesn't have any other ipfw rules running, so I don't think that
it's a conflict with your divert rules causing the problem.
Unfortunately I don't have a solution to your problem.  When I need to
use sshuttle I run it from a Linux machine instead.