This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Issues with Lua as root user

0

Hi,

I am a new user to wireshark and I just recently compiled wireshark from sources. However, I am facing an issue.

Wireshark is not starting up with Lua capability (unable to view it under Tools->Lua) I did the following steps:

  1. downloaded lua to directory under /usr/local/<lua-5.1>
  2. built lua using "make linux test"
  3. Downloaded wireshark 2.2.7
  4. Did "configure --with-lua" //seems to be working fine.
  5. Did "make" //runs fine , no errors

I also viewed the "About" section when wireshark starts and I am able to see "built with Lua-5.1" But I am very puzzled and perplexed as to why it doesnt show up under "Tools -> Lua"

Also, on another machine, I did this as a non root user and I am able to see Tools->Lua, but the interfaces for packet capture do not show up (probably since this requires root permissions)

I would be grateful if someone could kindly help me out

regards TJ

asked 14 Jun '17, 09:54

tharamur's gravatar image

tharamur
6●1●1●2
accept rate: 0%

edited 14 Jun '17, 10:22

grahamb's gravatar image

grahamb ♦
19.8k●3●30●206

One Answer:

0

By default Lua scripts will not be executed if Wireshark is running as the root user. The theory there is that running Wireshark's 2+ million lines of code as root is bad enough but running scripts would be even worse.

I would very strongly suggest you configure things so you don't have to run Wireshark as root. Gerald's blog post has an excellent description; you'll also find answers on this site on how to do it.

answered 14 Jun '17, 13:29

JeffMorriss's gravatar image

JeffMorriss ♦
6.2k●5●72
accept rate: 27%

Hi Jeff

Thanks a lot for your reply...I'm sorry I couldn't get back sooner, as I was temporarily assigned to another project.

Btw, I tried out the remedies suggested by you, but then the same issue persists When wireshark starts up as non root, none of the interfaces get displayed.

Is there any other way to resolve the issue ?

regards Tej

(05 Jul '17, 09:29) tharamur

Your answer has been converted to a comment as that's how this site works. Please read the FAQ for more information.

(05 Jul '17, 09:37) cmaynard ♦♦

Which method did you use to run Wireshark as non-root (there are a couple alternatives outlined in Gerald's blog post)?

(05 Jul '17, 10:28) JeffMorriss ♦