IPv4 DNS servers…

rcfa

Here's another problem:

If my WAN interface In System:Gatways there's always a WAN_DHCP6 gateway is configured for Static IPv4 and DHCP6, then I seemingly can't set IPv4 DNS server entries. If I try, this is what I get:

The following input errors were detected:

    The gateway specified for DNS server '8.8.8.8' is not from the same Address Family as gateway ''.
    The gateway specified for DNS server '8.8.4.4' is not from the same Address Family as gateway ''

I'd understand this error if the interface were ONLY configured for DHCP6, but why can't I set an IPv4 DNS server on an interface that offers IPv4 traffic???

Heck, even after I set the IPv6 configuration of the WAN interface to "none" and turn off IPv6 in System:Advanced:Networking by unchecking the "Allow IPv6" box, I still get this…

rcfa

Uhm, insert foot in mouth, kind of…
...for some reason the Static IPv4 configuration of the WAN interface didn't have the default gatway selected, but "NONE".

Still, the error message is rather misleading. It's not really the wrong address family, it's a WAN interface that's not associated with a gateway. If there's a way to fix that error message, that might help put people on the right track should someone end up in a similar state.

databeestje

I can probably reword that message, "I can't find a IPv4 gateway for 8.8.8.8 "

rcfa

@databeestje:

I can probably reword that message, "I can't find a IPv4 gateway for 8.8.8.8 "

I think that would be much more expressive. There can be many different reason for not being able to find a gateway, but at least that steers in the proper direction, so I think that would be a good change to make.

rcfa

Looks like some work was done on this, if I interpret the code properly:

https://github.com/bsdperimeter/pfsense/commit/020ba5fe8f190954acc8eaa37746fbf88bd5db73

But, while it has nicer wording for the case where the wrong type of gateway address family is active, I still don't see anything for the case where the gateway is plain missing, like was the case here.
Even the new messages will be misleading, if the cause isn't that the gateway is of the wrong type, but if it's just plain not there. Or have there been other changes made elsewhere that cover that case?

databeestje

oh right, lossy memory and a beer later.

databeestje

ding

rcfa

Cool! Thanks!

Would it make sense to have an alert that no valid gateway is given?
I mean, it could be that these are internal/local DNS servers that don't need a gateway, but it could also prevent needle-in-haystack searches…

databeestje

if no gateway is given, the choice is "none" which is valid.

if you have just a single gateway, this value is nill