From owner-freebsd-usb@FreeBSD.ORG Fri Dec 3 19:45:03 2004 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 647DD16A4CE; Fri, 3 Dec 2004 19:45:03 +0000 (GMT) Received: from smtp2.jazztel.es (smtp2.jazztel.es [62.14.3.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A84843D39; Fri, 3 Dec 2004 19:45:02 +0000 (GMT) (envelope-from josemi@freebsd.jazztel.es) Received: from antivirus by smtp2.jazztel.es with antivirus id 1CaJML-0006I1-00 Fri, 03 Dec 2004 20:44:53 +0100 Received: from [212.106.254.37] (helo=rguez.homeunix.net) by smtp2.jazztel.es with esmtp id 1CaJMK-0006HZ-00 Fri, 03 Dec 2004 20:44:52 +0100 Received: from redesjm.local (orion.redesjm.local [192.168.254.16]) by rguez.homeunix.net (8.13.1/8.13.1) with ESMTP id iB3Jir3L000494; Fri, 3 Dec 2004 20:44:53 +0100 (CET) (envelope-from freebsd@redesjm.local) Received: from localhost (localhost [[UNIX: localhost]]) by redesjm.local (8.13.1/8.13.1/Submit) id iB3Jiu8a001493; Fri, 3 Dec 2004 20:44:56 +0100 (CET) (envelope-from freebsd@redesjm.local) From: Jose M Rodriguez To: Roman Kurakin Date: Fri, 3 Dec 2004 20:44:55 +0100 User-Agent: KMail/1.7.1 References: <200412021702.53996.freebsd@redesjm.local> <41B09971.1080209@cronyx.ru> In-Reply-To: <41B09971.1080209@cronyx.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200412032044.56370.freebsd@redesjm.local> X-AntiVirus: checked by AntiVir Milter (version: 1.1; AVE: 6.28.0.19; VDF: 6.28.0.103; host: antares.redesjm.local) X-Virus-Scanned: by antivirus cc: hackers@freebsd.org cc: freebsd-usb@freebsd.org cc: net@freebsd.org Subject: Re: about a usb adsl modem driver X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 19:45:03 -0000 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