netdev - Re: adding tcpdump/OAM support to usb ATM devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200804281418.m3SEImnN032542@cmf.nrl.navy.mil>
Date:	Mon, 28 Apr 2008 10:18:48 -0400
From:	"Chas Williams (CONTRACTOR)" <chas@....nrl.navy.mil>
To:	Jeremy Jackson <jerj@...lanar.net>
cc:	netdev@...r.kernel.org
Subject: Re: adding tcpdump/OAM support to usb ATM devices

In message <1209331913.8768.214.camel@...narok>,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.

>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.

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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html