added functions to pad mac strings for net.ParseMAC() #5
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
On MacOS the MAC address strings returned by the ARP library are not directly consumable by the standard library's net.ParseMAC() function because the values aren't printed with a consistent number of digits.
This change adds a function that left pads the chunks between delimiters. If the delimiter is ":" or "-", the string is padded to 2 characters. If the delimiter is "." the string is padded to 4 characters:
0:0:c:7:ac:0 -> 00:00:0c:07:ac:00
0-0-c-7-ac-0 -> 00-00-0c-07-ac-00
0.c07.ac00 -> 0000.0c07.ac00
If the string consists of anything other than hex chars and a single delimiter the string is returned unmodified.