Project

General

Profile

Bug #3965

dhcp6c started before bridge configured at boot, preventing interface tracking

Added by Gregor Riepl almost 5 years ago. Updated about 3 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv6)
Target version:
-
Start date:
10/28/2014
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.2
Affected Architecture:
amd64

Description

Setup:
- WAN interface configured for DHCPv6 prefix discovery
- LAN interface configured for IPv6, tracking interface WAN

This works, if the LAN interface is a regular network interface.

However, if LAN is a bridge interface, dhcp6c bails out during boot with the following messages:
dhcp6c17652: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
dhcp6c17652: failed initialize control message authentication
dhcp6c17652: skip opening control port
dhcp6c17652: /var/etc/dhcp6c_wan.conf:16 invalid interface (bridge0): Device not configured
dhcp6c17652: failed to parse configuration file

If the lease is renewed manually after boot, IPv6 starts working, since the bridge0 interface exists at this point.

Setting up one of the network interfaces participating in the bridge for tracking seems to work too, but I'd prefer having it on the bridge itself.

I think this only affects 2.2 and not earlier releases, but I'm not 100% sure.

History

#1 Updated by Chris Buechler about 3 years ago

  • Status changed from New to Confirmed

Also available in: Atom PDF