Date: Fri, 3 Dec 2004 20:44:55 +0100 From: Jose M Rodriguez <josemi@freebsd.jazztel.es> To: Roman Kurakin <rik@cronyx.ru> Cc: net@freebsd.org Subject: Re: about a usb adsl modem driver Message-ID: <200412032044.56370.freebsd@redesjm.local> In-Reply-To: <41B09971.1080209@cronyx.ru> References: <200412021702.53996.freebsd@redesjm.local> <41B09971.1080209@cronyx.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
El Viernes, 3 de Diciembre de 2004 17:50, Roman Kurakin escribi=F3: > Jose M Rodriguez wrote: > >Hi, > > > >I've got a eagle usb adsl modem and get ready to work on FreeBSD > > support for it. > > [...]=20 > > > >My first idea was a sppp based one, that can be ported to all xBSD.=20 > > But now I think that a netgraph thing must be a better first > > contact. > > Note, with Netgraph you may use sppp via ng_sppp(4). Also it is not > to hard to > implement a dual driver. But I sugest to not do that way, especialy > if you want to > support multiple branches. I know how hard is that ;-). > (http://www.cronyx.ru/software/sigma.html) > If your implementation would work with sppp (via ng_sppp(4)) or you > would need > smth additional from sppp(4) let me know. > > rik > Well, this may depend of noted interest. I can work on RELENG_5_3 or RELENG_4, but I need some commiter that can=20 take this into HEAD. I found Netgraph the easy path. A, let's say, ng_uadsl limited only to=20 move aal5 between the modem and netgraph may be enough to use routed=20 protocols, bridged mode, pppoe, pppoa, pptp, user-ppp, sppp, ... just=20 with some equivalents of frame relay nodes and atm_llc, adapted to=20 rfc2684. The hard part of this solution is that we need more userland work to=20 sync all this stuff. Also, I noted that most of home adsl connections are of just only three=20 categories: =2D IPv4 routed (generally LLC) =2D pppoe over ethernet bridge (Only LLC) =2D pppoa (generally VCMux, but also LLC) I think this can be taken by a sppp derived work. pppoa may be really direct (just PDU test/adjust), but the other need=20 more work. IPv4 routed needs some kinda of bypass control, to use only the basic if=20 interface after sppp. pppoe (only client) may be implemented in a single step with ethernet=20 bridge encapsulation as a dial extension. Also, an auto mode for pppoe/pppoa-LLC/pppoa-VCMux may be implemented=20 without too much problem (rotatory mode selection in sucesive dial=20 attemps). Support form OpenBSD must be easy, but NetBSD is another story. This=20 implementation is heavily affected by pppoe works and really differ=20 from FreeBSD/OpenBSD. Also, the usb part needs works. A eagle implementation based on ueagle must be easy. but this driver is,=20 right now, too much 'eagle oriented'. I'll prefer a 'ugen derived' model (used by net/pppoa). Or, at last, a=20 more generic driver. This needs really 'too much manpower' that I can expend now. So, if noboby else have any more to say, I'll work it only two basic=20 directions, time permitting: =2D a sppp based, pppoa only driver for eagle, derived from ueagle, for=20 RELENG_5. =2D a ng_ueagle node for RELENG_5 derived from ueagle. thanks for your time, =2D- josemi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412032044.56370.freebsd>