From owner-freebsd-net@FreeBSD.ORG  Wed Nov 14 05:32:27 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 8EC39D1C
 for <freebsd-net@freebsd.org>; Wed, 14 Nov 2012 05:32:27 +0000 (UTC)
 (envelope-from eugen@grosbein.net)
Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5])
 by mx1.freebsd.org (Postfix) with ESMTP id E173F8FC08
 for <freebsd-net@freebsd.org>; Wed, 14 Nov 2012 05:32:26 +0000 (UTC)
Received: from eg.sd.rdtc.ru (localhost [127.0.0.1])
 by eg.sd.rdtc.ru (8.14.5/8.14.5) with ESMTP id qAE5WIva041919;
 Wed, 14 Nov 2012 12:32:19 +0700 (NOVT)
 (envelope-from eugen@grosbein.net)
Message-ID: <50A32CDD.5000109@grosbein.net>
Date: Wed, 14 Nov 2012 12:32:13 +0700
From: Eugene Grosbein <eugen@grosbein.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU;
 rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7
MIME-Version: 1.0
To: Dustin Wenz <dustinwenz@ebureau.com>
Subject: Re: Default ephemeral port range
References: <87A2D317-77BA-4641-979D-0AE43247D99E@ebureau.com>
 <95686CBD-5A11-48BD-A556-5133F537C82E@gmail.com>
 <2EEDF65D-C235-48A7-9464-82475C26E9DD@ebureau.com>
In-Reply-To: <2EEDF65D-C235-48A7-9464-82475C26E9DD@ebureau.com>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 8bit
Cc: freebsd-net@freebsd.org, Colin O'Keeffe <cokeeffe@gmail.com>
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: Wed, 14 Nov 2012 05:32:27 -0000

14.11.2012 04:48, Dustin Wenz пишет:
> Thanks for the information;
> 
> It would seem that when I invoke the connect() system call, it picks a client port in the portrange.first-last range and not necessarily in portrange.hifirst-hilast. Is this expected behavior, or a bug in connect()?

Please read ip(4) manual page on IP_PORTRANGE. You can choose one of three ranges
for your socket (default range, low and high).

Eugene Grosbein