From owner-freebsd-net Mon Oct 2 23: 2:35 2000 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 8487D37B66C for ; Mon, 2 Oct 2000 23:02:33 -0700 (PDT) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA40168; Mon, 2 Oct 2000 23:02:24 -0700 (PDT) Date: Mon, 2 Oct 2000 23:02:24 -0700 (PDT) From: Julian Elischer To: Matthew Emmerton Cc: Patrick Bihan-Faou , freebsd-net@FreeBSD.ORG Subject: Re: natd and userland ppp In-Reply-To: <000a01c02cf7$c0cb0a10$1200a8c0@gsicomp.on.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 3 Oct 2000, Matthew Emmerton wrote: > The only other option is to use netgraph. I'm thinking that a ng_nat module > would eliminate some situations -- however the majority would be would be > those requiring natd as a daemon (such as plain Ethernet or PPPoE) and not > the nat-enabled user-ppp. mpd uses all netgraph kernellevel processing for it's PPP (though is can do it itself if it needed to) It wouldn't take much to add a NAT module at the head of the chain.. for configuration We'd use the Netgraph ascii parser. I'd like to make an IPFW (or IPF) node as well but the difficult bit is working out exactly where to slot it in.. Basically it requires the ability to slot oneself just below the top interface of ANY network interface, (including lo, tun, ng, etc.) it might be a job more for ALTQ.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message