Ah, yes. I already have that documentation and the problem is I don't see how those 5 bytes relate to the document description. Like I said, the 5th byte is apparently a sequence number and increments by one each packet. The first byte is always 0x30... etc... now if you can look at the 5 bytes I am seeing and help me map them to the protocol description then I would be very grateful, but I fail to see the correlation...
Now you see my biggest problem. I am having trouble mapping what I see to the protocol description.
Bill
Anders Broman <a.broman@xxxxxxxxx> wrote:
Hi,
What should be done is to make a dissector for OpenVPN packages a protocol
description
Of sorts can be found at
http://svn.openvpn.net/projects/openvpn/trunk/openvpn/ssl.h
Best
regards
Anders
________________________________________
Fr�n: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] F�r Bill Fassler
Skickat: den 15 mars 2007 22:14
Till: wireshark-dev@xxxxxxxxxxxxx
�mne: Re: [Wireshark-dev] decoding thru unencrypted VPN tunnel
I haven't heard from anyone since my last post. Is the general opinion that
I should use the LUA interface, write a dissector, use "decode as" with a
byte offset (if possible) or some other method? The VPN tunnel is OpenVPN,
but I am not yet familiar with the 5 byte header into the encapsulated
payload. I guess I could write a simple plugin that doesn't decode the first
5 bytes and then passes the rest of the payload to the IP dissector and all
should roll downhill......
Bill
________________________________________
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink
Q&A.
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Need Mail bonding?
Go to the
Yahoo! Mail Q&A for
great tips from Yahoo! Answers users.
