> With an 802.11 device, does turning DLPI_NATIVE on put the device into
> monitor mode, or does it just cause it to supply 802.11 headers?
It just causes it to supply 802.11 headers. We may later add support to
monitor.
> Is there a way to query whether a device supports DLPI_NATIVE
>
Guy Harris wrote:
On Feb 1, 2008, at 12:47 PM, sagun shakya wrote:
Sebastien Roy wrote:
* 118-123: I would think that in 2008, most compilers can do a
better job at assigning register use than this (making every single
variable a "register" variable.) You don't have to fix this; th
On Feb 1, 2008, at 12:47 PM, sagun shakya wrote:
Sebastien Roy wrote:
* 118-123: I would think that in 2008, most compilers can do a
better job at assigning register use than this (making every single
variable a "register" variable.) You don't have to fix this; this
is more a question
On Feb 1, 2008, at 10:10 AM, Sebastien Roy wrote:
* 118-123: I would think that in 2008, most compilers can do a
better job at assigning register use than this (making every single
variable a "register" variable.) You don't have to fix this; this
is more a question for those more knowledg
Thanks Seb. I Will send out an updated webrev. My comments are below:
Sebastien Roy wrote:
http://cr.opensolaris.org/~sagun/libpcap/
aclocal.m4 and configure.in
* The macros and code in these files seem to be going out of their way
to support old versions of the public libdlpi library that d
>
> * 101: Perhaps this is a good time to ask about DLPI_NATIVE. For those
> not familiar with the concept, the idea is that some DLPI providers
> masquerade as a well-known media type by default, but can morph into
> their "native" types on-demand. Recent Solaris WiFi DLPI devices behav
sagun shakya wrote:
I've addressed all the comments from below and updated the webrev.
http://cr.opensolaris.org/~sagun/libpcap/
While testing the changes I found out that my changes didn't work on a Solaris
system that had libdlpi.h version
that existed before the public libdlpi.h was integra
