original IP
information. But if I understand you correctly this is not prudent because it
will have unknown affects on the other packets?
--
Message: 11
Date: Tue, 21 Sep 2010 11:24:00 -0700
From: Guy Harris
Subject: Re: [Wireshark-dev] Encapsulated IP
To: Developer
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 address not the encapsulated Address?
We make no guarantee whatsoever that dissectors for protocols running atop the
encapsulated IP will work cor
: 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
On Sep 20, 2010, at 5:16 PM, Ronald Howe wrote:
> The col_set_writable does not seem to make a difference in the source and
> destination address
Nope. The columns are set based on the addresses set by SET_ADDRESS, and we do
not allow a dissector to prevent another dissector from setting the
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.
On Mon, Sep 20, 2010 at 10:22:45AM -0700, Ronald Howe wrote:
> 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
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
