Re: about a usb adsl modem driver

From: Jose M Rodriguez (josemi_at_freebsd.jazztel.es)
Date: 12/04/04

  • Next message: Chuck Swiger: "Re: ipfw and bridging [was: pf and bridging]"
    To: Bruce M Simpson <bms@spc.org>
    Date: Sat, 4 Dec 2004 10:09:37 +0100
    
    

    El Sábado, 4 de Diciembre de 2004 01:56, Bruce M Simpson escribió:
    > On Fri, Dec 03, 2004 at 09:25:56PM +0100, Jose M Rodriguez wrote:
    > > But noted strong differences between atm boards and adsl modems.
    > >
    > > - atm boards are hardware assisted. usb adsl modems are bare
    > > assisted. - atm boards support better signaling, multiple channels,
    > > ... usb adsl modems just one PVC with uni signaling.
    >
    > Not really. See below.
    >
    > > So I realize that try to get a NATM/NETGRAPH hardware driver may be
    > > too work for little gain.
    >
    > Actually writing a NATM driver is far easier than writing a HARP
    > driver. And Harti's newer drivers for ATM cards are, in fact, NATM
    > drivers. You only need to implement Netgraph hooks. You don't need to
    > worry about implementing Netgraph protocol nodes, generally.
    >

    I think so. The actual ueagle driver do that, only needs NetGraph
    aditions.

    My objections to implement NATM are related to the final operation.
    What you get througt NATM is of low interest for usb adsl users.

    You don't need signaling managers, multipe channels, ...

    I think that a direct, one PVC, usb adsl version of ng_atm will do the
    work. I think implement the netgraph support directly in the usb
    driver.

    About the rest of the ng_ nodes involved, I think the only problem is
    ng_atmllc.

    To be a generic aal5 frame diverter, it lacks some funtionality like
    VCMux support or ppp VcMux/LLC autoswitch.

    > You might want to contact Benno Rice, he was working on a software
    > AAL5 kernel module to augment netnatm, which would help if you're
    > targeting the lower end ADSL hardware.
    >

    My initial plans was implement this as part of the driver, but I no
    have any objections to this. But I'll prefer take this in the future,
    when we have a working driver (Well, another. ueagle really works on
    RELENG_5).

    Any pointer on this is welcome.

    --
      josemi
    > Regards,
    > BMS
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
    

  • Next message: Chuck Swiger: "Re: ipfw and bridging [was: pf and bridging]"

    Relevant Pages

    • Re: ADSL PPPoA using a bridged ADSL router?
      ... Well, since the ADSL card in question doesn't exist, of course not:) ... > kernel driver & then reload it, ...
      (uk.comp.os.linux)
    • Re: Mandrake 9.1 modem ADSL NIC not recognized
      ... ]trouble finding out what the card is, ... ]Those aren't modems, btw. ADSL is digital. ... ]> 10/100 card and not the modem Adsl. ... What driver does it need/ What happens ...
      (comp.os.linux.misc)
    • Re: about a usb adsl modem driver
      ... > Actually writing a NATM driver is far easier than writing a HARP ... And Harti's newer drivers for ATM cards are, in fact, NATM ... You only need to implement Netgraph hooks. ... What you get througt NATM is of low interest for usb adsl users. ...
      (freebsd-hackers)
    • Re: ADSL PPPoA using a bridged ADSL router?
      ... >> Errr, I'm using a `Linux box with ADSL' route, it's just that the Linux ... > Yep, I've spotted that, and if the dirt-cheap ADSL card doesn't work ... kernel upgrades have even more consequences than they already do. ... >> binary-only driver doesn't work with that kernel? ...
      (uk.comp.os.linux)
    • Re: netgraph ISDN driver
      ... > does a PCI device driver need to have either a network device or a ... > character device or can i simply allow it to be a netgraph only ... think i got the answer from the "sr" driver. ...
      (freebsd-net)