[Lange Jan-Erik <Jan-Erik.Lange@xxxxxxxxxxxxxx>]

Thanks for the info. I'll try it. But for now the hex editor is Ok.

________________________________________
Von: wireshark-dev-bounces@xxxxxxxxxxxxx [wireshark-dev-bounces@xxxxxxxxxxxxx] im Auftrag von Helge Kruse [Helge.Kruse-nospam@xxxxxxx]
Gesendet: Donnerstag, 18. November 2010 13:16
An: Developer support list for Wireshark; wireshark-dev@xxxxxxxxxxxxx
Betreff: Re: [Wireshark-dev] foo dissector of the dev guide

-------- Original-Nachricht --------
> Datum: Thu, 18 Nov 2010 11:22:19 +0100
> Von: Lange Jan-Erik <Jan-Erik.Lange@xxxxxxxxxxxxxx>
> An: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
> Betreff: Re: [Wireshark-dev] foo dissector of the dev guide

> You're right. I captured UDP Frames from my network. Now I'm working with
> these Frames an modify them in a HEX Editor for testing..
>

Have you considered to use text2pcap? Since the source text editor is always open this might be helpful.

Helge

--
GMX DSL Doppel-Flat ab 19,99 &euro;/mtl.! Jetzt auch mit
gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe