From owner-freebsd-net@FreeBSD.ORG Mon Nov 3 02:42:19 2003 Return-Path: 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 8C13916A4CE for ; Mon, 3 Nov 2003 02:42:19 -0800 (PST) Received: from famine.e-raist.com (69-30-69-105.dq1mn.easystreet.com [69.30.69.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DA0D43FE0 for ; Mon, 3 Nov 2003 02:42:18 -0800 (PST) (envelope-from aburke@nullplusone.com) Received: from thebe (12-224-164-145.client.attbi.com [12.224.164.145]) (authenticated bits=0) by famine.e-raist.com (8.12.8/8.12.8) with ESMTP id hA3AgEfL029671; Mon, 3 Nov 2003 02:42:16 -0800 (PST) From: "Aaron Burke" To: "Joost Bekkers" , Date: Mon, 3 Nov 2003 02:41:50 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20031102142405.GA60111@bps.jodocus.org> Importance: Normal Subject: RE: how to run mpd for pptp on Cable and DSL links at the same time? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 10:42:19 -0000 > -----Original Message----- > From: Joost Bekkers [mailto:joost@jodocus.org] > Sent: Sunday, November 02, 2003 6:24 AM > To: Aaron Burke > Cc: freebsd-net@freebsd.org > Subject: Re: how to run mpd for pptp on Cable and DSL links at the same > time? > > > On Sun, Nov 02, 2003 at 04:21:54AM -0800, Aaron Burke wrote: > > > > Is there a way to get mpd to listen on both interfaces at the same time? > > > > This box is running FreeBSD 4.7-RELEASE, running mpd-3.9 . > > Cable Modem: dc0, 12.224.x.y/24 > > DSL: ed0, 199.26.a.b/29 > > LAN: xl0, 192.168.0.250/24 > > > > Try telling it to listen on the any address (0.0.0.0) instead of > the ip of a > specific interface. That seems to have worked. Allthough I have only tested this from one machine. However, it appears to work from any address from this client. > -- > greetz Joost > joost@jodocus.org Thanks Joost Aaron Burke aburke@nullplusone.com