Yup that is BORKED ;) That is the official technical term btw ;)

The ntp status of the fresh pfsense 2.2.4-p3 as opposed to the screenshot above which is from a pfsense 2.4.4-p2 to pfsense 2.4.4-p3 upgrade. That system had run for about 2-3 years with only one time sync issue before the upgrade. The ntp service was disabled before the upgrade.

newinstall-hdd-ntp-screenshot.png

I am STILL trying to determine whether this is a faulty RTC timer on the motherboard or not. Dell BIOS diagnosis says everything is good and the system seems to be holding it's BIOS time with the new battery installed.

I am going to run this fresh install/new SSD for a week or so and see if it also gets the time sync issue - if I understand it correctly it may not show itself for a few days to a week?

@jimp Thanks for the help! Opened up a ticket and had a response within 10 minutes. SG-88601U back to running 2.44p3 again. No problems whatsoever.

Thanks again for the fabulous support and great product!

Jeff

Well had a poke around could not see anything that could of helped, so i just loaded the default settings and now it works, i have no idea what settings it could be but i am not going to touch it, thanks for your help guys!

There is a huge difference between expired and "revoked" that error is NONSENSE if the issue is that lifetime is too long with the new 13 month limits that are going to be used.

Ah, nice catch!

Hmm, the addition if the bridge makes no sense there at all IMO. I would certainly not do that, you should be able to just route between the two subnets of you need access to the modem.

I think we dealt with this via a support ticket but if not you should open one.

Steve

@GregTheHun said in ZFS Setup with four drives, with different mount points?:

@GregTheHun said in ZFS Setup with four drives, with different mount points?:

Hi all,

I had already sent this in the installation section, but I'm moving to here to see if this is a better spot to ask my question.

I was wondering if there was any possible way when installing pfSense if you could install pfSense with four hard drives in total. My plan was to split the work between two SSDs in a Raid-Z Mirror, that way they're redundant.

Ideally, the layout would look something like:

ZFS:

OS Mirror 2 SSD Drives Write-heavy areas Stripe 2 SAS Drives

I could also be doing things completely backwards and if you have any other suggestions. I'd love to hear. Ideally any scenario that's possible would use all four drives.

Thanks all!

Anyone?

Sorry to bump, but here it is

Yeah it was the usb, i now have it installed, thanks for your help

If the pfSense isn't getting a DHCP IP from it then it likely isn't, and you'd have to enter a static IP address that is in the NetGear's subnet, with the NetGear as its gateway.

@serbus said in WAN stop accepting traffic when LAN port disconnected:

obscure

That is pointless. It does nothing other than make your setup more complex and more likely to make mistakes and be less secure.

Well that seemed to be what people were suggesting in Google's forum. Nothing definitive.
You can disable it behind pfSense but otherwise I'm not sure how you might disable it in Android globally. I imagine you can find a wifi location without IPv6 though.

Try setting up the VPN for just you local subnet rather than all traffic and see if you still see issues.
I can imagine both local connections and the VPN are trying to be the default route. Usually OpenVPN just set's itself and there's no problem though.

Steve

Never would have picked that up ! Thx for heads up ... this is gong to be lots of fun ..

up and running.
Thanks a lot!

@goodthings said in fatal error - cannot restore 2.4.2 backup in 2.4.4:

Unfortunately I don't have portal access.

In an act of pure desperation I searched github for the function "function upgrade_174_to_175()" and found that it relates to ipsec phase1.

The (non-functional) 2.4.2 config looked like this:

<ipsec> <phase1></phase1> <logging> [...] </logging> </ipsec>

I compared it to other configs and manually deleted the empty "phase 1" element. The configuration upgraded successfully.

<ipsec> <logging> [...] </logging> </ipsec>

That was a bit of a nightmare. ☹

Thanks for this bit of information. I was reinstalling from a rather old configuration file and my XML file just had a <phase1 /> line. After removing that the configuration installed properly.

Without removing that my dashboard was extremely slow to load and my NIC assignments would not persist on reboot.

@edz it's not :)
It's a VMware Fusion virtual machine.
Much easier to do testing on VMs where you can do snapshots, and have better performance.

Sorry for late reply. I got it fixed by installing on an HDD and putting that HDD into the System. Then booting it and it worked.

Upgraded to 1343 with pfblocker-ng installed, no problem here.