radclient: fix debug to not show source port in hex but as integer #5344
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
...we also replace %i with %u in the second block whilst here
jimdigriz
force-pushed
the
radclient-dehex
branch
from
b6ccd1d
to
dce4fd3
Compare
alandekok
added a commit
that referenced
this pull request
Jun 20, 2024
|
should this be closed since you added 59f5cf1? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Noticed when running
radtestI was seeing hex used to represent the source port.No idea if this was intention (appeared during some RADIUSv1.1 work), as the destination port is shown as an integer, but this commit makes the source port an integer.