From owner-freebsd-hackers Wed Jan 15 16:32:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA09674 for hackers-outgoing; Wed, 15 Jan 1997 16:32:46 -0800 (PST) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA09663 for ; Wed, 15 Jan 1997 16:32:41 -0800 (PST) Received: from awfulhak.demon.co.uk (localhost.coverform.lan [127.0.0.1]) by awfulhak.demon.co.uk (8.8.4/8.7.3) with ESMTP id AAA15181; Thu, 16 Jan 1997 00:31:28 GMT Message-Id: <199701160031.AAA15181@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: "Daniel O'Callaghan" cc: Archie Cobbs , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD as an ISDN Router In-reply-to: Your message of "Wed, 15 Jan 1997 17:09:55 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Jan 1997 00:31:28 +0000 From: Brian Somers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [.....] > And some might want to run alias stuff over ethernet or other, and not > want ppp at all. I agree completely - but the last time this was discussed (AFAIK) people didn't really want to dirty the tcp stack. The alias stuff converts *every* port number for a given interface, making what appears to be going on and what's actually going on into two completely different things. I think the best way to do this sort of thing would be to take advantage of something like a firewall'ing hook, and writing an alias lkm that massaged the packets at that level. That way, unless you "modload lkm_alias.o" and then condition a few interfaces, the tcp stack will be pure. I don't know off the top of my head if this is possible at the moment - does the firewalling code get a chance to change the packet ? Or is it just capable of blocking it. -- Brian , Don't _EVER_ lose your sense of humour....