core: Parsing configuration failed at startup between bridge and dhcp6c on WAN

Hi all,

Following https://github.com/opnsense/dhcp6c/issues/7, I’ve an issue that is probably not on the dhcp6c client but maybe on config testers during boot sequence.

I’m using OPNSense following this setup : https://wiki.opnsense.org/manual/how-tos/orange_fr_fttp.html

My box is set up as :

  • igb0 as WAN
  • igb1, igb2, igb3… as bridge0
  • bridge0 as LAN

I’m using a QOTOM hardware with 6x Intel interfaces.

On startup, dhcp6c client parses the config file and see that my LAN interface (bridge0) is tracking the WAN interface to get IPv6 configuration, but bridge0 is not set up at this moment, so the config fails and dhcp6c didnt start.

Jan  8 20:19:12 opnsense dhcp6c[38999]: /var/etc/dhcp6c_wan.conf:13 invalid interface (bridge0): Device not configured
Jan  8 20:19:12 opnsense dhcp6c[38999]: called
Jan  8 20:19:12 opnsense dhcp6c[38999]: failed to parse configuration file

I need to force a dhcp refresh by saving the WAN page settings and click on « apply », on each startup, to get IPv6 working correctly.

How to reproduce :

  • set up a WAN interface with dhcp6c
  • set up a LAN interface with bridge on multiple physical interfaces
  • set up id-assoc to the bridge interface
id-assoc pd 0 {
  prefix-interface bridge0 {
    sla-id 0;
    sla-len 8;
  };
};

  • reboot
  • see logs

What expected :

  • no errors during boot, ipv6 working directly

I had this issue on 1.8.7 and also after upgrading to 1.9.1

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 31 (30 by maintainers)

Commits related to this issue

Most upvoted comments

Ok thanks, you will have to do it for every update you perform since patches aren’t sticky (they are a test tool after all), but then I can close the issue now and test further to make sure 19.7 is as good as it gets. 😃

Thank you, Franco