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

tools: add support for heuristic SCION traffic identification by wireshark #4582

Merged
merged 7 commits into from
Jul 24, 2024

Conversation

jiceatscion
Copy link
Contributor

Made that default, since the dispacher removal makes port-based sorting flaky.

Fixes #4545

Made that default, since the dispacher removal makes port-based sorting
flaky.
@jiceatscion
Copy link
Contributor Author

This change is Reviewable

@jiceatscion jiceatscion requested a review from a team July 18, 2024 16:45
Copy link
Collaborator

@lukedirtwalker lukedirtwalker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed all commit messages.
Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @jiceatscion)


tools/wireshark/scion.lua line 1175 at r2 (raw file):

-- Two options are available. Identify SCION traffic by port number, or heuristically, by
-- looking for clues in the header. The heuristic is not extremely robust. It may mistake
-- non-SCION packet for scion packets. If you know precisely which ports carry SCION

Suggestion:

SCION

Copy link
Contributor Author

@jiceatscion jiceatscion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @lukedirtwalker)


tools/wireshark/scion.lua line 1175 at r2 (raw file):

-- Two options are available. Identify SCION traffic by port number, or heuristically, by
-- looking for clues in the header. The heuristic is not extremely robust. It may mistake
-- non-SCION packet for scion packets. If you know precisely which ports carry SCION

Done.

Copy link
Collaborator

@lukedirtwalker lukedirtwalker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 1 of 1 files at r3, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @jiceatscion)

a discussion (no related file):
additional fields that we could use:

  • NextHdr
  • DT/DL/ST/SL

But we can also leave it like this for now and refine later.


Copy link
Contributor Author

@jiceatscion jiceatscion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @lukedirtwalker)

a discussion (no related file):

Previously, lukedirtwalker (Lukas Vogel) wrote…

additional fields that we could use:

  • NextHdr
  • DT/DL/ST/SL

But we can also leave it like this for now and refine later.

Good point, not many valid values for a SCION packet. Will do.


Copy link
Contributor Author

@jiceatscion jiceatscion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @lukedirtwalker)

a discussion (no related file):

Previously, jiceatscion wrote…

Good point, not many valid values for a SCION packet. Will do.

done


Copy link
Collaborator

@lukedirtwalker lukedirtwalker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 1 of 1 files at r4, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @jiceatscion)

@jiceatscion jiceatscion merged commit 42e7811 into scionproto:master Jul 24, 2024
5 checks passed
@jiceatscion jiceatscion deleted the fix4545 branch July 24, 2024 12:43
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

Successfully merging this pull request may close these issues.

tools: update wireshark plugin after changes to end host port range
2 participants