Ethereal-dev: RE: [Ethereal-dev] trying to interface a generic 802.11abgwith ethereal( windows

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Ankur Aggarwal" <ankur@xxxxxxxxxxxxxxxxx>
Date: Mon, 6 Jun 2005 13:01:59 +0530
Thanks Harris and other ethereal team members

With your active and prompt support and guidance, I have been able to
get the data path up. (11abg card with prism header) and also been able
to ship all the packets (control + mgmt + data) through NDIS in windows
XP.

 1) Is there any way by which I can get the values displayed in column
be written in a csv file (like the airopeek)? It would be a nice feature
to record and tabulate the essence of packet information.

2) Is there any seed code on which I could implement the FSM of the
protocol checker, or guidelines for doing so?

The user requirement was like:
1)       Just marks if the packet response (eg. ack) was observed or
not.

2)       Check for timing

a.       Frame response timeout.

b.       Txops violation.

c.       Latency (maybe)

3)       Check for unexpected behavior in bit positions like sequence
number, Time stamps, capability.



Regards
Ankur

-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Thursday, June 02, 2005 10:20 PM
To: Ethereal development
Subject: Re: [Ethereal-dev] trying to interface a generic 802.11abgwith
ethereal( windows) using prism header

Ankur Aggarwal wrote:

> If anyone has any clue why the NDIS/ winpcap is dropping the packets, 
> please help.

You should probably ask the WinPcap developers about this, as it's 
probably some low-level issue with NDIS or WinPcap (perhaps the NDIS 
stack can't handle the Prism header, as NDIS and the networking stack 
might be expecting Ethernet headers).

Note also that there's no way in NDIS to specify that a networking 
device has Prism headers, so there's no way for WinPcap to know that 
merely by using information from NDIS - assuming you can even arrange 
that Prism headers (or AVS headers, or radiotap headers) be present in 
the packet (which might not be the case, as per my parenthetical note in

the previous paragraph), you'd have to modify WinPcap to somehow know 
that the driver is supplying them, so it can return the right DLT_
value.

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev