Dhcp6 client is not running, and if I re-apply lose ipv4 and need to reboot
when I initially was setting up my router IPV6 was working just fine. I have the 4860 I bought through the pfSense store.
when I created my bridge of the OPT ports to bridge my Wi-fi network together, it stopped getting the IPV6 address on the external port, and the way it did that was unusual. I can't find any logs on it 'trying' to get a DHCP6 either, so I'm not sure what is happening.
Intiially I had it set up to WAN to get IPV6 via DHCP, and then LAN port to get it via track. This worked great.
After I created my bridge, and stopped the LAN port from getting it via track and made the bridge get the address via track it stopped getting an IP.
So did the WAN port.
I then saw I should have turned on the 'suggest' and set the mask to a /64 as that seems to be the general consensus for TWC (TIme Warner Cable).
What happens then was really odd.
The IPV4 address on my wan port disappeared, the IPV6 address appeared, and my bridge had the correct ipv6 address. I rebooted the router and when it came back up, I have IPV4 addresses but no IPV6 address and I don't see anything in the log about the WAN port and DHCP6.
The error that was in the wan port for the IPV4 after I 'applied' the 'send hint' option for IPV6 was:
Other log entries about the IPV6:
Mar 2 11:24:10 pfSense dhcp6c: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory Mar 2 11:24:10 pfSense dhcp6c: failed initialize control message authentication Mar 2 11:24:10 pfSense dhcp6c: skip opening control port Mar 2 11:24:11 pfSense dhcp6c: XID mismatch Mar 2 11:24:11 pfSense dhcp6c: XID mismatch Mar 2 11:24:12 pfSense dhcp6c: XID mismatch Mar 2 11:24:12 pfSense dhcp6c: XID mismatch
There was an error on my screen about the WAN port post /64 hint apply with regards to the IPV4 address, but I can't find it in the logs. I've searched the dhcpd.log which I found the above errors, but not finding the errors that were in the web interface after this happened. I'm scanning other logs around this time but so far no luck.
I did find this: https://doc.pfsense.org/index.php/DHCPv6_Client_XID_Mismatch but there is no dhcp6c running
I followed the steps though because of not finding any, and after I apply it:
Mar 3 09:42:04 kernel: arpresolve: can't allocate llinfo for <myip4 address=""> on igb1 Mar 3 09:42:04 kernel: arpresolve: can't allocate llinfo for <myip4 address=""> on igb1 Mar 3 09:42:04 kernel: arpresolve: can't allocate llinfo for <myip4 address=""> on igb1 Mar 3 09:42:04 kernel: arpresolve: can't allocate llinfo for <myip4 address=""> on igb1</myip4></myip4></myip4></myip4>
the IP address on my wan port begins to come and go after this, and only a reboot seems to recover it. After reboot, no dhclient6 is running, and no ipv6 addresses. if I repeat the above, ta-da it does it again.
What can I provide to help figure this one out?
hda last edited by
You have apparently changed the default working config. ;) Why are you bridgeing and not applying an AP to a LAN ?
Try the concise method. Draw network setup. Post config GUI-screens. Concentrate on 1 LAN routing and suspend bridgeing.
In general you want a smaller prefixnumber (e.g. /60) than a /64 on WAN from ISP.
I'm bridging because the way my house is set up I have APs in different spots around the house, I need seamless transition from one AP to the next and if you change network ports I change networks. A bridge lets it be one flat network between the three 802.11ac points so as devices transition as they move throughout the house network connectivity doesn't go goofy.
VPN clients will disconnect, etc if I change underlying networks.
This is the way I've done it since early 1999 or so, and if it wasn't broke not in a hurry to fix it but Is there another method besides bridging that will allow me to continue a flat network on each port? Based on my knowledge I have to create four subnets and have four different DHCP ranges and this causes issues. I'd prefer to have a single device that does both my network switching & internet firewall/routing.
I'd prefer not to step it down to a single LAN as my connectivity via wifi sucks without distributed hot spots, and also to be honest what I'm doing was handled just fine by my lower performance router i replaced because of my update to faster internet. It's not that I'm having trouble distributing the IPV6, I'm not getting one and DHCLIENT6 is not running. It'd be one thing to me if I was getting an IPV6 on my WAN port, but I'm not even getting that. If I do get that, my IPV4 stack crashes and requires a reboot to recover. The WAN port isn't bridged in anyway, its' off by itself.
My Network Diagram of the physical layer.
Based on everything I've read about the way TWC works for IPV6 is they give you a /64, so that's what I was going with.
Screen shots of my extremely basic configuration (checkboxes checked) is here http://imgur.com/a/EyljQ