My pc isn't DNS resolving but my pfSense box is
-
@stephenw10 gotcha, thank you so much for the education, I so much appreciate it.
My IPv6 still shows as pending and unknown.
Is this something that will resolve on it's own or do I have some more troubleshooting to do?
-
Unlikely it would just start working, unless it's something broken at your ISP that they then fix.
Does your ISP support IPv6?
-
@Neoveo said in My pc isn't DNS resolving but my pfSense box is:
while my gateway was showing offline with 100% packet loss
Get back to System >Routing > Gateways and edit the WAN_DHCP, just to look.
At the bottom of the page, click also on "Advanced settings".
The gateway monitoring is used for two things : in measures the round trip of a constant ping so nice graphs can be produced.
Also : the action part : it will cycle the interface : taking it down for a short period to rebuild the connection. This in the hope that it will be better (== more stable ping.
Knowing that the WAN interface(s) are use by other processes like unbound, the resolver, they will also restart at that moment. This could very well explain what you've been experiencing all along.IPv6 : First : make things visible. Go to System > Advanced > Networking and check
Start DHCP6 client in debug mode.
From now on, the DHCP6 client (close friend, but not related the DHCP servers on your LAN will log more details.
The logs : Status > System Logs > DHCP
Look for "dhcp6c", that's the one.
During initial WAN (IPv6) construction, there will be more lines.Keep in mind :these days, after severals decades of experimenting, most of the time, you set your WAN IPv4 to 'DHCP' and you'll be good.
For IPv6 it isn't that easy. DHCPv6 is sued, but most probably more settings have to be selected, as every ISP can offer you IPv6 with it's own sauce. It will probably standardize in a decade or two ;)This is the idea :
Your WANv6 interface gets an IPv6, might be a GUA and/or the other thing, starting with a fe80......, the link local.
You will also have a IPV6 DNS, IPv6 gateway and a IPv6 subnet mask.
But there is more, we'll get to that.
-
Okay, I've set up the monitor as you have suggested and here is a screen shot of the logs (for all of the dhcp6c entries it simply says "sending solicit"
file:///home/neo/Pictures/DHCP logs.jpg -
Seems like your ISP doesn't support IPv6 then. Or at least isn't responding to DHCPv6.
Unless they have some special requirement. What does the ISP docs show?
-
@stephenw10 said in My pc isn't DNS resolving but my pfSense box is:
Seems like your ISP doesn't support IPv6 then. Or at least isn't responding to DHCPv6.
Unless they have some special requirement. What does the ISP docs show?
I have sent my ISP a message asking them if they support IPv6, I think they do but we'll see what their answer is.
-
@Neoveo it turns out that my ISP does not currently support IPv6.
-
That's strange.
But make live simpler, for now.
The perfect settings :
Under System > Routing > Gateways delete the IPv6 gateway, and select :
Save, Apply and done.
You could use an alternative : Configuring IPv6 Through A Tunnel Broker Service, I've been using their IPv6 services ( free ! ) for years. Their IPv6 is, IMHO, even today far better as what most ISP offer.
-
@Gertjan So what is the downside if I didn't set the Default gateway IPv6 to none?
I change it to none a few minutes ago but DHCP6 Gateway is still showing up as Pending and Unknown.
-
@Neoveo said in My pc isn't DNS resolving but my pfSense box is:
what is the downside if I didn't set the Default gateway IPv6 to none?
You have the DHCPv6 process running continually trying to get an IPv6 address on the WAN. You likely won't notice but at the very least it spams the logs with pointless errors hiding potentially useful info.
-
@Neoveo said in My pc isn't DNS resolving but my pfSense box is:
DHCP6 Gateway is still showing up as Pending and Unknown.
Delete the now pointless gateway.
