@Df1988_2005 said in New install - Default creds accepted but stays on login screen: v6 routing for internal preferably with OSFPv3 pfSense also to run upon relatively low-performance "iron", but don’t think that, we can to strangle into a VM environment which is only (1CPU / 1GB) OSFPv3, hmmm, if you want fast routing you have to increase the performance (definitely)

@linedan said in Problemes upgrading from 2.3.4 and install of packages: somehow could install the openvpn-client-export-package! Example : check out pfSense 2.4.5-RELEASE-p1 Now Available [image: 1606466395082-9ac4317f-0f54-4f38-b56a-865c3a719c0d-image.png] As the Netgate blog already states with any pfSense upgrade : IF there is a pfSense upgrade available, install that first. Never ever upgrade packages after a pfSense upgrade came out. As you can see in your image above, your pfSense is based on FreeBSD 10.3. Or the repository mentions it's based on FreeBSD 11.3. This means FreeBSD packages (for pfSense) and packages for pfSense that are pulled in are based on 11.3. They will have dependencies that won't work out. For example, a PHP library that is compiled against FreeBSD 11.3 will not work on a FreeBSD 10.3 system. This means : the GUI will go down. So, no "openvpn-client-export-package" for you : the risk is to big. I advise you to have the box send over to you. Or find some one on the other side that can do a bit more as n clicking "Like" on a screen, and you guide this person. Go for a re install, as cleaning out a system with a 'mixed identity' is possible, but very time consuming. It also needs a great deal of knowledge of the OS. I understand that, because of the distance, you won't upgrade every time when a new pfSense versions comes out. It's ok to wait a couple of weeks or even months. But hanging around with a 2.3.4 creates new problems. Knowledge about that version has faded out (on the forum )... I strongly advise you to look around on the forum. Others popped up with upgrade problems from 2.3.4. Some found solutions.

You should look at: https://redmine.pfsense.org/issues/8355 Specifically the last post I just made about NanoBSD being deprecated which leads you down this goatrope path.

You can check for Snapshots here: https://snapshots.pfsense.org/amd64/pfSense_master/installer/ -Rico

@stephenw10 Hi ! Just the 'queue appears hung' and server unreachable on the interface. Fabien

@rickytow Hi rickytow To fix your problem and regain admin access follow these steps. Type number 3 at the console of the device Press Enter/Return. This process resets the admin users password for access to both the console and the web interface to the default value of "pfsense"

@stephenw10 Could be a fault with the switch it's connected to as well.

@Mundon said in NanoPi R2S: NanoPi R2S That board has an ARM CPU: Rockchip RK3328, Quad-core Cortex-A53 The only pfSense ARM CPU's supported are Netgate's own boards. Look for a used PC with a 64-bit x86 CPU. /Bingo

You can use the shellcmd package to start programs at boot. https://docs.netgate.com/pfsense/en/latest/development/boot-commands.html

Custom loader values should be put in /boot/loader.conf.local. Create that file if you don't have it yet. Steve

it install everything is necessary for pfsense to work, dependencies included example: [2.4.5-RELEASE][root@pfSense.trmultiservice.lab]/root: pkg-static install pfSense-pkg-pfBlockerNG-devel-2.2.5_37 Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 9 package(s) will be affected (of 0 checked): <------ 9 dependencies New packages to be INSTALLED: grepcidr: 2.0 [pfSense] iprange: 1.0.4 [pfSense] jq: 1.6 [pfSense] lighttpd: 1.4.54 [pfSense] lua52: 5.2.4 [pfSense] pfSense-pkg-pfBlockerNG-devel: 2.2.5_37 [pfSense] py37-maxminddb: 1.4.1_1 [pfSense] py37-sqlite3: 3.7.7_7 [pfSense] whois: 5.2.17 [pfSense] Number of packages to be installed: 9 The process will require 9 MiB more space. 2 MiB to be downloaded. Proceed with this action? [y/N]: if no "New packages" are available than there is no dependencies needed or they are already installed

Hmm, interesting. You would not normally be able to just change the WAN to PPPoE (from dhcp?). The ISP and the ISPs router would need to already be configured for that. Steve

The solution that worked for me is here, https://forum.netgate.com/topic/156964/how-do-i-change-hard-drive-on-a-working-install?_=1604859343667

Apropriate allow rules (TFTP is UDP 69) , on the affected interfaces. /Bingo

Just had to try a few more things because I am stubborn. Character flaw, but I think at this point I am now done. There is no fix for this NIC/Hitron modem combo. I grabbed another SSD I had around, installed the 2.5 devel, did basic setup only on it- WAN set dhcp, lan set static ipv4. Nothing else. Connected the WAN to the Hitron modem and it flapped maybe twice, then no lights on modem or PFSense NIC. They just don't talk to each other. Connect the WAN to that little Netgear dumb switch and it's fine. So it stays like that till I can think of something else. BTW I also booted that SSD on an old test computer I have that has an old 2 port intel PRO 1000 NIC that also uses the IGB driver and it flapped then lights out as well.

I will try that, and see how it goes. If not, I can do it manually. /Jan

Hi ts1101, Good Day, Many thanks for the details again on this. I would agree with you with out any question. Prior unlocking, I could see its goes to BT Site for pay as you go subscription hence I don't want to take any chance i.e only by connecting lan2 port no phone line connected to it!. Some more setting pending with regards to WiFi access point need to keep them ready before hand. Will keep you updated. Thanks

furthermore if anyone has successfully negotiated this formidable task please feel free to enlighten this true nube with the details.