Re: [Wireshark-dev] Encapsulated IP

2010-09-21 Thread Ronald Howe
support list for Wireshark Message-ID: <598c2b55-7ced-47dd-8054-a82247e26...@alum.mit.edu> Content-Type: text/plain; charset=us-ascii On Sep 21, 2010, at 9:51 AM, Ronald Howe wrote: > ok Can I then use SET_ADDRESS to put the Source and Destination fields back > to the original IP add

Re: [Wireshark-dev] Encapsulated IP

2010-09-21 Thread Ronald Howe
: Ronald Howe Subject: Re: [Wireshark-dev] Encapsulated IP To: "wireshark-dev@wireshark.org" Message-ID: Content-Type: text/plain; charset="us-ascii" The col_set_writable does not seem to make a difference in the source and destination address They seem to update when I c

Re: [Wireshark-dev] Encapsulated IP

2010-09-20 Thread Ronald Howe
The col_set_writable does not seem to make a difference in the source and destination address They seem to update when I call the ip dissector again. If I could read those columns before I call the dissector I could replace the fields when it returns but I don't see a function in column-utils.

[Wireshark-dev] Encapsulated IP

2010-09-20 Thread Ronald Howe
Hello I am new and have a question about the IP dissector. I have written a plug-in for my work and one of the packets has encapsulated IP. I call the IP dissector and that works fine my question is there any way to call the dissector and not have it update the source and destination fields? Can