From owner-freebsd-net@FreeBSD.ORG Tue Aug 29 08:11:08 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2479D16A4DA for ; Tue, 29 Aug 2006 08:11:08 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68C8543D46 for ; Tue, 29 Aug 2006 08:11:07 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from atlantis.dp.ua (localhost [127.0.0.1]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k7T8Asn9037080; Tue, 29 Aug 2006 11:10:54 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Received: from localhost (dmitry@localhost) by atlantis.dp.ua (8.13.1/8.13.1/Submit) with ESMTP id k7T8Aria037075; Tue, 29 Aug 2006 11:10:53 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Tue, 29 Aug 2006 11:10:53 +0300 (EEST) From: Dmitry Pryanishnikov To: freebsd-net@freebsd.org In-Reply-To: <20060829010553.GC93062@dwpc.dwlabs.ca> Message-ID: <20060829101749.R48261@atlantis.atlantis.dp.ua> References: <44EF6E18.6090905@elischer.org> <44F3429F.6050204@FreeBSD.org> <44F344FA.1000408@elischer.org> <20060828221218.GB93062@dwpc.dwlabs.ca> <44F370F2.7080406@elischer.org> <20060829010553.GC93062@dwpc.dwlabs.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Julian Elischer Subject: Re: possible patch for implementing split DNS X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 08:11:08 -0000 Hello! On Mon, 28 Aug 2006, Duane Whitty wrote: > Well, I think maybe your solution is the simplest and it sounds like an > interesting feature. I do wonder though if it would be possible to bind > a process to a network interface alias on the fly? So if you had ten possible Alas I don't see the way to bind an abstract process to the specific IP address on hosts with several IPs. For applications which use connect(2), we have net/libconnect port, but simple experiments with it and a couple of trivial resolver(3) consumers (like ping or telnet) show that resolver(3) doesn't use connect(2) by default, so net/libconnect can't change source IP address for DNS queries on the fly. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE