OPNsense Forum
Archive => 21.7 Legacy Series => Topic started by: lrosenman on October 18, 2021, 11:44:32 pm
-
2021-10-18T16:39:25 opnsense[32558] /status_services.php: Warning! dhcpd_dhcp6_configure() found no suitable IPv6 address on opt1
2021-10-18T16:39:25 opnsense[32558] /status_services.php: Warning! dhcpd_dhcp6_configure() found no suitable IPv6 address on opt3
2021-10-18T16:38:43 dhcp6c[52920] child: exec failed: Bad address
2021-10-18T16:38:43 opnsense[63681] plugins_configure newwanip (execute task : webgui_configure_do(,opt5))
2021-10-18T16:38:43 opnsense[63681] plugins_configure newwanip (execute task : vxlan_configure_interface())
2021-10-18T16:38:42 opnsense[63681] plugins_configure newwanip (execute task : unbound_configure_do(,opt5))
2021-10-18T16:38:42 opnsense[63681] /usr/local/etc/rc.newwanipv6: Dynamic DNS: Not updating home.lerctr.org A record because the IP address has not changed.
2021-10-18T16:38:42 opnsense[63681] /usr/local/etc/rc.newwanipv6: Dynamic DNS: Not updating home-fw.lerctr.org A record because the IP address has not changed.
What else do I need to supply?
-
Any ideas on this? It causes dhcpdv6 to die :(
-
I’ll ask the obvious question - the DHCPv6 server is not enabled on that interface?
-
Not that's shown in the GUI.
-
Check under Services/DHCPv6 ?
-
It just shows the one interface that has IPv6 turned on.
-
Just wondering:
Which interface has a static IPv6 address from which you are serving IPv6 DHCP leases?
Do you have a valid IPv6 address on opt5? The DHCP client appears to crash. Is there an IPv6 DHCP server (or a relay) configured on that network?
-
> dhcp6c[52920] child: exec failed: Bad address
What's going on here? DHCPv6 setup on WAN crashes. The rest is just follow-up errors.
Cheers,
Franco
-
@franco: I wish I knew.
This is ATT Fiber, BGW210-700 Gateway. I do have an override config for that interface to get the 8 PD's.
What can I supply to help?
-
There is a Log Level setting under Interfaces: Settings. Best to reboot to make sure debug level properly applied and grab dhcp6c specific lines from System: Log Files: General (most probably, but not around a GUI at the moment).
Cheers,
Franco
-
I've got the debug logs. Is there a place on the system I can grab the files? I have the circular logs turned off.
I'd like to get the files and have y'all look at them.
-
My curiosity continues:
I noticed your work with Franco on dhcpc in 19.1...
Is this a new setup? Or did it once work and has since broken?
Is the BGW210 definitely getting a /60 delegated prefix on it's WAN?
And under the BGW210's DHCP config, both prefix delegation and address assignment are enabled?
On the override, I take it you are using the dhcp.conf override developed for pfSense in the netgate forums. I wasn't aware of one specifically for opnsense. Would there be any opnsense <-> pfSense oddities?
-
Logs are in the /var/log/system/ ordered by date. Most important lines are probably those from "dhcp6c" itself.
Cheers,
Franco
-
It happened again this AM, so I grabbed a grep of dhcp6c from the logs, and also the config file.
attached as a tarball here.
Yes, the interface is getting the /60, and the PD's are happening.
I upgraded the NVG599 to the BGW210-700
I removed the "bypass" stuff, and am using the dhcp6c stuff from pfsense, there doesn't APPEAR to be any nonsense between them.
Any ideas gratefully appreciated.
-
There appears to be some noise in the logs you provided. Potentially there's more happening around the dhcp6c entries than shown in your grep dump.
It might pay to clean up your config. I believe dhcpd is "sensitive" to whitespace, etc. I note that the comments often appear out of order in the log. I would remove all the comments to rule this out.
Also:
If you don't need any of these, I would remove those lines:
send rapid-commit; <-- particularly this one
request domain-name-servers;
request domain-name;
If you don't need a particular PD, don't include the send ia-pd X for that PD and remove the corresponding id-assoc pd X stanza.
On your VLAN interfaces (which you have commented out), you should probably restore the sla-len 0 and delete the second sla-id 0 and the prefix statement. When listing the VLAN prefix-interface you could try the OPT interface but you might need em0.<VLAN ID> as pfSense does, e.g. em0.8. For example:
id-assoc pd 1 {
prefix-interface opt1 {
sla-id 0;
sla-len 0;
};
};
OR
id-assoc pd 1 {
prefix-interface em0.8 {
sla-id 0;
sla-len 0;
};
};
Finally, check you only set the script up on the WAN (em4) interface, and set the other interfaces (em0, opt1, opt3, etc.) to track (then set the proper PD ID down below).
Maybe give that a go and see if things clear up...
-
Thank You. I now have IPv6 on all interfaces. and we'll see if the whines shut up.
# em4 is the WAN interface for my installation.
# Setup requests for the WAN interface.
interface em4 {
# Request a single IPv6 address for WAN interface (RG responds with 2600:1702:xxxx:yyy0::48)
send ia-na 0;
# Request 8x /64 prefix delegations:
send ia-pd 0;
send ia-pd 1;
send ia-pd 2;
send ia-pd 3;
send ia-pd 4;
send ia-pd 5;
send ia-pd 6;
send ia-pd 7;
request domain-name-servers;
request domain-name;
script "/var/etc/dhcp6c_opt5_script.sh";
#script "/conf/set_wan_static_v6.sh";
};
# These blocks are required, and I should probably
# assign the prefixes to the LAN interfaces here.
# Since my /60 has not changed since I implemented
# this, I treat them as static and assign them as such.
id-assoc na 0 { };
id-assoc pd 0 {
prefix-interface em0 {
sla-id 0;
sla-len 0;
};
};
id-assoc pd 1 {
prefix-interface em0_vlan8 {
sla-id 0;
sla-len 0;
# prefix 2600:1700:210:b18e::/64 600 200;
};
};
id-assoc pd 2 {
prefix-interface em0_vlan2 {
sla-id 0;
sla-len 0;
# prefix 2600:1700:210:b18d::/64 600 200;
};
};
id-assoc pd 3 {
prefix-interface em0_vlan10 {
sla-id 0;
sla-len 0;
};
};
id-assoc pd 4 { };
id-assoc pd 5 { };
id-assoc pd 6 { };
id-assoc pd 7 { };
root@home-fw:~ #
-
No worries. Let us know how it goes.
Glad you could keep your comments - and the extra PDs - so far anyway...
It appears I just learnt OPNsense VLAN device notation. That should come in handy in coming weeks... ;D
-
I was going by what ifconfig told me :)
-
FTR, the upgrade to 21.7.4 went flawlessly, and on reboot, all the services and IPv6 came up without manual intervention. I'd say this is solved. Thanks to @benyamin for the pointers to my typographical non-skills.