New install on 3rd party HW getting "Eligibility" error
-
I am trying to upgrade my backup and then my primary pfSense router to 2.7.2. I made a USB stick with the netgate installer image and booted it and started the install (note I used root/pfsense to login to the console, not admin/pfsense, could that be an issue?).
Note that I plugged my backup router into my switch which is downstream from my primary pfSense router. I configured the WAN to the active connection and LAN to an inactive connection and continued. It gets to the screen to contact NetGate servers and fails.
Can I plug a pfSense router in downstream from another pfSense router to satisfy the "WAN" requirement? Or does it literally have to be plugged into my WAN connection to work? Anything else I am doing that might be incorrect?
I saw in Issues installing Pfsense on Protectli Vault that I can get the legacy installers from https://atxfiles.netgate.com/mirror/downloads/. Is that the right approach?
My plan was to do:
- fresh 2.7.2 install on backup
- restore config from primary to backup
- verify backup
- replace primary w/ backup
- fresh 2.7.2 install on primary
- restore config on primary
- verify
- replace backup w/ primary
Anything wrong with that approach?
-
@RyanM said in New install on 3rd party HW getting "Eligibility" error:
Can I plug a pfSense router in downstream from another pfSense router to satisfy the "WAN" requirement?
Yes that will work fine as long as the con figured LAN does not conflict with that WAN. Like if both routers are using the default 192.168.1.X for example.
-
@stephenw10 which they of course are.
How would others handle this for a home router? I am not sure if I can plug in 2 clients on my WAN.
And what do you think of the approach? Those steps sound reasonable? One hiccup is I need to connect upstream to be able to install packages before restoring config. Or at least I feel like I "should" install the packages before restoring config.
-
Just renumber the LAN for the install to any unused subnet. Or even just unassign the LAN. You only need the WAN interface to access the pkg servers.
