We had a similar problem with recent upgrade, same message.  We do not have fireware, tried disabling USB but no luck. After some research we came across this post: http://freebsd.1045724.n5.nabble.com/run-interrupt-driven-hooks-still-waiting-for-xpt-config-tp3925904p3925915.html that gave us the idea that some storage might not be responding to the pfsense kernel. Finally we figured out the problem, it was an faulty old CD/DVD Drive that no longer worked. Unplugging the drive solved our boot problem.

Hi again.  I think I have resolved the issue. I reinstalled 2.1.3 from a CD (previously i had used 2.2.2 memstick install) I then upgraded via the console to 2.2.2 which presented a problem with unbound not starting. following some advice here https://forum.pfsense.org/index.php?PHPSESSID=85j3ap423rg5mtrurrgslvvpc6&topic=92712.msg514140#msg514140 I downloaded the update patch locally and applied it to the system again via the web interface. I then restored my configuration and everything seems to be working so far. Not sure if somewhere along the process of first install there was some data corruption somewhere. Thank you guys for the assistance. [image: dashboard.png] [image: dashboard.png_thumb]

Ok, i tried again today, enabling the 2 boxes and it works fine on APU and Alix. So, I don't know why it didn't worked before, as i didn't change anything. Anyway, it works well, pfSense is a really great solution :)

there is sorta mac filtering but its a pain to manage ..  (see dhcp server –> static ARP)

More easier just copy the NanoBSD image to your USB stick, and import your config into that.

@Waldoman: @cmb: The upgrade didn't fully complete. Bring up the console, go to option 8, and run: chown -R root:wheel / Then reboot. It'll be fine after booting back up again. This worked, Thank you so much, been fighting with it. Thanks it works for me too Just don't forget to clean your browser cache before going into openvpn server ;)

Yes, you're pointing at the amd64 repo. It's safe. Steve

Thanks to all. I got it working now.  8)

@johnpoz: so your blocking only udp 443, that would explain why https works. perhaps.. as you can tell I know very little about this… but all I know is that at this point the issue I was having with Avast DNS is corrected  8)

Many thanks for the responses, this has helped me a lot. The Squid files - mainly the cache state was the primary issue.  These remained post uninstall of the package.  I think there might have been uninstall options to keep the cache etc ? I checked the Suricate logs and I think that at some point, the log trimming was not working correctly - even though theoretically the GUI showed trimming enabled.  I re-applied the settings and the logs for Suricate appear to be trimming properly now. Really appreciate the great help of forum members.

try to delete the cache and history then make sure you accept the unknown certificate also what version of chrome do you  have? Recently chrome been having issues especially with Hikvision addon

Hi all. I'm struggling with this. When I add the two lines I end up seeing the error Parse error: syntax error, unexpected 'else' (T_ELSE) in /etc/inc/unbound.inc on line 257 When I visit services->DNS Resolver. At this point the resolver will not start and I have to use the forwarder.  This is on the serial I386 2.2.2 install.

I already linked the bug. Do a clean install and move on. Really a no brainer with VMs.

"How do I fix this so DNS Resolver works and uses OpenDNS for name resolution?" Simple troubleshooting.  So can your client behind pfsense query opendns?  Can your clients behind pfsense query the roots?  Or any other name servers? What do you have the resolver listing on?  Are you really using the resolver or do you have it in forwarding mode?  Can pfsense?