Oh, I understand now, you have to open the Packets window, load a capture,
and then it will work.

On Mon, Aug 2, 2010 at 6:38 PM, f4king it <[email protected]> wrote:

> To work around it, I just added the following to the end of C:\Program
> Files\Wireshark\init.lua
>
> dofile("test.lua")
>
> Now, I do see the Tools -> Test -> Packets menu item, but after loading a
> capture and opening it, there's nothing, as if the tap is not really
> working. Any thoughts? Is this example out-of-date?
>
> Thanks.
>
>
> On Mon, Aug 2, 2010 at 6:31 PM, f4king it <[email protected]> wrote:
>
>> Hi, what is the <personal config dir> [1] on Windows 7, 64-bit? I've
>> enabled lua by editing C:\Program Files\Wireshark\init.lua and
>> setting disable_lua = false, and I created test.lua with the contents of
>> http://www.wireshark.org/docs/wsug_html_chunked/wslua_tap_example.html.
>> However, I can't figure out how to get this to load. I've tried all of the
>> following:
>>
>>    - Put the above script into %APPDATA%\init.lua
>>    - Put the above script into %APPDATA%\Wireshark\init.lua
>>    - set WIRESHARK_LUA_INIT="c:\test\test.lua" and then execute
>>    Wireshark.exe
>>    - C:\Program Files\Wireshark\wireshark.exe -X lua_script:test.lua
>>    (with test.lua being in the current directory)
>>
>> None of these attempts show a new menu item under Tools after I restart
>> Wireshark and load a capture.
>>
>> I'm using Wireshark 1.2.8 and Help -> About shows "with Lua 5.1."
>>
>> If I create a test.lua with the contents print("hello world!") and run
>> tshark and it works fine:
>>
>> C:\Program Files\Wireshark>tshark -X lua_script:test.lua
>> hello world!
>> Capturing on Microsoft
>>   0.000000 9.49.203.197 ->...
>>
>> [1] http://wiki.wireshark.org/Lua
>>
>> Thanks!
>>
>
>
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to