Is this normal behavior for the Resolver to act that way?
-
@stephenw10 said in Is this normal behavior for the Resolver to act that way?:
Hmm, so it still failed at boot with outbound NAT set to automatic?
I wonder if you have ever seen this in the system log after a boot or reboot
php-fpm 589 /rc.newwanipv6: Gateway, NONE AVAILABLE
I have every time and I only have one wan;gateway;ISP set DHCP. -
Yeah that's normal if you don't have a v6 gateway defined. It shouldn't cause a problem.
-
@stephenw10 System/routing/gateways default gateway set Automatic
and also tried WAN_DHCP both get no default route found and the no gateway. Also, have outbound mode set on Automatic outbound NAT rule too.
If I wait long enough (1-5mins) it just finds a route/gateway by itself usually. Until it does dns queries fail which is a problem. -
For IPv6 specifically?
-
@stephenw10 Yes. pfSense plus 24.11 seems not to like the wan to be set DHCP.
-
Specifically IPv6 set to DHCP though?
How is your DNS configured? By default Unbound resolves directly and will use IPv4.
-
@stephenw10 unbound is set forwarding mode and use ssl/tls with outgoing network interfaces set to all. Should I set outgoing network interfaces to WAN only ipv4 and ipv6 interface instead when forwarding ?
-
Do you have an IPv6 address at all? I'm not sure quite what problem you're seeing here?
If you set the default IPv6 gateway to automatic and don't have a valid IPv6 connection then that log entry is expected.
Obviously for for IPv6 outbound NAT normally doesn't come into play (assuming you do have a valid v6 IP). For for ther 4 or v6 Unbound itself should use the public IP without NAT.
-
@stephenw10 After every reboot or cold boot there is always a wait before there is a IPv6 gateway. LAN is set track interface(WAN) Router Advertisements is set unmanaged should it be Assisted? IPv6 gateway also breaks when DHCP lease expire(WAN/ISP DHCP server) for IPv6 and the get new IP is ignored. pfsense DHCP6c never changes the IP treats DHCP like its static then things like streaming break/stop. Yes the ISP sucks but setting DHCP should be dynamic not static. Still on version 24.11
-
Sounds like you might want/need to set 'do not wait for RA' in the dhcpv6 client settings on the WAN. Otherwise you will only see it connect after the ISP sends an RA and that can vary a lot.
