@johnnybe: @pfsparc: Today I did a reinstall of pfsense.. All went fine, until Snort was fired up, and the http inspection issue arose again. Suppressing it doesn't help. So for the time being '-1' helps, but will have to look into this more coming days. bdwyer says: Make sure you add your suppression list to the snort interface settings.  Change it from default to the list that has that rule. http://forum.pfsense.org/index.php/topic,43043.msg222725.html#msg222725 It works, as you can see here as well: http://forum.pfsense.org/index.php/topic,43606.msg225992.html#msg225992 Many thanks !! As the second link gave the real hint… adding the suppression list to the snort interface.

Yes I am running NanoBSD version. I see so it's like a backup version… that's very clever and I'm sure very useful in the event of problems or for testing. Thank you for clarification. :)

Apologies to all - did not intend a hijack Andrew

Presents the same message above and have worked with the steps for manual installation of pfsense in HD, but the problems persist, I think it should be the 32bit version. I did the test with 64bit.

follow instructions on this topic to fix it: http://forum.pfsense.org/index.php/topic,44224.msg229418.html#msg229418

Will check tomorrow - time to go home here

Problem resolved.  From my notes: To edit fstab on embedded flash: On separate machine, Boot into pfSense from the Live CD Do not select Recovery or Installation options, let the system boot until the menu appears Pick option 8 to drop into a pfsense shell prompt From the shell mount the CF which is likely /dev/da1s1a to /mnt Proceed to edit the /etc/fstab file to reflect the correct device ad0s1a NOTE: The fstab file indicates that the drive is to be mounted rw.  Is this correct?  Also, I think I killed the swap install onto the flash card by specifying 0 bytes for swap space size. SUCCESS!!  This process seems to have worked.  fsSense booted up fine.

That's exactly what I thought, 'DHCP comes before IP and TCP surely'. Wikipedia is never wrong!  ::) Steve

If you need to know what the default cron jobs are (if they were deleted or altered), they can be found in the default config located in /conf.default/config.xml on the firewall.

Thanks for the suggestion, but cycling the cable model did not do anything. This turned out to be a firewall issue, and I still don't know with certainty what caused it. On the old (1.2) firewall, I had a block rule on the WAN port for all traffic on top of the list. When I replicated this, I think it behaved the way it it is supposed to, i.e. it blocked everything on the WAN port. It does not appear that this rule behaved as expected on pfsense 1.2.

As long as you have adequately sized hardware for your connection speed, the difference in end to end latency between say a 500 MHz ALIX and a quad core Xeon server is trivial. The majority of the Internet will be 30-80 ms from you or more depending on your physical location, microsecond differences don't have any noticeable impact.

You can install ezjail package and create a jail with 8.1 release and install ports for example. Nat + firewall rules remains on pfsense.

Hi Bob, I'm with Virgin and mine is left blank so I'm not sure why yours did not work without it? If you have removed the default allow any rule then you need to allow DNS traffic from the interface subnet to the interface address else websites will not load. I don't know enough about networking to know why setting that hostname makes it work for you or which is the best way to use, perhaps I'm doing it wrong? hopefully someone more educated can comment? Regards.

Squid seems to work now. I added a firewall rule to the LAN tab for allow the LAN computers to connect to the squid port (in my case 800). I also modified the squid config, removing the LAN interface from the listbox named "Proxy interface" (you could multi-select elements on it pressing the CTRL key), saved it, and after I re-added the LAN interface another time. This was done if the configuration had bad information related with the interfaces and ip aliases With this now it's working for me.

@jimp: The mount command probably failed, it's saying it can't find /dev/da0s1a Because the slice is formatted with FAT32 there will be no a partition. It is probably the fsck that is failing because there is no FreeBSD a partition in a FAT32 slice.

Just an update to this. The Draytek Vigor 120 works perfectly. A quick reboot of PfSense and the WAN connection came up.

Figure it out. Needed to mount the filesystem as rw then I could edit.