Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with wireshark dissector #1963

Closed
remyleone opened this issue Nov 7, 2014 · 10 comments
Closed

Problem with wireshark dissector #1963

remyleone opened this issue Nov 7, 2014 · 10 comments
Assignees
Labels
Platform: native Platform: This PR/issue effects the native platform Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)

Comments

@remyleone
Copy link

I've installed the Wireshark dissector and launch the commands documented in the wiki and it still doesn't work on my Ubuntu 14.10.

$ wireshark --version
wireshark 1.12.0 (Git Rev Unknown from unknown)

$ uname -a
Linux sieben-lincs 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

@OlegHahm OlegHahm added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Platform: native Platform: This PR/issue effects the native platform labels Nov 7, 2014
@miri64
Copy link
Member

miri64 commented Nov 7, 2014

Works like it should on my system, but I've got Ubuntu 14.04 (wireshark 1.10.6). So here's my little troubleshooting rundown ;-):

  • Which application do you use? I think rpl_udp is the best for testing this since it's currently the only example application that generates 6LoWPAN packets
  • Which board are you using? Mind that the dissector only works for native.
  • Are you listening on the right interfaces? If you used cpu/native/tapsetup.sh create with no additional parameters this should be tap0 or tap1
  • are you running wireshark as a non-privileged user or as root? Lua plugins only work in user mode.

@miri64
Copy link
Member

miri64 commented Nov 7, 2014

  • is there any output on the lua console? (Tools -> Lua -> Console)

@miri64
Copy link
Member

miri64 commented Nov 7, 2014

Change log does not really state any great changes to the Dissector API either :/

@OlegHahm
Copy link
Member

OlegHahm commented Nov 7, 2014

I can tell that it was used with rpl_udp on native. Sniffing on tapbr0.

@OlegHahm
Copy link
Member

OlegHahm commented Nov 7, 2014

For the record, it's working on Arch:

wireshark 1.12.1 (Git Rev Unknown from unknown)

Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 3.12.2, with Cairo 1.12.16, with Pango 1.36.6, with
GLib 2.40.0, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
with libnl 3, without SMI, without c-ares, without ADNS, with Lua 5.2, without
Python, with GnuTLS 3.3.7, with Gcrypt 1.6.2, with MIT Kerberos, without GeoIP,
with PortAudio V19-devel (built Jan 31 2014 21:19:35), without AirPcap.

Running on Linux 3.17.2-1-ARCH, with locale en_US.UTF-8, with libpcap version
1.6.2, with libz 1.2.8, GnuTLS 3.3.9, Gcrypt 1.6.2.
Intel(R) Core(TM) i5 CPU       M 520  @ 2.40GHz

Built using gcc 4.9.1 20140903 (prerelease).

@miri64
Copy link
Member

miri64 commented Nov 7, 2014

I can tell that it was used with rpl_udp on native. Sniffing on tapbr0.

Yes, of course. This is also possible :-)

@LudwigKnuepfer
Copy link
Member

What do you mean with "it doesn't work"?

@OlegHahm
Copy link
Member

OlegHahm commented Nov 8, 2014

It doesn't dissect. (Unknown Ethernet type is shown IIRC.)

@remyleone
Copy link
Author

Correct everything is gray and appear as Ethernet
Le 8 nov. 2014 15:39, "Oleg Hahm" notifications@github.com a écrit :

It doesn't dissect. (Unknown Ethernet type is shown IIRC.)


Reply to this email directly or view it on GitHub
#1963 (comment).

@miri64
Copy link
Member

miri64 commented May 26, 2015

Is this still an issue? In general this won't be an issue with the new network stack because the dissector is not needed anymore and I've got the feeling this is more a wireshark error than an error of the dissector.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Platform: native Platform: This PR/issue effects the native platform Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Development

No branches or pull requests

4 participants