Project

General

Profile

Bug #3394

radvd wrongly binds to *:546 in some circumstances

Added by Chris Buechler about 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
Start date:
01/14/2014
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.1-IPv6
Affected Architecture:

Description

I can't seem to determine why, as different systems with seemingly identical radvd.conf files don't consistently display the issue, but radvd can bind to UDP6 *:546 where there shouldn't be any reason for it to do so. This can break dhcp6c because the Advertise ends up getting picked up by radvd and dhcp6c never receives it.

History

#1 Updated by Chris Buechler about 7 years ago

I'll provide further details privately to the person working on the issue, it's on a customer system and not something I can replicate with a test setup, nor any other production setups I've checked.

#2 Updated by Chris Buechler about 7 years ago

  • Status changed from New to Feedback

Ermal committed a fix for this in dhcp6c that was causing radvd to inherit its socket.

#3 Updated by Chris Buechler about 7 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF