From: Jeremy Jackson <jerj@coplanar.net>
To: chas3@users.sourceforge.net
Cc: netdev@vger.kernel.org
Subject: Re: adding tcpdump/OAM support to usb ATM devices
Date: Mon, 28 Apr 2008 11:54:42 -0400 [thread overview]
Message-ID: <1209398082.8768.257.camel@ragnarok> (raw)
In-Reply-To: <200804281418.m3SEImnN032542@cmf.nrl.navy.mil>
On Mon, 2008-04-28 at 10:18 -0400, Chas Williams (CONTRACTOR) wrote:
> In message <1209331913.8768.214.camel@ragnarok>,Jeremy Jackson writes:
> >who cares about ATM? Well anyone using ADSL/2/2+ high speed internet
> >access is stuck with it, and that's not a small number of people.
>
> i still care.
good to hear! I'd love to label ATM as legacy and forget it... but
we're stuck with ATM on ADSL (VDSL has packet mode with HDLC-like
framing) since no hardware vendor has implemented the packet mode for
ADSL2/2+ even though it's part of the spec.
> >The question: what is the recommended way to push the captured cells to
> >userspace? raw ATM socket, netlink, packet socket, i'm not up to speed
> >here people!
>
> the right way is netlink. i have some patches to add more complete
> oam support but they use the current ioctl interface which should be
> considered deprecated. so adding new functionality using this interface
> to the kernel, would likely be rejected.
Can you send me some patches? It would be good for discussion and
experimentation.
> eventually, all the atm clients (zeppelin, atmsigd, et al) should be
> converted to using netlink.
>
> >in 2.6.22 drivers/usb/atm/usbatm.c::usbatm_extract_one_cell()
> >
> >cells received for open PVC/SVC sockets are processed, however OAM cells
> >are dropped, and cells to unbound VPI/VCI are dropped.
> >
> >This seems the likely place to route cells somewhere useful, but what
> >mechanism to use?
>
> i guess now might be the time to try to define a netlink interface
> between the userspace and the kernel.
I think there are 2 cases, packet socket support for ATM, for
libpcap/tcpdump etc, and control functions (presently ioctl) switched to
use netlink. Generating OAM cells might belong to a control function on
netlink, but I wonder about PF_RAWATM, the present setup with pcv/svc
sockets is a bit wierd, you set the qos type to AAL0 to mean raw.
Perhaps there should be a PF_RAWATM instead.
--
Jeremy Jackson
Coplanar Networks
(519)489-4903
http://www.coplanar.net
jerj@coplanar.net
next prev parent reply other threads:[~2008-04-28 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 21:31 adding tcpdump/OAM support to usb ATM devices Jeremy Jackson
2008-04-27 21:35 ` David Miller
2008-04-27 22:35 ` Jeremy Jackson
2008-04-28 14:18 ` Chas Williams (CONTRACTOR)
2008-04-28 15:54 ` Jeremy Jackson [this message]
2008-04-29 12:04 ` Chas Williams (CONTRACTOR)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1209398082.8768.257.camel@ragnarok \
--to=jerj@coplanar.net \
--cc=chas3@users.sourceforge.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox