Thank you. I still don't understand where 172.x.x.x (private IP) is coming from? as it was set to default, why default is not picking up WAN IP? I've left Gateway as dynamic (it still displays 172.x.x.x address), but I've added Monitor IP 8.8.8.8 (Google DNS). I'm not sure if this is correct, but I can see now correct status in Status>Gateways

Probably some power saving feature that SD doesn't do.

@jimp I upgraded from 2.4.3_1 -> 2.4.4_1 and this time I had no issues. Thanks for the support and great product!

Thanks

Hi, Nuke the raid stuff - visit BIOS if needed. Btw : nuking means re reinstalling ... take config backups

In the end nothing helped but reinstalling. I was naturally afraid of doing so but it turned out: It was fast (with the exception of getting the image in the first place) and worked beautifully. So thanks for the assistance!

@ronpfs said in Restore config doesn't change Syslog Log file size on disk: But do I have to visit all tabs and sub tabs to figure out what I need to pay attention to when restoring to a new installation? Keep a good documentation of the changes you made. And yes, verifying your setup after a config restore is important and pretty much a standard procedure.

Thanks for all the help. Since client is a 24/7 operation I'm going to suggest they replace this old unit with an SG-3300. Then we'll try the reinstall on the old unit and save it as a backup.

Thanks for the reply. Mainly to separate the traffic on the first pfSense. That one currently runs at about 35% to 55% cpu. Eventually that server will be upgraded. The thought is the 2nd pfSense at that location will be used exclusively for the VPN access. If the VPN access begins to affect the traffic through the main pfSense server, I'll just cut the site2site access out of the picture. I have limited bandwidth available (400/25) so the site2site is a nice to have to eliminate running to the building when something goes bonkers there. I may try enabling the site2site on the 1st server and see what happens. Is it possible to run site2site and road-warrior on the same pFsense server. Needless to say, because I had been relying on RDS for the past few years, I'm a noob on the VPN side of things.

It doesn't matter how many you have, one should be set to default. Either directly or by using a gateway group as the default. There is an open bug report about a gateway group as default not working for everyone, though, perhaps your setup is one of the affected ones. As long as you have a default route showing under Diagnostics > Routes you should be fine.

The advice you were given was pragmatic and meant to get you back up & running quickly, which is usually desirable when your net access is downor your config seems irreparably broken.. If you're really that upset then simply ask for a refund and move on, but I've worked with other firewalls in the past and I've had upgrade problems with ALL of them at one time or another. At least pfSense isn't a black box and you can poke around and make changes that might fix whatever issue you have. Try doing that on most other firewall appliances. I upgraded a Mikrotik 6 months ago and it blew away ALL of my configuration, including a complex QoS config. That's not to say that the 2.4.4 upgrade could have gone a little smoother, but that nothing is perfect. If you have a problem that can be reproduced then log it to redmine and they will fix it.

New location/client, I'm gathering information and assessing here. I'm sorry you are being a jerk here about this. You really are haha. I'm expressing my opinion on the interface saying all is fine and up to date. If it were under my management it wouldn't be this long before it was checked into. Again thanks for leading me to the information I needed.

Ah, looks like this was discussed a few months back: https://forum.netgate.com/topic/135395/where-to-download-old-versions/7 Intentionally removed because they are insecure, and we should maintain downloaded copies if we want them.

Check this : What ? Google doesn't accept MITM anymore ?

Thanks, yes I know it will be double NAT'ed but it should only be for a short time. I was going to set it up before hand and just swap it out but need internet to download packages and I think the setup to the WAN is not going to be easy as it needs a PPoE connection and also a VLAN10 so want to have the rest of the setup done before I need to sort out this part. I may be surprised and the WAN connection goes great but if it doesn't and takes a while then the rest of the house/servers is without internet connection for longer.

@kendalja tried your way but unable to install ssme error efi framebuffer

@zander7990 said in Can't reach internet: but my laptop can't reach the internet or ping my Nas. Where is your NAS? You have given us nothing to work with here.. Other than its broke.. Is your wan public or private IP on pfsense... What is your lan network.. Assume you left it default - does it overlap with your wan network? How are you managing pfsense - through your VM console? Lets start with basics... Install to bare metal.. Can you get to the pfsense webgui? Lets get that far and then see where your going wrong... I can tell you for sure removing rules off your lan isn't going to fix anything..