trafgen: Fix for ipv6 header generation when L3-only devices are present #233
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.
When trying to run trafgen with a config which included the ipv6() header generation helper function, I noticed the tool halting without sending any traffic.
By further inspection I found out that the issue was a segmentation fault caused by NULL pointer deferencing inside the lookup function for the device ipv6 address.
Apparently, the getifaddrs function returns a linked list node for L2 even in the case of L3 interfaces (in my case, it was a TUN device created in the network) but with the pointer to the address structure set to NULL. This causes a segfault when trying to access the address family from it.
I solved the issue by checking the validity of the pointer beforehand.