On Thu, Mar 16, 2017 at 08:45:34PM +, Kunal Thakrar wrote:
> Hi Peter,
>
> So if using the Lua API, if I put a script which primes the fields I
> am interested in within the plugins folder I will be able to access
> information such as the IP addresses (to see which TCP connection it
> was par
Hi Peter,
So if using the Lua API, if I put a script which primes the fields I am
interested in within the plugins folder I will be able to access information
such as the IP addresses (to see which TCP connection it was part of) and any
information about the HTTP packets (obviously if it was,
Hi Kunal,
On Tue, Mar 14, 2017 at 10:37:47PM +, Kunal Thakrar wrote:
> The next question I had is to do with post-dissectors in Lua. Please
> correct me if I'm wrong, will they allow me to get data in the
> proto-tree section of the main Wireshark screen? At the moment I have
> packets with th
Hi Peter,
Thanks for the response. I found a work-around wherein the stack will stop
fluctuating and having values pushed and popped if I stop live capture (this
was caused by the tap.packet function). This allows me to call wslua scripts
from my C++ code. This is obviously not ideal but might
On Mon, Mar 13, 2017 at 10:25:17PM +, Kunal Thakrar wrote:
> My aim for my module is to create a web browser agnostic developer's
> tools, similar to Chrome and Firefox. When a user opens my module they
> will see all the current TCP conversations occurring on their system
> (this works in a si
Apologies, I assumed my previous email will link to the thread in February but
it did not.
My aim for my module is to create a web browser agnostic developer's tools,
similar to Chrome and Firefox. When a user opens my module they will see all
the current TCP conversations occurring on their s
