Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

BestMatchPinger fails to initialize when IPv6 is not available

Description

Excerpt from chat:

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed May 17, 2017 at 10:10 AM

Benjamin Reed May 15, 2017 at 10:34 PM

Custom-built a kernel without IPv6 support and was able to reproduce this. Found one issue, and in fixing that, found another.

Ronny Trommer May 13, 2017 at 9:42 AM

What Linux distribution do you use? It seems to me you ran in a very specific corner case. Can you explain why you are running an operating system with completely non-existing IPv6 support at all?

Just for further readings: https://blogs.cisco.com/enterprise/disable-ipv6

Benjamin Reed May 12, 2017 at 5:49 PM

I'm not able to figure out how to set up an environment that mimics this problem so I can't reproduce it. If I just disable IPv6 on Linux the protocol support is still there, it's just disabled getting IPv6 addresses. Even docker on my machine supports IPv6.

Can you tell me how your particular environment was set up?

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created May 9, 2017 at 12:48 PM
Updated April 16, 2018 at 4:40 PM
Resolved May 18, 2017 at 8:21 AM