DHCPv6 failed to load configuration file

  • Hi!

    When the configuration file of DHCPv6 contains some option, DHCP6 failed to load it.

    interface igb0.832 {
            send dhcp-class-identifier "sagem";
            send user-class "+FSVDSL_livebox.Internet.softathome.Livebox3";
            send option-11 00:00:00:00:00:00:00:00:00:00:00:66:74:69:2F:XX:XX:Xx:XX:XX:XX:XX;
            script "/var/etc/dhcp6c_wan_script.sh";
    id-assoc pd 0 { 
            prefix-interface bridge0 {
                    sla-id 0;
                    sla-len 8;

    And the result :

    Aug 27 08:14:03 dhcp6c 15929 failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory 
    Aug 27 08:14:03 dhcp6c 15929 failed initialize control message authentication 
    Aug 27 08:14:03 dhcp6c 15929 skip opening control port 
    Aug 27 08:14:03 dhcp6c 15929 /var/etc/dhcp6c_wan.conf 2: syntax error 
    Aug 27 08:14:03 dhcp6c 15929 /var/etc/dhcp6c_wan.conf 2: fatal parse failure: exiting (1 errors) 

  • Rebel Alliance Developer Netgate

    Are those custom options you entered somewhere like a configuration override file? I don't see anywhere in the code that those options can be set through the GUI or user settings.

    The GUI would have no way to validate if your options are proper/correct for the dhcp6c client if you entered them manually in an override file. You'll have to fix your customizations to match what the client supports.

  • I used the field "Send options" from the GUI. This options are mandatory to connect to Orange France Fiber in DHCPv6.

  • Rebel Alliance Developer Netgate

    Then there is something wrong with your formatting/names/values for those specific options.

    Again, it's all custom input so the GUI can't hold your hand there.

  • I use exactly the same options in DHCPv4 without problem. I just changed option-90 by option-11.

  • Rebel Alliance Developer Netgate

    The DHCP clients are different for v4 (dhclient) and v6 (dhcp6c), they do not necessarily allow or accept the same data. There is no guarantee that will work as you expect.

  • I found on the bug tracker a ticket on the same subject (but raw-option is used): https://redmine.pfsense.org/issues/8173
    I hope you add this quickly !

Log in to reply