From owner-freebsd-isdn Tue Dec 22 06:42:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25333 for freebsd-isdn-outgoing; Tue, 22 Dec 1998 06:42:35 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25328 for ; Tue, 22 Dec 1998 06:42:32 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA11909; Tue, 22 Dec 1998 15:42:27 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA24517; Tue, 22 Dec 1998 15:42:26 +0100 (MET) Message-ID: <19981222154225.A24362@follo.net> Date: Tue, 22 Dec 1998 15:42:25 +0100 From: Eivind Eklund To: Martin Husemann , Gerhard Sittig Cc: FreeBSD-ISDN Mailingliste Subject: Re: updates to i4b References: <000101be2b91$363b70b0$53cb08d4@hwart.teuto.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <000101be2b91$363b70b0$53cb08d4@hwart.teuto.de>; from Martin Husemann on Sat, Dec 19, 1998 at 09:50:29PM +0100 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Dec 19, 1998 at 09:50:29PM +0100, Martin Husemann wrote: > This is not a "solution" but a hack (IMHO), and it's the thing we talked > about right at the start of this discussion. There are subtle details, so a > bit more discussion before adding this as an optional feature is OK, I > think. Never copy linux implementation and call it design before undstanding > the problem and all possible solutions and their implications! (No pun > intended: this says nothing about either linux implementation or design, > just about the "copy an existing implementation" substituting design work.) > > In the concrete example: the setups where I've met the problem always > included some NAT functionality on the ISDN router. Since the local > (caching) nameserver as well as the http-client are (at least logicaly) on > the other side of the translation, a fine tuned integration between the NAT > framework and the IPCP implementation could resolve this problems in a much > cleaner way. At least at first lookt this seems possible. I have code that does this. It'll hopefully be available from the stock distribution of mpd at the time a new version of i4b is available. I just have to clean up a couple of patches. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message