From owner-freebsd-net Wed Aug 4 3:23:59 1999 Delivered-To: freebsd-net@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id D491E14FF1 for ; Wed, 4 Aug 1999 03:23:56 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id LAA70299; Wed, 4 Aug 1999 11:23:32 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA02519; Wed, 4 Aug 1999 11:24:47 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199908041024.LAA02519@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: kit Cc: Brian Somers , jonathan michaels , Brian Somers , Robert Watson , freebsd-net@FreeBSD.ORG Subject: Re: "Invitation to participate in PPPoE Trial" (fwd) In-reply-to: Your message of "Tue, 03 Aug 1999 22:45:26 EDT." <37A89856.9C819AA8@xtra.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Aug 1999 11:24:47 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org a.bob@xtra.co.nz said: > On a sort of related topic what would be required to run RFC 2365 PPP > over AAL5. Would it be easier/ harder than over UDP / Ethernet? How > would natm and user ppp fit? And where would one look to find out > what is required? Anything that requires device-specific link negotiation isn't easy to implement at the moment - that's the idea behind changing the ``set dial'' stuff so that it's ``chat'' capabilities are abstracted at the device level. This is what's really missing at the moment. It'll have to be written for PPPoE, and the isdn patches I have (not yet committed) would benefit from such changes. I don't think natd fits into any of this - it just mangles packets via divert sockets - it doesn't control the traffic in any other way. The only place to find out more about this is in ppp/datalink.c - specifically the DATALINK_DIAL state code that currently passes off responsibility to the chat state machine. It needs to use a more generic state machine from which the chat state machine will be derived at the ``struct physical'' level for ttys, a i4bchat state machine sould do the RBCH_DIALOUT stuff for ISDN devices, and an EthernetChat derivation could be written for PPPoE. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message