netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Jackson <jerj@coplanar.net>
To: netdev@vger.kernel.org
Subject: adding tcpdump/OAM support to usb ATM devices
Date: Sun, 27 Apr 2008 17:31:53 -0400	[thread overview]
Message-ID: <1209331913.8768.214.camel@ragnarok> (raw)

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.

Diagnosing problems is often complicated by the fact that large backhaul
networks appear as only 1 IP hop in traceroute.

The goal is to support sending and receiving F5 OAM cells on a Linux
host, from in-use PVCs bound to a br2684 bridge, your typical USB ADSL
modem.  The ATM OAM segment "ping" can be useful in troubleshooting, yet
few modems support it, and *none* return timing and other detailed
information.

The modems running embedded Linux internally (openwrt AR7 for example)
could also use this.

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!

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?

-- 
Jeremy Jackson
Coplanar Networks
(519)489-4903
http://www.coplanar.net
jerj@coplanar.net


             reply	other threads:[~2008-04-27 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 21:31 Jeremy Jackson [this message]
2008-04-27 21:35 ` adding tcpdump/OAM support to usb ATM devices David Miller
2008-04-27 22:35   ` Jeremy Jackson
2008-04-28 14:18 ` Chas Williams (CONTRACTOR)
2008-04-28 15:54   ` Jeremy Jackson
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=1209331913.8768.214.camel@ragnarok \
    --to=jerj@coplanar.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;
as well as URLs for NNTP newsgroup(s).