From owner-freebsd-stable@FreeBSD.ORG  Tue May  1 19:41:35 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 59E9D106564A
	for <freebsd-stable@freebsd.org>; Tue,  1 May 2012 19:41:35 +0000 (UTC)
	(envelope-from lx@redundancy.redundancy.org)
Received: from redundancy.redundancy.org (75-101-96-57.dsl.static.sonic.net
	[75.101.96.57]) by mx1.freebsd.org (Postfix) with SMTP id 2186D8FC0C
	for <freebsd-stable@freebsd.org>; Tue,  1 May 2012 19:41:35 +0000 (UTC)
Received: (qmail 37225 invoked by uid 1001); 1 May 2012 19:41:25 -0000
Date: Tue, 1 May 2012 12:41:25 -0700
From: David Thiel <lx@redundancy.redundancy.org>
To: freebsd-stable@freebsd.org
Message-ID: <20120501194101.GD66263@redundancy.redundancy.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13
X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg
X-Face: %H~{$1~NOw1y#%mM6{|4:/<p]y9X%E+4%:1wo-M!re,
	zl.qH~yzbL-MWhtp$3QuKP&di/a{FOctD[FuX.\n4U*,
	M{TJg$oYp663.NyX!%H~~Tw$eR9xZU5W?1BM#t"a@'27^2x
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Jails can't get routing info
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 19:41:35 -0000

Hello,

So, I've been trying to debug an issue running nmap scans within jails, 
partially documented here:

http://seclists.org/nmap-dev/2012/q2/220

On further debugging, it's seeming like jails can't read routing 
information directly at all:

# route get 69.163.203.254
route: writing to routing socket: No such process

Now, this is normally done via reading the routing table via something like 
socket(PF_ROUTE, SOCK_RAW, AF_INET), so one would suspect that this is a 
problem with raw sockets; but raw sockets are enabled within the jail. 
netstat is able to read routing information just fine, but I don't think 
it's doing it via the socket() call.

Anyone know why this behavior might be happening?

Thanks,
David