Ok, thank you.

Suggestion: Try adding the line kern.cam.boot_delay="20000" to the pfSense file /boot/loader.conf.local (create the file if it doesn't already exist). This will delay the startup a bit before trying to access file systems. You might need to tweak the number a bit to make it big enough but not "too big".

Thank you very much! Regards Kostas

Sort of feasible: if you have modem in routing mode, then it's feasible -or- you have modem at bridging mode and you have not done all the virtual ip's for the pfsense -or- you have every single wan ip set, but manual outbound nat rules isn't set right

@GruensFroeschli: Update your (tiny)BIOS to 0.99h You can download the needed files here: http://pcengines.ch/alix2.htm Thank you a lot GruensFroeschli. Now, with the 0.99h bios, it works!!! Thank you again!!! :) Luca

To the original poster, just to be clear: You have added a route on the Cisco router to the pfSense box and a route on the pfSense box to the Cisco router's subnet and all have the correct metrics and other options specified for the two different entries on the two different devices? Just checking… Take the best and leave the rest. Jon

http://doc.pfsense.org/index.php/HOWTO_Install_pfSense#Embedded_.28Compact_Flash.29_Installation

Or maybe sticky the instructions.  ;D

Other clients in the same subnet are working? You have set the WAN interface is setup correctly? Steve

Yes you don't have to worry about the limited write cycles of your CF card (within reason) when you're using the NanoBSD image. It is specifically designed to avoid this. You don't have to worry about performance either since everything runs from ram. In fact the CF card is very slow compared to a HD since it doesn't use DMA. I believe that if you are using the squid package on a NanoBSD image it too runs it's cache only from ram (or it could be setup as non-caching I can't remember.  ::)) Having said all that there are some threads about running your Squid cache and logging on a separate HD if your search the forum. Steve Edit: Like here for instance: http://forum.pfsense.org/index.php/topic,36724.0.html

Thanks Steve. I downloaded the correct image you mentioned and then used the win32diskimager and that worked. Thanks a lot!

Backup your data, the drive is likely dying. You can also check Diagnostics > SMART Status If it were random LBAs/offsets, I might be inclined to say it could be a driver/cable/controller issue, but to see the same LBA/offset over and over screams "dying disk".

All unmanaged swithces is automatically layer 2 devices. if you have managed switch it doesn't mean that it's L3 device, only if it's routing switch(can do inter-vlan operations without external router/firewall), then you can mention it to be L3 switch. 1. All the trafic what goes in one vlan don't (usually, there is special occasions) go through firewall 2. All the trafic what goes from vlan to vlan go through firewall, unless you have L3 switch doing that for you 3. All the trafic what goes to internet goes through gateway device, that is usually firewall.(same applies to point 2) Is there anything what need clarification?

Tried this morning and got in. Looks like it was a bad password. One thing I know for sure (may be) I was using the same one as for GUI. Go figure :-. Thanks anyways. I was getting this error - sshd[29368]: error: PAM: authentication error for admin from xxx.xxx…

Oh thanks, I'll look into that also!

It is a glitch that hasn't been addressed yet.  http://forum.pfsense.org/index.php/topic,40428.0.html  I have also had that problem on the re-syncing of the packages.  What you end up having to do is "clear the package install bit" under backup/restore.  Then manually reinstall each of the packages after recovering your setup without the package information attached in the xml file. 1. Clear package bit 2. backup configuration (omitting package info) 3. reinstall packages

Oh!!! Thanks anyway

Yes. Only difference is size. That is covered in the doc wiki, as it's an FAQ.