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

IRATI stack and wireshark #1343

Open
joholly opened this issue May 19, 2021 · 4 comments
Open

IRATI stack and wireshark #1343

joholly opened this issue May 19, 2021 · 4 comments

Comments

@joholly
Copy link

joholly commented May 19, 2021

Hi,

I set up alittle test enviroment with the IRATI stack. I wanted to use the wireshark application that is deposited in the project.
I'm not sure if I installed it correctly. It seems that wireshark is not able to decode the recieved packages.

The output looks like this:

grafik

I also tried to use this dissector: https://github.com/SIDN/irati-wireshark-dissector.

Can someone help me with this problem?

Greetings,
Jo

@edugrasa
Copy link
Contributor

Hi,

The standard Wireshark package doesn't contain the logic to decode packets belonging to the core RINA protocols (EFCP and CDAP). @cschutijser wrote the dissector you have mentioned in the issue, maybe he can provide some guidance.

Cheers,

Eduard

@cschutijser
Copy link

Hi, I don't see the problem (if any) right away. It does surprise me a little that our dissector doesn't recognize the EFCP payload. In your screenshot, I see that the ethertype is 0xd1f0 and our dissector should act on that.

Is the dissector installed correctly, as explained in the README? You can verify that by starting Wireshark, then selecting Analyze > Enabled Protocols and searching for "efcp". It should display an entry.

If the dissector is indeed installed correctly, you can share a PCAP file with me and I can have a quick look.

@joholly
Copy link
Author

joholly commented Jun 2, 2021

Hi,
I got it fixed. Installing the dissactors of the irati project with

  • configure
  • make
  • make install
    didn't work. I tried to do it with cmake. Some of the generated make files were buggy.
    Now they are working.

@cschutijser
Copy link

Alright! Good to hear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants