Config should be in /cf/conf/config.xml afaik. In  /cf/conf/backup are all the old versions. Hope you can save some of it.

@Snailkhan: bump .. what about 2.3 and the little updates that always show up in update check ? can we just initate update and close browsers ? yes

Thanks, I'll give this a go.

Exactly, - Choice is a good thing tho - A fully authenticated session via the modem as on DOCSIS is useful - unpiug the router plug in something else - and if you've ever had problems with Comcast connections you'll appreciate this ability. I just find it very odd that for the UK and UK alone your product gets downgraded without your consent. And, on pf 2.3.1. there was no PPPoE/A working so if you have a UK V130 re-flash to earlier FW and it will connect. I bought what I believed was single port modem with built in authentication. It has many uses - router goes tits up an you've still got a connection - router goes tits up with dumb modem and your screwed till you fix or replace it Anyways, some my find the info useful

Now I suceed. After give it another try, I could update and my tunnels are still working. I had to edit and save them new to get them online.

still have the same Problem. Fresh Install on APU1D4 Board

I would: a) Save the config b) Set to factory defaults (so you get DHCP on WAN) c) Plug the WAN into an ordinary LAN (e.g. plain old office LAN at work) that gives out DHCP Now the unit has internet. d) Do the online upgrade e) Restore the config

Update: We've been good all day today.  So for me, deleting squid, reinstalling, chown worked.

@Derelict: Try 192.168.0.0 with a /16 netmask not 192.168 Thanks, working now.

@ThePooperScooper: Whats a normal amount of processes to have requesting it? Right know, Mine reads "Read/Write (reference count 6)". I've been having problems with write speeds to the CF card I have and have been trying to figure out whats causing this. I have it in forced Read/Write mode. Would having 6 processes requesting privileges be something to be concerned about and mite be causing the slow write times? That would be odd to have 6 things that are currently needing RW and are doing their thing (updating the config, writing conf files, whatever). Most likely some processes have done the mount RW and somehow failed to a matching mount RO call on their way out. As cmb says, go to 2.3.1 and RO is no more.

@JorgeOliveira: Now try booting the system with the following commands: set hint.ata.0.disabled=1 set hint.ata.1.disabled=1 boot -v Then add to /boot/device.hints: hint.ata.0.disabled="1" hint.ata.1.disabled="1" Hopefully, it does work now. (In addition to the link on my previous post, also found that at: https://superuser.com/questions/1055316/why-does-disabling-ata-fixes-run-interrupt-driven-hooks-still-waiting-after-60) didn't work for me… but thanks anyway. confirmed with my datacenter support, they are running QEMU with IP KVM for managing console through user portal

That's exactly what I did. I noticed it installing all of the non-kernel/non-OS packages at that point. Back in the <= 2.2 days, it seemed to do all that in the background with that animated hard drive image. At least then, the router was up and routing packets while doing so.

I could not find the right image. Contacted support and they gave me the right image. Made an usb and re-installed the unit. Load backup config. Done =) Thanks for great support =)

Hello all, FYI: I have disabled Growl notifications and also the IP address field is blank. No issue any more. Thanks for your help.

That was the issue! We're using LDAP groups for access, and the permission was added to these groups.

I did some tests of reset to factory defaults using the reset button on an Alix 2D13: (a) Power on, wait 5 seconds, press reset button for 10 seconds, release (b) Power on, wait until console is showing the FreeBSD booting stuff, press reset button for 10 seconds, release Power on, wait until console is showing the pfSense booting stuff, press reset button for 10 seconds, release before/immediately you see "Launching the init system" (d) Power on, wait until console is showing "Launching the init system", press reset button until "Reset button pressed" message is displayed, release (e) Power on, wait a bit (5 to 60 seconds - no panic), while the left green LED is steady press the reset button, hold it until the 3 LEDs have been cycling a couple of seconds, release (a) (b) and (c) do NOT result in a reset to factory defaults. (d) and (e) DO result in a reset to factory defaults. If you can see the console output, then (d) is a useful guide. If you cannot see the console output (most likely scenario if you are needing to use the reset button), then (e) will guide you successfully. Note that it is 90 to 120 seconds from power on until the 3 LEDs start cycling, so there is no rush to get the reset button held in immediately you apply power.

Expected. You won't actually go to 2.3.2 if you're set to stable. https://lists.pfsense.org/pipermail/list/2016-May/009934.html

Ctrl + F5?

one more thing: I was very happy to do the upgrae remotley, b/c the two if with syntax error were LAN if and my remote access via VPN was luckily still working. So I was able to fix it easily ! Thanks!

pfSense 2.2.* is based on FreeBSD 10.1 pfSense 2.3.* is based on FreeBSD 10.3 So anything that happened for FreeBSD 10.2 and then 10.3 in regard to drivers etc would have the possibility to trigger different behaviour.