Bugs/Problems with Netgate Installer Beta
-
Yes 24.03-Beta2 is still (confusingly!) the current version of the Net Installer. Expect an update name/number shortly.
That's all good feedback though. Thanks!
-
@bmeeks said in Bugs/Problems with Netgate Installer Beta:
@Gertjan, I believe he is talking about the relatively new pfSense Online Network Installer described here: https://docs.netgate.com/pfsense/en/latest/install/netinstaller.html. Unfortunately (or maybe fortunately) it currently has a major/minor versioning scheme that mimics pfSense Plus, so it's easy to get the two different products confused
.It's literally in the caption: "Installer Beta" :) Yes I'm reporting details about the installer beta not the images that can be installed which have other versions alltogether :)
-
Point 3 (gw which can't be set unless IP is /24) is a nightmare. I only happened to bypass using /24 by accident.
All of the WAN/LAN settings does at the installer stage are completely lost when the installed system reboots. Need to redo it all with the command line wizard.
I do not see the point of the installer.
Is it so hard to let download either an ISO for pfSense CE or an ISO for pfSense+ ?
Or keep a single ISO for pfSense CE and keep the move to pfSense+ as an opt-in upgrade from the installed pfSense CE, as before. What were the issues which triggered this effort toward a far from sleek and complete global installer ? -
@lvrmsc said in Bugs/Problems with Netgate Installer Beta:
Point 3 (gw which can't be set unless IP is /24) is a nightmare. I only happened to bypass using /24 by accident.
That's fixed in the new version which is imminent.
@lvrmsc said in Bugs/Problems with Netgate Installer Beta:
All of the WAN/LAN settings does at the installer stage are completely lost when the installed system reboots. Need to redo it all with the command line wizard.
Yes, that's a feature that's coming. It would also be nice to pull the WAN settings from an imported or recovered config at that stage.
-
@lvrmsc said in Bugs/Problems with Netgate Installer Beta:
I do not see the point of the installer.
Is it so hard to let download either an ISO for pfSense CE or an ISO for pfSense+ ?
Or keep a single ISO for pfSense CE and keep the move to pfSense+ as an opt-in upgrade from the installed pfSense CE, as before. What were the issues which triggered this effort toward a far from sleek and complete global installer ?The point of the net installer for me is to be able to install 23.09.1. If you install CE and then move to pfSense+, it only gives you the option to move to 24.03 and no other version.
The second reason is that of convenience. I just did a netinstall over the top of another virtualised pfSense build and in no time at all I had everything reinstalled and it took in my previous config sitting on the disk. I was really impressed. I did have the issue of the /24 on the WAN being enforced and borking if I added /29, and the borking about the DHCP range when I have DHCP on the LAN turned off, but thankfully those issues were able to be worked around and bypassed.
-
@stephenw10 said in Bugs/Problems with Netgate Installer Beta:
@lvrmsc said in Bugs/Problems with Netgate Installer Beta:
Point 3 (gw which can't be set unless IP is /24) is a nightmare. I only happened to bypass using /24 by accident.
That's fixed in the new version which is imminent.
Is this the case ? I find installer v1.0-RC still cannot work with "weird" gateways. Some virtual environments give you a gateway thats out of subnet and need to be interface bound like WAN IP is 203.0.113.99/24 but the gateway is 100.100.0.0%vtnet0
-
What was fixed there was the ability to add a gateway when the subnet was anything other than /24. That was a pretty clear bug.
But setting a non-local gateway outside the WAN subnet is not yet allowed. Let me raise it internally....
-
@stephenw10
Also it seems to me that everything DNS without giving it a forwarder on the outside is pretty much non-working, too.
E.g. setting not setting anything and configure using DNS resolver results in non working pkg check. Setting it to 127.0.0.1 and DNS resolver also doesn't work. So installing only seems to work if you explicitly enter a forwarding DNS on the outside, using unbound itself for root doesn't seem to work. -
Hmm, like if you configure the WAN statically and have to enter a DNS server? In the 1.0-RC version I assume?
-
@stephenw10 Aye that's right
