Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Dec 1998 15:42:25 +0100
From:      Eivind Eklund <>
To:        Martin Husemann <>, Gerhard Sittig <G.Sittig@abo.FreiePresse.DE>
Cc:        FreeBSD-ISDN Mailingliste <freebsd-isdn@FreeBSD.ORG>
Subject:   Re: updates to i4b
Message-ID:  <>
In-Reply-To: <000101be2b91$363b70b0$>; from Martin Husemann on Sat, Dec 19, 1998 at 09:50:29PM +0100
References:  <Pine.LNX.4.02.9812191559280.28352-100000@speedy.gsinet> <000101be2b91$363b70b0$>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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.


To Unsubscribe: send mail to
with "unsubscribe freebsd-isdn" in the body of the message

Want to link to this message? Use this URL: <>