You can also do that on-the-fly from a loader prompt without editing: https://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_with_an_alternate_console

@Technigogo: @jimp: umount -f /cf; fsck -t ufs -y /cf; mount -f -o rw /cf Jimp, is this safe to do over SSH from a LAN computer that I am RDP'd into? (I am not onsite) We have done that exact thing remotely several times with no ill effects, but there is always a chance it could go sideways so I can't say it's completely safe.

Yeah I posted on that topic earlier so will see what they come back with.

Want to report that I too have the same lock up issue, I have 3 Netgate SG-2440.  Also seeing the same issue where interrupts goes really high.  Based on when the devices lock up, I think it's dependent on the total number of packets that has gone through ipsec.  Once it hits some limit, the system becomes unresponsive. All three systems uses ipsec.  Two of the systems uses ipsec a lot and locks up after about a week.  One rarely uses ipsec and has only locked up once.

@johnpoz: I have been running pfsense on esxi for long time..  Yes if your bridge mode depending on your isp you should get dhcp.  I get dhcp via my cable connection. Just validate per the mac of the vnic in esxi that your connected to the right ones in pfsense. Thank you so much. i'll test it and get back to you.

the patch from https://redmine.pfsense.org/issues/6149 worked for me, but only after changing the uppercase HTTP_PROXY to lowercase http_proxy

it provides you a way to setup the vlans before you get to the gui.. and during setup.  It provides no "extra" features if that is what your asking. Say the way your network is setup you would need vlan to be able to get to pfsense, would be bad if you could not set them up until you could get to the gui, since you need vlan info to get to the gui, etc.

A better forum would be "Traffic Shaping" than "Installation and Upgrades".

Hmm, that is strange indeed.  Well, that one is above my pay grade.  Up to the devs now…

Just upgraded from version 2.1 to 2.3, somehow if I enable proxy, all the traffic will be directed to https, all my users cannot access a lot of the websites, and my users also could access ftp site eventhough I have opened the port on firewall on LAN port, otherwise all works fine.

Good lord the time I've wasted on this. I rebooted the jail and it started responding so I rebooted the server and everything is working now. Sorry for the stupid post, it was PEBCAK.

Your destination would normally be your WAN IP..  Since to be honest that is the ONLY IP it could ever be dest for.

As said on the other thread, I'd like to know if you had the chance to solve.

Hi guy, was wondering if you solved somehow. Cause actually I'm on the same path than you. Thanks in advance.

@Derelict: Get your config how you like it Reinstall fresh Connect laptop to LAN webgui at 192.168.1.1 kill the auto config (click the pfsense logo at the top) Restore the old config (modified for the new hardware) Auto-reboot and you're done. Reconnect to your modems, switches, etc. That is an exact description of my workflow. Several times with 2.2.6 and 2.3. Tried with and without changing the interfaces in the config and it just doesn't work. Tried a fresh install and manually configuring everything and it doesn't work. Tried a fresh install with nothing but a single port forward and it doesn't work. A port forward is so simple and should "just work" but for some reason it doesn't. ETA: Since this seems to be a new/different problem now I'm going to stop replying to this thread and move the discussion to this one.

@alphajoza: So what should I do? try to connect to server via LAN? I use host only adapter for the LAN interface and set its network to something like 192.168.249.0/24. Configure the pfSense LAN with 192.168.249.1 via console option 2 and then the host machine can access pfSense via it's LAN interface.

I have the same issue, I cannot upgrade to 2.3 from 2.2.6 nanobsd 4g 64bit. Same error message as well. "Something went wrong when trying to update the fstab entry" EDIT:I used the built in upgrade and that worked fine.

Diag>NanoBSD, enable permanent rw.

Don't you just love those "interesting" coding issues that collaborate to muck upo your network at will….. Glad you got it sorted out.