@tsmalmbe: Hello all, I have tried to upgrade my nano-installation from 2.2.5 to latest 3.2.x without success. The upgrade stops (gets stuck for at least 10 minutes - haven't waited longer) at a message "RRD update WANGWXXXX" (or alike, do not remember exactly because the machine I'm running teraterm on does not have internet connectivity). To even get this far in the upgrade, I have deleted all RRD data and disabled RRD completely on my 2.2.5 (I had my disk fill up with RRD before doing this). I then assumed I wuold have no more problems with RRD - but even after disabling it seems that RRD data for LANGWxxxx and WANGWxxx is being created and now the WANGWxxx RRD data is causing me this problem. Is there a workaround or what am I doing wrong? Same thing happened to me when going 2.2.6 to 2.3.1. Very disappointing that you cannot do a regular ('vanilla' install, no mods or changes) upgrade without major hassle.

If you have the firewall disabled you sure and the hell are not forwarding anything because your not doing nat.. What are you wanting to forward too if you only have 1 interface? How about you draw up your network are they both rfc1918?, showing your networks on the wan and lan side.  Install pfsense clean don't freaking disable the firewall or nat and then its click click for a forward.  If does not work then see the above troubleshooting guide for where you made a mistake. I can tell from being on this forum for many many years that forward issues are 99.99999% of the time PEBKAC or that the traffic is just not even getting to pfsense for it to forward in the first place.  Which if port 80, yeah many an ISP block that inbound. [image: disablefirewall.jpg] [image: disablefirewall.jpg_thumb]

THANK YOU!!! I had the same problem and this fixed it for me.

well pfsense is not using the resolver (itself) its using google.  You sure you have the resolve enabled.  Your client did not get refused or servfail it got a timeout, like pfsense isn't even listening on 53??  Or maybe your connection upstream of pfsense blocks you from resolving??  Your isp blocking or intercepting dns to other than major players? Notice how mine comes back that it asked itself 127.0.0.1, why is your using google?  If using resolver mode the only dns listed in pfsense should be loopback. Even if pfsense couldn't do upstream queries it should come back with its own name.. blsljdsf.sjlfjdsfldsfdf.sljfdsldjfs Server:  pfSense.local.lan Address:  192.168.9.253 *** pfSense.local.lan can't find blsljdsf.sjlfjdsfldsfdf.sljfdsldjfs: Non-existent domain [image: pfsensedns.jpg] [image: pfsensedns.jpg_thumb]

@danioj: @jimp: You can see the servers in /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf But don't edit that file. Instead, make a host override in your resolver/forwarder (whichever you're using) to resolve pkg.pfsense.org to 162.208.119.39 (or whatever it resolves to for you on a system with connectivity. Hardcoding addresses like that is dangerous, however, as we could move that to another IP address at any time. i can't believe i didn't think of that myself. thanks very much. appreciate it. worked like a charm. for anyone else wanting to do the same thing and stumbles on this post, this is how it is done: assuming host is pkg.pfsense.org and that resolves to 162.208.119.39 services>dns forwarder>host overrides>add host = pkg domain = pfsense.org ip address = 162.208.119.39 description = pfsense updater override save apply :) 8)

I figured it out, my vmware networking was all messed up. I had to rebuild the esxi server and that resolved the issue. Thanks for the multiple ideas and all the assistance, greatly appreciated!

Wow what an old thread. Disclaimer: I have no idea how valid any of what I'm about to say is.  It is mostly just based on my limited observation and even more limited knowledge of the subject. It may be utter nonsense. I've been running full install pfSense on USB flash drives for a number of years.  With RAM disk enabled, and backup schedule for RRD at 9 hours, and DHCP leases 7 hours. The USB flash drives seem to last about a year before starting to go bad. They seem to start exhibiting file corruption.  Though one went sudden total failure (probably a critical block went bad).  Inaccessible/Undetectable.  Could even detect and use it in a PC. Not sure if the wear-leveling of USB flash drives is effective and able to detect and mark bad blocks within the active file system. Two possibility mitigation techniques. When a file is noticed to be corrupted.  Don't delete it or edit it.  Rename it.  Then restore a good copy of the file.  This may keep the bad blocks out of service so they don't become available for other write cycles. Re-install to recreate the file system from scratch so the bad blocks can maybe be detected and marked. Bare minimum fail safe:  Have handy, 1) installation media, 2) a good USB flash drive, 3) recent config backup.

That's what I'm saying also.

It's a good question. All I've got access to is the CLI so I think I'm good using those IP ranges, certainly it's never been an issue when I've installed on VMWare but if there is a command I can use to be sure and/or test this I'll happily give it a go!!

That did the trick! Thank you for your support.

another update: I loaded the config from the site that worked fine and this is what came up with VERY little delay. Waiting for Internet connection to update pkg metadata and finish package reinstallationUpdating pfSense-core repository catalogue… repository pfSense-core has no meta file, using default settings Unable to update repository pfSense-core Updating pfSense repository catalogue... repository pfSense has no meta file, using default settings Unable to update repository pfSense ERROR!!! An error occurred on pkg execution (rc = 70) with parameters 'update -f': pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-core/meta.txz: No address record pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-core/packagesite.txz: No address record pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-pfSense_factory-v2_3_2/meta.txz: No address record pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-pfSense_factory-v2_3_2/packagesite.txz: No address record It does that 3 times and then this ERROR: Error trying to get packages list. Aborting... pkg: Repository pfSense-core missing. 'pkg update' required pkg: Unable to open remote repository catalogues. Try running 'pkg update' first. All within a span of less then a minute.  Any thoughts as to why this config works and the other one stalls for a couple hours would be helpful.

Thanks

Okay. Should I file a bug for hiding the Etc zones from pfSense?

Same problem as mine! https://forum.pfsense.org/index.php?topic=118177.0 Some monitors are ok, some not, and it's simply not booting if there are no monitor connected.

This could be caused by any number of dozens of reasons. The information you've given is pretty much the bare bones of what anyone would need to work out the cause. And you haven't said what version of PFS you're installing either (32-bit or 64-bit), or whether your old desktop machine is a 32-bit or 64-bit machine. So I will repeat my previous question and ask if you're booting with the correct version of pfSense for your hardware? If you're trying to install a 64-bit version of software on a 32-bit machine, your installation will hang in just such a way as you describe. Please fully read any questions you get in response to your problem and try to answer them - otherwise you may as well just ignore what's being asked and try sorting things out yourself.

I have the same problem My mbo is Via Epia and i did try to install to ide HDD no way . Different Stick didnt help , on my laptop it goes but i get a different eror . What you can try is go to bios on the hdd you are using ad disable smart and dma set all to manual and hdd typ from auto to LBA. Maybe that will help .

Read over the upgrade guide and the release notes for both 2.2 and 2.3, more likely than not, you need to make some adjust to your captive portal HTML code.

Agreed this is pointless..  Run it on a vm, run it on their little cloudkey, run it in the cloud..  Just no point to messing with the pfsense install to try and get this to run.  If you could get signoff from the developers that this would be fine then ok.. Now that they have really dropped support or suggestion that you run a wifi card in pfsense you can not longer purchase from their store appliances with wifi cards added and they suggest external AP maybe they would think about doing such a thing.. But I wouldn't hold my breath ;) If you want to run multiple things on 1 piece of hardware - then run VM…  I run pfsense on my esxi host, and then I have another vm for my controller, have another for my nas ;)  Which is the other thing people want to run on pfsense..

@Gertjan: I had some spare time yesterday, so I decide to repair my crystal ball. Your question was just great to test it afterwards. This is what I saw : The issue is what your cameras is "seeing". Snort is a "packet inspection system" and the new version that came with 2.3.2 doesn't like what your camera 'sees'. Snort kicks in and filters it out. So : tell snort that your camera is trusted. Can you confirm that my crystal ball is repaired ? Thanks for fixing and dusting off your crystal ball. Yes it seems to be related to SNORT, if its uninstalled prior to upgrade the remote camera continues to stream to my local recorder. I did add a alias of the remote internet IP number and then I added it to snorts "pass list" prior to removal. I did a little "light" reading (too alleviate my noobness) on how to filter logs.  ::) but my "remote" ip never shows up in logs. I reinstalled SNORT and my setting reappeared and my cameras are working still, post upgrade/package reinstall . puzzling. Another way I think of this is, that I am doing a download of a file from a internet server at 2.5mbps all day long to a local computer. If things change I will update. But look like its working.