Skip to content

Conversation

bunert
Copy link
Contributor

@bunert bunert commented Sep 8, 2022

Correct the behavior of the --max-mtu flag for scion ping.

Previously, there was a bug where the calculated payload size was ignored and the value from --payload-size was taken.
In most cases, this would be the default.


This change is Reviewable

The maxMTU flag for the scion ping overwrites the payload size which is used when initializing the ping config. There was an error that the updated payload size was not used during initialization.

Changes:
    - changed the value used for the PayloadSize for the ping config
Copy link
Contributor

@oncilla oncilla left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 1 files at r1.
Reviewable status: all files reviewed (commit messages unreviewed), all discussions resolved (waiting on @bunert)

Copy link
Contributor

@oncilla oncilla 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: :shipit: complete! all files reviewed, all discussions resolved (waiting on @bunert)

@oncilla oncilla changed the title scion/cmd: do not ignore payload size if maxMTU flag is set cmd/scion: set payload size appropriately if --max-mtu is set Sep 8, 2022
@oncilla oncilla merged commit 248ce0d into scionproto:master Sep 8, 2022
benthor pushed a commit to benthor/scion that referenced this pull request Nov 24, 2022
…roto#4250)

Correct the behavior of the `--max-mtu` flag for `scion ping`.

Previously, there was a bug where the calculated payload size was ignored and the value from `--payload-size` was taken.
In most cases, this would be the default.
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.

2 participants