And what does pfsense have to do with your windows neighborhood hood browsing? Pfsense has nothing to do with machines talking to each other on the same segment.  Nothing!!!

:) [image: CQcH8pc.jpg] [image: CQcH8pc.jpg_thumb]

Run a cable, and directly connect it.. Or use a switch in front of pfsense if you don't want to run 2 wires.  I would run 2 wires ;) Or you can sniff the traffic from your set top box and see exactly what is going on, could be something with dhcp option and jumping vlans like a phone can do, etc.  But without understanding how its getting the public how do you expect to make it work behind pfsense?

dears is it working as same as configuration bbut with squid non transparent ??

@doktornotor: Look at the Cache/Proxy subforum and see for yourself. So is there a less "shitty" way to do content filtering??

Have you tried disabling the COMMS port?

Nope, it is not yet fixed in 2.2.2 as this is the version I am on. I have taken your advise and yes, it is booting up fast and furious. I do not need my comms port on this machine so will leave it disabled. Thank you for pointing me in the right direction.

I was looking at going to a Kingston 8Gb - it will do USB3, but only in a USB2 port http://www.kingston.com/datasheets/DTSE9g2_en.pdf It talks about a 5 year life?

Update: Tested and working on m0n0wall 1.8.1, 1.34, 1.33 to pfSense 2.2.2 + 2.1 NanoBSD

Hi, I was coming from the previous version (my pfsense box is only 2 months old).  Hardware is a lenovo desktop, new with an intel 4port nic.  I selected to perform a full backup prior to the upgrade. Thanks,

Yes, it seems this can still happen. When it does though the dashboard will show the pfSense version as 2.2.2 but the FreeBSD version as 8.3 still. That should never happen obviously. Rebooting manually will fix that. Steve

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.