Bug #3965
closed
dhcp6c started before bridge configured at boot, preventing interface tracking
Added by Gregor Riepl over 9 years ago. Updated over 3 years ago.
100%
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.
Updated by Chris Buechler almost 8 years ago
- Status changed from New to Confirmed
Updated by Manu Bretelle over 3 years ago
It seems this is the same issue as https://github.com/opnsense/core/issues/3199
and patch https://github.com/KontextWork/opnsense_core/commit/7db2af80e33e975cb222a3091c9eee20e06b3da0 .
Updated by Viktor Gurov over 3 years ago
- Affected Version changed from 2.2 to 2.5.0
Updated by Kewin Christensen over 3 years ago
For reference. I'm seeing the same issues without having a bridge - but just multiple tracked VLAN interfaces. It seems random which interface it complains about at boot:
dhcp6c_wan.conf:
interface igb1.102 {
send ia-na 0; # request stateful address
send ia-pd 0; # request prefix delegation
request domain-name-servers;
request domain-name;
script "/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh"; # we'd like nameservers and RTSOLD to do all the work
};
id-assoc na 0 { };
id-assoc pd 0 {
prefix-interface igb0 {
sla-id 1;
sla-len 8;
};
prefix-interface igb0.10 {
sla-id 2;
sla-len 8;
};
prefix-interface igb0.60 {
sla-id 4;
sla-len 8;
};
prefix-interface igb0.20 {
sla-id 32;
sla-len 8;
};
prefix-interface igb0.50 {
sla-id 80;
sla-len 8;
};
};
After reboot:
Nov 25 09:14:23 router dhcp6c18939: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Nov 25 09:14:23 router dhcp6c18939: failed initialize control message authentication
Nov 25 09:14:23 router dhcp6c18939: skip opening control port
Nov 25 09:14:23 router dhcp6c18939: /var/etc/dhcp6c_wan.conf:21 invalid interface (igb0.60): Device not configured
Nov 25 09:14:23 router dhcp6c18939: failed to parse configuration file
After another reboot:
Nov 25 09:39:54 router dhcp6c18497: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Nov 25 09:39:54 router dhcp6c18497: failed initialize control message authentication
Nov 25 09:39:54 router dhcp6c18497: skip opening control port
Nov 25 09:39:54 router dhcp6c18497: /var/etc/dhcp6c_wan.conf:17 invalid interface (igb0.10): Device not configured
Nov 25 09:39:54 router dhcp6c18497: failed to parse configuration file
And dhcp6c will remain crashed until I do a save/apply on WAN, then everything will come up. So I also suspect a race condition where dhcp6c is started before all interfaces are configured.
Updated by Kewin Christensen over 3 years ago
Seems Vyatta also suffers from this bug: https://phabricator.vyos.net/T2741
Updated by Viktor Gurov over 3 years ago
Updated by Renato Botelho over 3 years ago
- Status changed from Confirmed to Pull Request Review
- Assignee set to Viktor Gurov
- Target version set to 2.5.0
- Affected Version changed from 2.5.0 to All
Updated by Renato Botelho over 3 years ago
- Status changed from Pull Request Review to Feedback
PR has been merged. Thanks!
Updated by Viktor Gurov over 3 years ago
- % Done changed from 0 to 100
Applied in changeset de2d64abc0bad744ecb34cdd4bda890c60026dca.
Updated by Kewin Christensen over 3 years ago
I'm afraid the issue wasn't fixed.
Tested on 2.5.0.a.20201126.1250 (Hardware: APU2):
Reboot:
Nov 26 22:13:51 router dhcp6c27606: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Nov 26 22:13:51 router dhcp6c27606: failed initialize control message authentication
Nov 26 22:13:51 router dhcp6c27606: skip opening control port
Nov 26 22:13:51 router dhcp6c27606: /var/etc/dhcp6c_wan.conf:17 invalid interface (igb0.10): Device not configured
Nov 26 22:13:51 router dhcp6c27606: failed to parse configuration file
Reboot:
Nov 26 23:09:01 router dhcp6c25453: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Nov 26 23:09:01 router dhcp6c25453: failed initialize control message authentication
Nov 26 23:09:01 router dhcp6c25453: skip opening control port
Nov 26 23:09:01 router dhcp6c25453: /var/etc/dhcp6c_wan.conf:17 invalid interface (igb0.10): Device not configured
Nov 26 23:09:01 router dhcp6c25453: failed to parse configuration file
Reboot:
Nov 26 23:17:56 router dhcp6c27347: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Nov 26 23:17:56 router dhcp6c27347: failed initialize control message authentication
Nov 26 23:17:56 router dhcp6c27347: skip opening control port
Nov 26 23:17:56 router dhcp6c27347: /var/etc/dhcp6c_wan.conf:17 invalid interface (igb0.10): Device not configured
Nov 26 23:17:56 router dhcp6c27347: failed to parse configuration file
Save/Apply on WAN:
Nov 26 23:21:57 router dhcp6c71486: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Nov 26 23:21:57 router dhcp6c71486: failed initialize control message authentication
Nov 26 23:21:57 router dhcp6c71486: skip opening control port
Nov 26 23:21:58 router dhcp6c72121: Sending Solicit
Nov 26 23:21:59 router dhcp6c72121: Sending Request
Nov 26 23:21:59 router dhcp6c72121: dhcp6c Received REQUEST
Nov 26 23:21:59 router dhcp6c72121: add an address 2001:db8:801f:bb01:x:y:fe41:780/64 on igb0
Nov 26 23:21:59 router dhcp6c72121: add an address 2001:db8:801f:bb02:x:y:fe41:780/64 on igb0.10
Nov 26 23:21:59 router dhcp6c72121: add an address 2001:db8:801f:bb04:x:y:fe41:780/64 on igb0.60
Nov 26 23:21:59 router dhcp6c72121: add an address 2001:db8:801f:bb20:x:y:fe41:780/64 on igb0.20
Nov 26 23:21:59 router dhcp6c72121: add an address 2001:db8:801f:bb50:x:y:fe41:780/64 on igb0.50
Nov 26 23:21:59 router dhcp6c72121: add an address 2001:db8:100:0:174:b2db:c435:fb1/128 on igb1.102
cat /var/etc/dhcp6c_wan.conf
interface igb1.102 {
send ia-na 0; # request stateful address
send ia-pd 0; # request prefix delegation
request domain-name-servers;
request domain-name;
script "/var/etc/dhcp6c_wan_script.sh"; # we'd like some nameservers please
};
id-assoc na 0 { };
id-assoc pd 0 {
prefix-interface igb0 {
sla-id 1;
sla-len 8;
};
prefix-interface igb0.10 {
sla-id 2;
sla-len 8;
};
prefix-interface igb0.60 {
sla-id 4;
sla-len 8;
};
prefix-interface igb0.20 {
sla-id 32;
sla-len 8;
};
prefix-interface igb0.50 {
sla-id 80;
sla-len 8;
};
};
Updated by Viktor Gurov over 3 years ago
Kewin Christensen wrote:
I'm afraid the issue wasn't fixed.
try to update to the latest snapshot,
works as expected on 2.5.0.a.20201126.1850 with bridge or vlan track interfaces (vtnet)
Updated by Kewin Christensen over 3 years ago
Updated to 2.5.0.a.20201127.0050 - still no dice :(
After update:
Nov 27 11:59:15 router dhcp6c28729: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Nov 27 11:59:15 router dhcp6c28729: failed initialize control message authentication
Nov 27 11:59:15 router dhcp6c28729: skip opening control port
Nov 27 11:59:15 router dhcp6c28729: /var/etc/dhcp6c_wan.conf:17 invalid interface (igb0.10): Device not configured
Nov 27 11:59:15 router dhcp6c28729: failed to parse configuration file
Reboot:
Nov 27 12:14:14 router dhcp6c27889: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
Nov 27 12:14:14 router dhcp6c27889: failed initialize control message authentication
Nov 27 12:14:14 router dhcp6c27889: skip opening control port
Nov 27 12:14:14 router dhcp6c27889: /var/etc/dhcp6c_wan.conf:17 invalid interface (igb0.10): Device not configured
Nov 27 12:14:14 router dhcp6c27889: failed to parse configuration file
Dunno if it makes a difference, but my WAN is also a VLAN on igb1.102 and there are 5 interfaces tracking, 1 parent and 4 VLANs. I have no bridges.
Updated by Viktor Gurov over 3 years ago
Kewin Christensen wrote:
Updated to 2.5.0.a.20201127.0050 - still no dice :(
as bridge track interface issue is resolved, please create a new redmine issue concerning VLAN track interfaces
and provide detailed configuration info of all your interfaces
Updated by Viktor Gurov over 3 years ago
Kewin Christensen wrote:
Updated to 2.5.0.a.20201127.0050 - still no dice :(
Dunno if it makes a difference, but my WAN is also a VLAN on igb1.102 and there are 5 interfaces tracking, 1 parent and 4 VLANs. I have no bridges.
got it, no need to create a new issue:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/70
Updated by Jim Pingle over 3 years ago
- Status changed from Feedback to Pull Request Review
Updated by Renato Botelho over 3 years ago
- Status changed from Pull Request Review to Feedback
PR has been merged. Thanks!
Updated by Viktor Gurov over 3 years ago
- Status changed from Feedback to Resolved
works as expected on 2.5.0.a.20201215.0250