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: <20080427.143504.197027637.davem@davemloft.net>
Date:	Sun, 27 Apr 2008 14:35:04 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jerj@...lanar.net
Cc:	netdev@...r.kernel.org
Subject: Re: adding tcpdump/OAM support to usb ATM devices

From: Jeremy Jackson <jerj@...lanar.net>
Date: Sun, 27 Apr 2008 17:31:53 -0400

> 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()

It depends upon what you want to do with this.

Maybe it makes sense, if what you're trying to do is expose the
signalling layer of the packet to diagnostic tools, is have an
option in the driver such that the entire ATM header area will
be presented to the AF_PACKET socket when tapping the network.

Could that work?

Adding special mechanisms to get at the packet data is going to
make it more difficult to use this stuff, and kind of defeat
your purpose.  So anything that's automatically working with
tcpdump and will "just work" is preferred.
--
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