On May 9, 2007, at 12:46 AM, Graham Bloice wrote:
> ยท Wireless (802.11) capturing and monitor mode on Vista - With
> supported
> hardware, (Native WIFI), you can now trace wireless management
> packets.
> You can scan all channels or a subset of the ones your wireless NIC
> supports. You can
On Wed, May 09, 2007 at 02:53:25PM -0400, Kevin A. Noll wrote:
> I'm trying to decode a packet that has TLVs at the end of it. One of
> the possible TLVs is a "NULL" TLV, which is simply one or more bytes
> with the zero value. However, if it's any other kind of TLV, it is
> likely to start wit
Kevin A. Noll wrote:
> The dissector in question is packet-wlccp.c.
>
> Regarding heuristic or not, I still don't fully understand what the
> difference is. I don't think this one is heuristic, and this should be the
> top layer protocol, so I wouldn't need to hand it off to another recipient.
Guy,
You're asking me a question I don't think I know how to answer (darned
amateurs :-).
The dissector in question is packet-wlccp.c.
Regarding heuristic or not, I still don't fully understand what the
difference is. I don't think this one is heuristic, and this should be the
top layer proto
Kevin A. Noll wrote:
>
> I know this should be easy to do, but I can't find it written down in
> anything I can readily find...
>
> I'm trying to decode a packet that has TLVs at the end of it. One of the
> possible TLVs is a "NULL" TLV, which is simply one or more bytes with the
> zero value. Ho
I know this should be easy to do, but I can't find it written down in
anything I can readily find...
I'm trying to decode a packet that has TLVs at the end of it. One of the
possible TLVs is a "NULL" TLV, which is simply one or more bytes with the
zero value. However, if it's any other kind of T
Hi,
I've incorporated the Win32 resources starting from the 0.99.5 release,
so that's why your code probably doesn't have these resources.
One thing you can do is use the strings utility, which tries to display
everything that looks like a string in an executable file.
sysinternals' process explor
Hi Joerg,
Slightly off topic, but in this statement/request...
> Please do not send patches compressed as zip files: It makes viewing
> them inline impossible. I at least won't spend the time at looking at
> them (except that they personally interest me).
>
Did you mean "zip files" literally, or
Folks,
The win32 buildslave is now compiling again, but fails the tests.
My build seems to work OK. Is it something in the test environment?
--
Regards,
Graham Bloice
Software Developer
Trihedral UK Limited
Tel: +44 (0)1224 258910
___
Wireshark-dev m
Here it is.
br,
Lars
Stephen Fisher wrote:
Could you please send these as unified diffs (diff -u or using the svn
diff command) so we can tell the context the changes are made in without
having to cross-reference the source files.
On Tue, May 08, 2007 at 10:28:53AM +0200, Lars Ruoff wrote:
[EMAIL PROTECTED] wrote:
> Thanks, Graham,
>
> that's what I expected to happen, too. But if i hover over the dll (it is
> Win32, forgot to mention, sorry )
> it only says "application extension". The property tab only lists empty data
> like "title, comment, author,...".
>
> I'm using the VS
On Fri, Apr 20, 2007 at 09:47:46AM -0700, Mike Duigou wrote:
> Enclosed is a patch adapted from Apache APR via JXTA to create a
> config.nice file for Wireshark. config.nice allows you to re-run
> ./configure with the same options you used as the last time you ran
> ./configure
It looks to me t
Thanks, Graham,
that's what I expected to happen, too. But if i hover over the dll (it is
Win32, forgot to mention, sorry )
it only says "application extension". The property tab only lists empty data
like "title, comment, author,...".
I'm using the VS 6 compiler and the Wireshark 0.99.4 sourc
[EMAIL PROTECTED] wrote:
> Hi,
>
> I wrote some plugin dissectors for different proprietary protocols. As the
> protocols changed, I changed the plugin versions in moduleInfo.h, too.
> Now I have a bunch of dlls named myPlugin.dll, but I can't determine their
> version string.
> My plugins' vers
Hi,
I wrote some plugin dissectors for different proprietary protocols. As the
protocols changed, I changed the plugin versions in moduleInfo.h, too.
Now I have a bunch of dlls named myPlugin.dll, but I can't determine their
version string.
My plugins' versions are listed in Wireshark->About->Pl
Hi Ulf,
sounds good.
Ragarding VS2005. I know that problem from other projects.
* time_t is 64 bit now: Use the define _USE_32BIT_TIME_T to make it
backward compatible
* wchar_t is a built-in type now. This may also cause problems,
because it was a "unsigned short" before. Bu
Probably others have received this from MS, interesting stuff about
their display filters including filter building by clicking on a data
element, and the wireless stuff on Vista.
Dear Network Monitor 3 user
Network Monitor 3.1 Beta Has Released!
The NM3.1 Beta is available on http://connect.Micr
Gerhard Gappmeier wrote:
> Nevertheless I attached an update where I fixed the missing { 0, NULL
> }entries
> in the value_string arrays.
Good, that had to be fixed anyway.
> I also attached the result of tshark so you can compare it with yours.
> Is the access violation catched in any way and pro
18 matches
Mail list logo
