Date: Wed, 04 Aug 1999 11:24:47 +0100 From: Brian Somers <brian@FreeBSD.org.uk> To: kit <a.bob@xtra.co.nz> Cc: Brian Somers <brian@FreeBSD.org.uk>, jonathan michaels <jon@caamora.com.au>, Brian Somers <brian@Awfulhak.org>, Robert Watson <robert+freebsd@cyrus.watson.org>, freebsd-net@FreeBSD.ORG Subject: Re: "Invitation to participate in PPPoE Trial" (fwd) Message-ID: <199908041024.LAA02519@keep.lan.Awfulhak.org> In-Reply-To: Your message of "Tue, 03 Aug 1999 22:45:26 EDT." <37A89856.9C819AA8@xtra.co.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <brian@Awfulhak.org> <brian@FreeBSD.org>
<http://www.Awfulhak.org>; <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour ! <brian@FreeBSD.org.uk>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908041024.LAA02519>