Netgate Installer v1.1.1 PPPoE DNS resolution
-
I am at a lost on how to further troubleshoot this..
PPPoE on a tagged vlan that can't reach the Netgate servers.. seems like Operator error BUT the installer does get the corerct IP address (a static).
From a virtual console I can ifconfig to see that, and I can ping 8.8.8.8 but can't resolve www.google.com and thus curl -I https://ews.netgate.com doesn't work either.
I tried local resolver setting false and true but that didn't get me going.
The installer a couple versions back, DID work, the last time I used it. I don't seem to have it anymore.
I am in Canada on Bell, if there is anyone here on the same?
Thanks!
-
I may have replicated this on a local setup.
Can you resolve anything just using for example:
host pfsense.org?If you set use local resolver to true does it still connect to the PPPoE and get an address and gateway?
-
I just tested this again:
First attempt, left use local resolver at false. Got an IP, can ping 8.8.8.8 but can't resolve anything including host pfsense.org
reboot
2nd attempt, changed use local resolver to true. DID NOT connect to PPPoE, so no address or gateway. You were right about that :-)
-
Ok, digging....
-
@stephenw10 How was your digging? Is this an issue with the installer, or is it supposed to work? Thanks!!
-
It looks like a DNS issue. I opened a bug/feature to add the required pull lines: https://redmine.pfsense.org/issues/16587
-
@stephenw10 Ah, OK thanks! It doesn't really explain to us mere mortals why setting local resolver to true doesn't connect to PPPoE, but maybe that will be fixed also?
Unless I am doing something wrong, 1.1.1 installer doesn't work on PPPoE WAN with a vlan. At least with my ISP and setup at the office.
Obviously there are ways around that at the office with an existing WAN, but in the field or for a new customer this is an issue.
Thanks for your help as always!
-
Indeed, I can't explain that either. Yet. It looks like there was some bug in earlier versions that was actually allowing Unbound resolution locally when it should not have been.
-
To chime in, exactly the same issue here. A lot of our cutomers have fiber with PPPoE on a VLAN. Most of them have 2100's, some smaller offices have 1100's. On a two or three occasions I had issues and wanted to start from scratch, but oh my what a terror this installer is, especially with PPPoE. In the end I made a hotspot on my phone, connected that through a TP-Link WR902AC to the WAN of the Netgate and went that route.
In the office I just tried with a spare 2100, and this installer... well it's just so slow and cumbersome. I'm glad I saved the old recovery images. So much faster to just install that, restore the config and upgrade from pfSense itself. I've read here on the forum that the reasoning for the installer is users don't have to download a new ISO ir image for every release, but given the release cadence that would be twice a year max. And for getting up and running fast in case of issues, I really prefer that to the installer. I would really like to see the old style recovery images getting back. It's so much faster to restore from them, not dependent of a connection and so far much less error or issue prone.Having said that, as said I chimed in to get notifications on this. The redmine ticket shows it's already in the dev-builds, I will try to reinstall on a PPPoE link whenever installer 1.2 is at least RC. Thanks for fixing the issue!
-
Yup, it's fixed in internal 1.2 builds. It also has other fixes, hopefully we can get that out very soon.
