Thank you so much!

Ok. See my reply on your other thread for disabling that. Steve

Clarification: The LAN is a routed, isolated subnet ==> WAN is private network ==> Edge router ==> internet

Thanks ChrisMacMahon... currently we plan just to renew all drives as caution measure... does the FreeBSD of PFsense 2.4.4 support SSD trimming? Thanks! Pedreter.

ppc0: cannot reserve I/O port range That's a very common warning shown on many if not most systems. It's not an indication of a problem. It sounds like you may be describing the problem with unsupported sdhci issue some boards have. Like this for example: https://forum.netgate.com/post/752747 You can interrupt the boot loader and set those at the loader prompt even on the installer if required. Steve

Wow! That did the trick. Thank you very much!

Is the terminal set to 115200bps? If it's set to 9600 or 38400 then that would be all you would see. Otherwise yes you can always re-install: https://docs.netgate.com/pfsense/en/latest/solutions/vk-t40e/reinstall-pfsense.html That will ensure you have a clean install. It's quick and easy if you have an mSATA drive. If you are booting from SD card you can install directly to it but you should remove the swap partition at install and move /var and /tmp to RAM after setup. It doesn't look like you were running Nano though so it's probably not booting SD. Steve

found a solution which seems to work reliable. As the ethernet USB adapter is on USB3 it seems to need more time during boot to be available to pfsense. I've installed the ShellCmd Package and added a earlyshellcmd with sleep 25 code. After loading the configuration pfesense waits for 25 second to have the usb network adapter initialised and the continiues with boot up. After several reboot this seems to fix the problem.

I ran into the same issue after upgrading to 2.4.4 and at least for my issue it was related to having multiple gateways setup. I edited /etc/inc/gwlb.inc as recommended and it fixed the issue for me "https://redmine.pfsense.org/issues/9004"

Never know now.... doing some work with BBCAN177 and needed a reboot. Now the Backup Files/Dir is working.

Hmm, interesting. A number of systems had the opposite problem there, the legacy console did not boot. I suspect that might be an early UEFI BIOS then with some.... quirks! Steve

@gertjan said in Retrying pfSense: @randomaustralian said in Retrying pfSense: Has anyone got a working Telstra configuration with just IPv4 or also IPv6 on their pfSense box? Hi, Your lucky day : read this. To confirm. the thread you linked provided the required information and i have no idea how the guy who worked it out came up with said information.

That entirely depends on what your DC built for you. It sounds like you might need to answer 'yes' to setup VLANs and then add VLAN ID 221 with igb0 as the parent, and then assign that as WAN, using an IP address from your subnet, with the correct mask, and then set the ISP gateway they gave you as the gateway.

Just wanted to report that issue was resolved. The sha256sum hash of the iso.gz file was reported correctly however I discovered the files hadn't been extracted correctly when unzipped. My only suggestion would be to list a sha256sum hash of the actual iso file in addition to the iso.gz file. Thanks.

Below is the working route/gateway table. Firewall rules used to push traffic to VPN Internet: Destination Gateway Flags Netif Expire default 192.168.0.1 UGS em0 1.1.1.1 10.156.0.29 UGHS ovpnc3 9.9.9.9 10.156.0.29 UGHS ovpnc3 10.156.0.29 link#9 UH ovpnc3 10.156.0.30 link#9 UHS lo0 46.182.19.48 192.168.0.1 UGHS em0 81.3.27.54 192.168.0.1 UGHS em0 91.xx.xx.xx 10.156.0.29 UGHS ovpnc3 127.0.0.1 link#6 UH lo0 192.168.0.0/24 link#1 U em0 192.168.0.234 link#1 UHS lo0 192.168.20.0/24 link#2 U em1 192.168.20.5 link#2 UHS lo0 192.168.21.0/24 link#4 U em3 192.168.21.5 link#4 UHS lo0 Table from where is does not work. Internet: Destination Gateway Flags Netif Expire default 192.168.0.1 UGS em0 1.0.0.1 10.149.0.13 UGHS ovpnc1 1.1.1.1 10.156.0.29 UGHS ovpnc3 9.9.9.9 10.156.0.29 UGHS ovpnc3 9.9.9.10 10.149.0.13 UGHS ovpnc1 10.149.0.13 link#10 UH ovpnc1 10.149.0.14 link#10 UHS lo0 10.156.0.29 link#9 UH ovpnc3 10.156.0.30 link#9 UHS lo0 46.182.19.48 192.168.0.1 UGHS em0 81.3.27.54 192.168.0.1 UGHS em0 85.xx.xx.xx 10.149.0.13 UGHS ovpnc1 91.xx.xx.xx 10.156.0.29 UGHS ovpnc3 127.0.0.1 link#6 UH lo0 192.168.0.0/24 link#1 U em0 192.168.0.234 link#1 UHS lo0 192.168.20.0/24 link#2 U em1 192.168.20.5 link#2 UHS lo0 192.168.21.0/24 link#4 U em3 192.168.21.5 link#4 UHS lo0 This is the traceroute (which works) from when both VPNs are up. traceroute to mintlinux.mirror.wearetriple.com (93.187.10.106), 30 hops max, 60 byte packets 1 10.156.0.1 (10.156.0.1) 30.850 ms * 30.785 ms 2 * v741.ce01.ams-01.nl.leaseweb.net (37.48.118.60) 30.738 ms * 3 * ae-5.cr01.ams-01.nl.leaseweb.net (81.17.33.128) 30.667 ms * 4 be-111.bb03.ams-01.leaseweb.net (31.31.38.200) 30.622 ms * be-112.bb03.ams-01.leaseweb.net (31.31.38.204) 30.578 ms 5 * triple-it.telecity2.nl-ix.net (193.239.116.57) 37.565 ms * 6 mirror.wearetriple.com (93.187.10.106) 37.501 ms 25.516 ms * however, this is the error from the linux package manager and as i say, on the whole http browsing works. Failed to fetch http://mintlinux.mirror.wearetriple.com/packages/dists/tessa/InRelease Cannot initiate the connection to mintlinux.mirror.wearetriple.com:80 (2a00:1f00:dc06:10::106). - connect (101: Network is unreachable) Could not connect to mintlinux.mirror.wearetriple.com:80 (93.187.10.106), connection timed you can see it is resolving in the application error message, so i don't think it is a dns issue. If i shutdown either of the VPN clients, this will work.

Ah, great. Coming from 2.3.4 or earlier can be a bit sketchy. There are several repo and upgrade package updates that need to apply before you see the 2.4.X updates. Glad you were able to resolve it. Steve

@zdevlor said in Unable to install packages looks like certificate error: how do i do that with no access to the repo With no access, this file pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or director can't be loaded, so it can't be found. A WAN connection need to exist to update/upgrade.