Fix: Handle IPv6 Stack Unavailability in Traceroute Functionality (Generated by Ana - AI SDE) #11
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.
Description
This pull request addresses an issue where the traceroute functionality would fail on systems without an available IPv6 stack.
Specifically, the
Tracer
class inconnvitals/traceroute.py
now gracefully handles the absence of an IPv6 stack by checking for its availability before attempting to create IPv6 sockets. If the stack is not available, anEnvironmentError
is raised, preventing crashes and providing a more informative error message.Changes
socket.has_ipv6
in theTracer.__init__
method before creating IPv6 sockets.EnvironmentError
is raised with a message indicating that the IPv6 stack is not available on the system.Fixes Issue 9
This patch was generated by Ana - AI SDE, an AI-powered software development assistant.