DHCP v6 - no route to host
-
Now I know how to reproduce the out of memory issue. I'll have a look later this evening.
-
I saw you have adjusted the raflags accordingly. Just gitsynced and ran some tests and it works like a charm now! Only thing I can't get to work yet is the DHCPv6 reservations. Reservations are simply ignored and an address from the address pool is provided. Is this a thing you're still working on or should it work and do I need to play with it some more to try to get it to work?
-
Actually what I can not do anymore with the latest version is let pfSense send out the advertisements through rtadvd and let my Windows DHCPv6 hand out the IPv6 addresses as it used to do (since I have the IPv6 reservations working on my Windows server). For it to work I need pfSense to advertise itself using the MO flags, but when I configure pfSense in Assisted mode, it automatically also enables its own DHCPv6 service thus causing a conflict on the network with pfSense which is also giving out addresses. Ideally it should be that I can always choose an operating mode on the DHCPv6 page in pfSense, but only when I check the box to enable the DHCPv6 server, it will also enable the DHCPv6 service. Sounds rather logical too if you think about it. Is this a thing you agree on Databeestje and can realize? I can change the Javascript on the page to allow this if you want.
-
Databeestje, I saw you have followed up on my proposal already and checked in some changes regarding this matter. Great work! I have found a few issues with it so far:
1. When I keep the mode at advertised and disable the DHCPv6 service, it still provides DHCPv6 addresses
2. The DHCP service reports an error on startup in the system log:php: /services_dhcpv6.php: The command '/usr/local/sbin/dhcpd -6 -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpdv6.conf -pf /var/run/dhcpdv6.pid em0_vlan3' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /etc/dhcpdv6.conf line 23: expecting string or hexadecimal data. host-identifier option dhcp6.client-id ; ^ /etc/dhcpdv6.conf line 28: expecting string or hexadecimal data. host-identifier option dhcp6.client-id ; ^ Configuration file errors encountered – exiting If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If yo
3. When entering a DUID at the DHCPv6 reservation page, it does not get past the validator which keeps stating that it is not a valid DUID while it is. I also do not understand the remark posted under the field:
Enter a DUID Identifier in the following format:
"DUID-LLT - ETH – TIME --- ---- address ----"
"xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx"My DUID matches the xx:xx format shown, but is not accepted. What is meant with the line above the xx:xx?
-
I see new checkins have been done which fix the DUID problem. I can indeed add a DUID reservation now. However, the whole DHCPv6 system doesn't work anymore with the latest gitsync. I'm getting this error in the system log:
php: /services_dhcpv6.php: The command '/usr/local/sbin/dhcpd -6 -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpdv6.conf -pf /var/run/dhcpdv6.pid em0 em0_vlan3' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /etc/dhcpdv6.conf line 23: expecting string or hexadecimal data. host-identifier option dhcp6.client-id 00-01-00-01-12-0D-0D-6C-00-1E-8C-4A-56-F ^ /etc/dhcpdv6.conf line 36: expecting string or hexadecimal data. host-identifier option dhcp6.client-id ; ^ /etc/dhcpdv6.conf line 41: expecting string or hexadecimal data. host-identifier option dhcp6.client-id ; ^ Configuration file errors encountered – exiting If you did not get this software from ftp.isc.org, pleas
I noticed it complaining about my DUID reservation. I have added it as Windows reports it: in the xx-xx-xx format instead of the required xx:xx:xx format. You might want to add a little regular expression JavaScript validation on the DUID field to make sure its added in the xx:xx:xx format. Or better yet, add a piece of JavaScript to the onblur of the textfield that will replace the '-' with ':' so it's still Windows copy/paste friendly :)
I just changed the DUID to the correct xx:xx:xx format. I'm still getting an error in the system logs and am still not getting a DHCPv6 lease. Also still nothing in the DHCP logs regarding IPv6 requests or responses. The error I'm getting in the system logs is:
php: /services_dhcpv6.php: The command '/usr/local/sbin/dhcpd -6 -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpdv6.conf -pf /var/run/dhcpdv6.pid em0 em0_vlan3' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /etc/dhcpdv6.conf line 36: expecting string or hexadecimal data. host-identifier option dhcp6.client-id ; ^ /etc/dhcpdv6.conf line 41: expecting string or hexadecimal data. host-identifier option dhcp6.client-id ; ^ Configuration file errors encountered – exiting If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. I
It seems there is still something wrong with my reservation so I removed the reservation and restarted the dhcp deamon. Now I'm getting in the situation again where the dhcpd service kills the webinterface of pfSense. Only this time, doing a killall dhcpd on the console did not bring it back up. So next I tried rebooting the pfSense server. Luckily this brings it back up again. I did notice an error during the boot though. Something with a foreach loop in some interfaces file. I tried rebooting again and recording the bootup into an AVI to capture the error, but it did not occur anymore.
After the reboot, still no response from the DHCPv6 service and still this error with all DUID reservations now being removed:
php: : The command '/usr/local/sbin/dhcpd -6 -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpdv6.conf -pf /var/run/dhcpdv6.pid em0 em0_vlan3' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /etc/dhcpdv6.conf line 31: expecting string or hexadecimal data. host-identifier option dhcp6.client-id ; ^ /etc/dhcpdv6.conf line 36: expecting string or hexadecimal data. host-identifier option dhcp6.client-id ; ^ Configuration file errors encountered – exiting If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to requ
The router advertisement flags are still handed out correctly using assisted mode, DHCPv4 addresses are still provided, but no response at all from the DHCPv6 service anymore. May it have something to do with the firwall rules you have cooked into the software? The behavior is the same as when I had my firewall rules set incorrectly.
When I set it to unmanaged mode on the router advertisements, my clients discover the gateway and will auto-generate an IPV6 address to use. So that is okay.
-
More findings. Checking the in the error reported config file at /var/dhcpd/etc/dhcpdv6.conf I noticed the error is referring to the following content of this file:
}host s_opt1_0 {
host-identifier option dhcp6.client-id ;
fixed-address6 2001:470:-removed-:52::21;
option host-name DC4;
}
host s_opt1_1 {
host-identifier option dhcp6.client-id ;
fixed-address6 2001:470:-removed-:52::55;
option host-name KoenLaptop;
}Turns out on a different interface I still had two reservations. I removed these, restarted the dhcp deamon and no errors in the system logs anymore and it did start to provide DHCPv6 addresses again from the pool!
Next I tried adding a DUID reservation again. I did an ipconfig /renew6 on my Windows 7 x64 client and voila: my reserved IPv6 address was returned. Databeestje, you da man! :D
-
One more question.. I notice that when getting an DHCPv6 address from pfSense (either a static reservation or pool address), my Windows 7 x64 client will add a route to the routing table like this:
2001:470:-removed-:51::1111/128
Meaning.. all data between hosts on my local 2001:470:-removed-:51::/64 subnet will be routed to the default IPv6 gateway being pfSense. This brings extra unnecessary load on pfSense and causes the pfSense logs to be filled with entries regarding my local IPv6 traffic. Is it possible to have the clients designate a /64 route to the assigned IPv6 address?
Another question.. what is the IPv6 Prefix Pool field for in a DCHPv6 reservation?
Last thing.. don't forget to put updating /status_dhcpv6_leases.php on the todo list. It does show the leases, but not the IPv6 addresses, still shows a column MAC address instead of DUID and does not allow for pool leases to be translated to a reservation.
-
I was playing with the IPv6 Prefix Pool field and apparently it can kill whole pfSense. I now know why I didn't see the error during boot on the interfaces.inc file anymore. It only appears when having this field set and if so, it will kill the WAN interface completely. I caught the error. Check the attached screenshot. The error points to this section in the interfaces.inc file:
/* Setup the prefix delegation */
foreach($IfList as $pdinterface => $friendly) {
if(is_numeric($interface['ia-pd'])) {
$realif = get_real_interface($friendly);
$dhcp6cconf .= " prefix-interface {$realif} {\n";
$dhcp6cconf .= " sla-id {$interface['ia-pd']};\n";
$dhcp6cconf .= " sla-len {$config['interface'][$interface]['dhcp-ia-pd-len']};\n";
$dhcp6cconf .= " };\n";
}
}I removed this block completely from the interfaces.inc file, rebooted pfSense and now I have a working pfSense installation again. So there is a bug in this block that kills the WAN interface.
-
I also just found out that the DHCPv6 service is still very unstable. After a couple of successful DHCPv6 requests, it will stop responding to DHCPv6 requests. Restarting the dhcpd service will get it going again for a few requests. No errors logged though, so probably very difficult to trace to the cause.
-
The dhcp support is still very much a work in progress. The prefix pool setting for the dhcp client static mapping is for dhcp-pd support. This is what preactically the world will use for deploying IPv6 to end users.
You can save the prefix pool but is not used anywhere yet. That will come later. I need to BBQ first.
-
Might be work in progress, but works very well already :) I found out that deleting the existing /var/dhcpd/var/db/dhcpd6.leases file on my system and restarting the dhcpd service solved the problem of the dhcpd service only staying active for a few requests. It did give my quite some errors after restarting the dhcpd service the first time, but now it's up and running for two days already and still providing IPv6 addresses according to both the pool addresses and the configured reservations. So its almost perfect now.
I'm still wondering how I can solve the problem where the clients assign a /128 route to the assigned IPv6 address thus sending all IPv6 traffic via the pfSense firewall which is the default gateway. For IPv6 traffic on my local LAN this causes a lot of problems. Remote desktops from one machine to another for example will go over IPv6 by default but pfSense will drop a few packets every now and then causing the remote desktop to freeze. These dropped packets are logged by pfSense. When connecting to the same client using its local IPv4 address, it works well. If I could just get it to assign a /64 in the routing table on the client the problem would be solved. Anyone got a clue how to get this done?
-
https://lists.isc.org/pipermail/dhcp-users/2010-January/010810.html
-
Sounds like exactly the problem I was facing. Same errors and outcome. As stated above, for me it was solved by deleting the leases file and having dhcpd create a new one. Its still happily providing IPv6 leases now after being up for 2,5 day already.
-
Currently importing isc dhcpd 4.2.1-P1
-
Cool :) Do you have a clue how I could have the DHCPv6 leases set to /64 in the clients routing table?
-
not yet, open for options. new snapshots on my site with the new dhcpd
-
Hmm.. isn't this a thing that rtadvd should provide? My knowledge about IPv6 isn't sufficient to know if router advertisements should provide this, but it sounds logical. I'll do some searches on the internet to find out more about this.
-
I found a statement in RFC4862 on page 8 which to me sounds like the router advertisement should indeed provide the cidr block by providing an address prefix. I quote:
Router Advertisements also contain zero or more Prefix Information
options that contain information used by stateless address
autoconfiguration to generate global addresses. It should be noted
that a host may use both stateless address autoconfiguration and
DHCPv6 simultaneously. One Prefix Information option field, the
"autonomous address-configuration flag", indicates whether or not the
option even applies to stateless autoconfiguration. If it does,
additional option fields contain a subnet prefix, together with
lifetime values, indicating how long addresses created from the
prefix remain preferred and valid.I remember seeing the cidr notation in the rta config before. I'll check out the rtadvd man pages for more info.
-
I see you already got this stuff included in the /var/etc/rtadvd.conf file and it looks fine. Hmm. What could it be.
-
it appears to be a issue with a combination of the dhcp server and the client.
I've upgraded the dhcp server to 4.2, that should fix the issue with the dhcp leases file. Maybe i'm missing a option I need to send that carries the prefix length.
More work soon, I have a family issue that I find far more important then IPv6 atm.