Ulf Lamping wrote:
>> I have MSVC 8.0 build 50727. I detest trying to use the M$ compiler
>> suite, but sometimes the alternatives are worse.
>>
>
> Do you use the Express Edition or the Studio?
Ulf,
I'm using MSVC 2005 Express edition.
I got the error message below after running "nmake -f M
On Wed, Jan 10, 2007 at 04:21:39AM +0100, Ulf Lamping wrote:
> I've checked in a related patch from Laurent Rabret, you may try
> another build.
>
> As I don't know the real cause of the problem, I don't know if the
> problem is fixed (all my machines are keep building just fine ...).
That fix
Andrew Hood wrote:
>>> Those are fixed by adding gdi32.lib advapi32.lib comdlg32.lib to
>>> wireshark_LIBS.
>>>
I've checked in the "/MD" patch from Laurent, could you give it another try?
Regards, ULFL
___
Wireshark-dev mailing list
Wireshark-dev
Laurent Rabret wrote:
> Hi,
> Sorry for not providing this simple patch before. It is OK with VS
> 2005 express edition, can you check it is OK with previous releases
> because I do not have them anymore?
Tested on some of the machines and all were building fine. Checked in -
it might help other
Stephen Fisher wrote:
> Ulf,
>
> Have you built Wireshark with Microsoft Visual C++ 2005 Express Edition
> (with Microsoft Platform SDK for Windows 2003 R2 in the WinXP build
> environment) yet? I've never tried compiling Wireshark on Windows
> before so I don't know what these errors even mean
Andrew Hood wrote:
>> Anders also observed it didn't build. If you did "nmake -k ..." it might
>> build later on, and then rerunning nmake might work.
>>
That was a bug in the dependencies, I've checked in a fix. It should
compile zlib1.dll now as required.
Regards, ULFL
Laurent Rabret wrote:
> Hi,
> Sorry for not providing this simple patch before. It is OK with VS
> 2005 express edition, can you check it is OK with previous releases
> because I do not have them anymore?
I'll try but that will last a while (on 7 different configurations) ...
>
> Regarding rela
Andrew Hood wrote:
>>> I enable HHC_DIR and disable AIRPCAP_DIR in config.nmake
>>>
>> You may better keep HHC_DIR disabled for now (it's optional) - let's fix one
>> thing at a time ;-)
>>
> It's trivial to fix by changing HHC_LIBS as quoted lower down.
>
I guess so, but I would li
[EMAIL PROTECTED], another one there!
What about adding yet another one so we add to the collection :-)
I found that other one in crypt/ I took it.
I'll try that!
On 1/9/07, Anders Broman <[EMAIL PROTECTED]> wrote:
> Hi,
> What's missing from epan/sha1.c?
> BR
> Anders
>
> -Ursprungligt me
Stephen Fisher wrote:
> Ulf,
>
> Have you built Wireshark with Microsoft Visual C++ 2005 Express Edition
> (with Microsoft Platform SDK for Windows 2003 R2 in the WinXP build
> environment) yet?
Yes, and it's working fine (however, I had to tweak some setting files).
> I've never tried compilin
While no one complains or notice another problem ... no ;)
Stephen Fisher wrote:
> Thanks for following up on this! So no changes are needed in our
> documentation for this issue?
>
> On Wed, Jan 10, 2007 at 12:13:50AM +0100, Sebastien Tandel wrote:
>
>
>> I just received the confirmation f
Thanks for following up on this! So no changes are needed in our
documentation for this issue?
On Wed, Jan 10, 2007 at 12:13:50AM +0100, Sebastien Tandel wrote:
>
> I just received the confirmation from the debian package maintainer
> that xorg packages had been renamed/reworked and now the d
I just received the confirmation from the debian package maintainer that
xorg packages had been renamed/reworked and now the dependencies for
gtk2-dev should be correct ...
Regards,
Sebastien Tandel
Stephen Fisher wrote:
> On Mon, Dec 18, 2006 at 12:44:01AM +0100, Sebastien Tandel wrote:
>
>
http://fxr.watson.org/fxr/source//crypto/sha1.c
Ciao,
Davide
DS>-Messaggio originale-
DS>Da: [EMAIL PROTECTED] [mailto:wireshark-dev-
DS>[EMAIL PROTECTED] Per conto di LEGO
DS>Inviato: martedì 9 gennaio 2007 23.52
DS>A: Developer support list for Wireshark
DS>Oggetto: [Wireshark-dev] SH
Ulf,
Have you built Wireshark with Microsoft Visual C++ 2005 Express Edition
(with Microsoft Platform SDK for Windows 2003 R2 in the WinXP build
environment) yet? I've never tried compiling Wireshark on Windows
before so I don't know what these errors even mean:
ascend-scanner.obj : error LN
Hi,
What's missing from epan/sha1.c?
BR
Anders
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För LEGO
Skickat: den 9 januari 2007 23:52
Till: Developer support list for Wireshark
Ämne: [Wireshark-dev] SHA1 in airpdcap_sha1.c fails on big endian boxen
As per t
As per the subject, the sha1 implementation in airpdcap_sha1.c does
not work on my PPC Mac.
does anyone know where (besides gcrypt) can I fetch a version that
works OK on both LE and BE machines?
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
_
On Mon, Jan 08, 2007 at 09:42:38PM -, Mike Davies wrote:
> There was a change in Corrigendum 1 (03/2004) to H.248.1 which allows
> an empty {} to be omitted from the Signal Descriptor. Currently (SVN
> 20346) this causes Wireshark to report [Packet size limited during
> capture] as shown i
I don't think you're convincing anyone that you are actually aware of
the header formats or you'd probably be able to figure this out, which
is why Guy suggested you do a little more reading.
But I'll try to help you along a little further:
The Ethernet header is a fixed 14 bytes as follows
Hi,
I fond some copy paste errors could you try revision 20358 and see if it
works better?
BR
Anders
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Anders Broman
Skickat: den 9 januari 2007 21:51
Till: 'Developer support list for Wireshark'
Ämne: Re:
[Wires
Hi,
Sorry for not providing this simple patch before. It is OK with VS 2005
express edition, can you check it is OK with previous releases because I do
not have them anymore?
Regarding relationships between VS express edition and PSDK, I successfully
compiled Wireshark once I had only done the 3
Ulf Lamping wrote:
>>I have MSVC 8.0 build 50727. I detest trying to use the M$ compiler
>>suite, but sometimes the alternatives are worse.
>
>
> Do you use the Express Edition or the Studio?
"Add Remove Programs" lists it as "Microsoft Visual Studio 2005
Professional Edition - ENU"
>>nmake Mak
LEGO wrote:
> any warnings afterwards?
Plenty, but I'm not sure they're related:
packet-snmp-template.c: In function 'format_oid':
packet-snmp-template.c:427: warning: pointer targets in passing argument 1 of
'strlen' differ in signedness
packet-snmp-template.c: In function 'new_format_oid':
pack
LEGO wrote:
>> ./configure --prefix=/xxx --with-ssl --with-portaudio
>> --with-net-snmp=/bc/net-snmp/bin/net-snmp-config --disable-usr-local
>> --enable-randpkt
>
> BTW you'll need gcrypt as well in order to decrypt. w/o gcry it will
> only verify authentication.
Sure, but that's enabled by defau
Hi,
The main reason is that we want to get rid of the old asn1.c and
Use the ber helpers instead.
Could you send samples privately or use tex2pcap to remove sensitive data?
The BER errors may be IMPLICIT or OPTIONAL missing in some Tags or tags
missing. Knowing which messages or tags is causing the
So far I have looked at two captures and they both report problems.
The files decoded fine with Wireshark 0.99.4.
The files are from customer sites so I can't submit them.
In some cases the error messages is simply "Malformed Packet: ANSI MAP"
in others it's a BER error.
What was the motivation
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Ulf Lamping
Skickat: den 9 januari 2007 15:33
Till: Developer support list for Wireshark
Ämne: Re: [Wireshark-dev] Microsoft Visual C Version 6support isa
bitoutdated ...
>
>
>With my latest changes (yesterd
> ./configure --prefix=/xxx --with-ssl --with-portaudio
> --with-net-snmp=/bc/net-snmp/bin/net-snmp-config --disable-usr-local
> --enable-randpkt
BTW you'll need gcrypt as well in order to decrypt. w/o gcry it will
only verify authentication.
--
This information is top security. When you have r
any warnings afterwards?
On 1/9/07, Thomas Anders <[EMAIL PROTECTED]> wrote:
> LEGO wrote:
> > might be a problem caused by a macro defined in one of the following
> > 71 #include
> > 72 #include
> > 73 #include
> > 76 #include
> > 77
LEGO wrote:
> might be a problem caused by a macro defined in one of the following
> 71 #include
> 72 #include
> 73 #include
> 76 #include
> 77 #include
>
> try move them after net-snmp's headers
Yep, that did the trick. Please comm
Thomas Anders wrote:
> In file included from /bc/net-snmp-5.4cvs/include/net-snmp/types.h:41,
> from /bc/net-snmp-5.4cvs/include/net-snmp/mib_api.h:8,
> from packet-snmp-template.c:76:
> /usr/include/netinet/in.h:355: error: expected identifier or '(' before
> '__e
might be a problem caused by a macro defined in one of the following
71 #include
72 #include
73 #include
76 #include
77 #include
try move them after net-snmp's headers
On 1/9/07, Thomas Anders <[EMAIL PROTECTED]> wrote:
>
try removing line 68
On 1/9/07, Thomas Anders <[EMAIL PROTECTED]> wrote:
> LEGO wrote:
> > However the most important test to be done is that it does no harm
> > while disabled. Weird runtime linking problems disallow me to build
> > with net-snmp so I cannot test it that way. I do not think that
>
> How about a prerelease on Monday, followed by a final release later in
> the week (assuming everything goes well)?
Sounds good to me!
So hopefully there's even some time to update the developer's guide accordingly
and to do a "call for testing" to try it on the various MSVC variants by othe
LEGO wrote:
> However the most important test to be done is that it does no harm
> while disabled. Weird runtime linking problems disallow me to build
> with net-snmp so I cannot test it that way. I do not think that
> net-snmp changes anything for this but verifying that everything that
> worked b
I have confirmed that the code included in libgcrypt_11 part of the
wireshark-setup-99.5-SVN-20350.exe has fixed the issue.
Thank you,
Robin Caron
- Original Message -
From: "Gerald Combs" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Tuesday, January 09, 2007 12
[EMAIL PROTECTED] wrote:
> Please correct me if I'm wrong , but as per my understanding , if I have
> a file "test" with the above values as content then the below command
> will generate an IP packet using these values and add some dummy
> ethernet header values to it.
> Command :text2pcap
oops, the file format for the users file is the next:
#engine-id username auth_pass priv_pass auth_model priv_model
# engine-id, username and passwds can be either "quoted" or hex
# double quoted strings are c-style strings and take escape chars
80001F888059DC486145A26322 "pippo" "plutoxxx" "PLUT
Here we go!
what's missing is:
* auth SHA1 -- RFC3414 section 7
* crypt AES -- RFC3826
* localized key cahching -- so that if a (mentally stable) system
administrator uses the same username/password for all nodes in a
network he has to add just one line to the users file, instead of one
for each
LEGO wrote:
> Gerald,
>
> How far in time are we from branching the next release?
>
> I'm almost there with SNMPv3 USM authentication and decryption, and I
> would like to know whether if to start checking it in now or to wait
> for the branching.
>
> It depends how long we have to wait for th
Ulf Lamping wrote:
>> It depends how long we have to wait for the branching to take place.
>>
>
> Hi!
>
> I'm currently deep in the process of bringing compilation on "various"
> Microsoft compiler variants to life, and I'm making good progress.
>
> There are some (minor) things left to be sol
Hi,
I'm sorry that I assumed you were more familiar with CDP.
I think because it's a Cisco protocol many manufacturers want to
interoperate with it. I know that at least HP and Broadcom (in their VoIP
chipsets) support it, as well as the Linux protocol stack.
Got to run!
Jaap
On Tue, 9 Jan 2007
>
> It depends how long we have to wait for the branching to take place.
>
Hi!
I'm currently deep in the process of bringing compilation on "various"
Microsoft compiler variants to life, and I'm making good progress.
There are some (minor) things left to be solved, which I think I'll need a
Hi,
Of course that's why you review the patches! And I haven't said
anything about this review. You, guys, are the "wireshark experts" and
you know better than me the potential side effect(s) of a particular patch.
But I'm sorry to try to glean some additional information because *I*
didn't get
[EMAIL PROTECTED] wrote:
> I cannot find the source code for gcry_rndw32_gather_random. In the
> patched version of libgcrypt used with Wireshark 0.99.4 there is an
> uninitialized variable being checked and since it is not consistently
> set will cause the slow random bit generation code to be us
Hi,
On Tue, 9 Jan 2007, Sebastien Tandel wrote:
> hu ... do you meant
>
> "Here is a patch for the management of the bad/good checksum for ISIS
> (like TCP/UDP/IP).
>
> support added for :
> - booleans hf_isis_lsp_checksum_good, hf_isis_lsp_checksum_bad in the tree,
> - information in the i
LEGO wrote:
> I'm almost there with SNMPv3 USM authentication and decryption
This is excellent news! Can you either check it in or post a diff so
interested people (like me) can help testing/improving?
Cheers,
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
_
hu ... do you meant
"Here is a patch for the management of the bad/good checksum for ISIS
(like TCP/UDP/IP).
support added for :
- booleans hf_isis_lsp_checksum_good, hf_isis_lsp_checksum_bad in the tree,
- information in the info column if bad checksum,
- expert info for bad checksum,
-
Gerald,
How far in time are we from branching the next release?
I'm almost there with SNMPv3 USM authentication and decryption, and I
would like to know whether if to start checking it in now or to wait
for the branching.
It depends how long we have to wait for the branching to take place.
Lu
I cannot find the source code for gcry_rndw32_gather_random. In the patched
version of libgcrypt used with Wireshark 0.99.4 there is an uninitialized
variable being checked and since it is not consistently set will cause the slow
random bit generation code to be used instead of existing after g
On Tue, Jan 09, 2007 at 02:52:21PM +0100, Sebastien Tandel wrote:
>I am not defending anything here (cause as you said I can change this
> preference rule) but I don't get to the point. CDP is only implemented
> on Cisco routers but there are also Juniper, Hitachi, Alcatel, Nortel,
> 6wind etc.
Hi Guy Harris ,
armed with what you've learned from that book about the format of
Ethernet headers and IP headers,
look at the first 14 bytes of data in the packet (you'll now know
how that produces the display
Thanks for the above suggestion especially the book.
But I'm already awar
Hi,
For now? Yes
Thanx,
Jaap
On Tue, 9 Jan 2007, Sebastien Tandel wrote:
> Hi Jaap,
>
>
>I am not defending anything here (cause as you said I can change this
> preference rule) but I don't get to the point. CDP is only implemented
> on Cisco routers but there are also Juniper, Hitachi, Alc
> I have MSVC 8.0 build 50727. I detest trying to use the M$ compiler
> suite, but sometimes the alternatives are worse.
Do you use the Express Edition or the Studio?
> nmake Makefile.nmake clean
You might better use distclean
> moved my modified config.nmake and Makefile.nmake out of the buil
Hi Jaap,
I am not defending anything here (cause as you said I can change this
preference rule) but I don't get to the point. CDP is only implemented
on Cisco routers but there are also Juniper, Hitachi, Alcatel, Nortel,
6wind etc... Having Cisco routers does not imply you'll configure CDP.
Fu
Ulf Lamping wrote:
> P.S.: In the meantime, I can successfully compile and run Wireshark
> versions generated on every MSVC variant mentioned - so there's actually
> some real progress in this topic ;-)))
This is about as clear as I can make it.
I have MSVC 8.0 build 50727. I detest trying to
Hi,
Can you send a pcap file for testing purpose, please?
Regards,
Sebastien Tandel
Nicola Arnoldi wrote:
> Hi everybody.
> The great work Sebastien did about Roofnet dissectors was related to
> Version 2, which is still far from stable.
> It should be implemented the V 1 as well, which has
Hi everybody.
The great work Sebastien did about Roofnet dissectors was related to
Version 2, which is still far from stable.
It should be implemented the V 1 as well, which has some differences
between V2.
I attach the c++ header, hoping it would be sufficient for you to modify
the dissector accor
58 matches
Mail list logo
