The 6501 is very picky about which USB sticks it will boot from. Out of the half dozen or more I tried, only one would boot.

If you copy/paste the line from the BIOS detection that shows the drive, it would help to determine if it's a problem with the stick or not.

You can configure this path on squid package but usually it will be on /var(/squid)

To get a better performance, enable soft updates on this new partition.

If that's on CD, that's normal, and not fatal.

It's trying to read or probe the CD in some way that isn't possible while booting from CD.

On 2.0 that option can change the WAN IP as well.

You really shouldn't be starting out with 1.2.3 at this stage, 2.0 (and 2.0.1) have been out for many months.

Thank you!

Thanks a bunch jimp ;).
Cheers

Just import the files they give you into the Cert Manager. IIRC, If you made the CSR in the GUI, the CSR should still show up, you can press "e" to edit the CSR and input the result from your originating CA.

Solved by adding the kern.cam.boot_delay=10000 tricks….......
It would be nice if this is by default on, it doesn't really cause much extra time from booting but a few hours for ignorance like me to trouble-shoot ::)

It would interesting to know what they expect the network to look like.
Presumably they have done this many times before and have found this be the best setup.

I'd be interested in the opinion of someone with more experience on this.

Steve

It's because the default rule on the pfSense LAN interface that allows access to the web GUI only allows access from the LAN subnet.
If you are coming from a remote subnet routed via a VPN that will be blocked.
You need to add a rule on LAN to allow access from your remote subnet.
You should be able to so your routed access attempts being blocked in the firewall logs.

Steve

I recommend you use the NanoBSD install on a compact flash card in that box unless you have a good reason not to. For instance you need to have a HD install to have access to all available packages.
There is no HD image as far as I know.

Steve

All credit goes to the developers.  :)

Steve

thank you pal, have fixed it now:

You are on the latest version.

Tom

The underlying OS has no support for 11n, only will once we're on FreeBSD 9.x which will be 2.2, late this year. No way around it.

@burnsl:

Okay, so…  i REALLLLY HATE using auto proxy detection stuff, it is a needless delay at each browser start-up.

It's not needless if you want to secure https

squid + squidguard is a good option too but with transparent proxy it will filter only http.

If you want to filter web content, then you probably need dansguardian.

check performance with

squid
dansguardian
squid+squidguard

See what offers better performance and filtering options.

Check this Topic: http://forum.pfsense.org/index.php/topic,44637.0.html

I have manual edited the config.xml and pasted the old snortconfiguration within the tag <snortglobal>…
Then I restored this configuration in Diagnostics->Backup->Restore.
There is no option to choose "Snort" as restore area, so I have to choose "ALL".

After that system reboots and reinstalls all packages, the snort configuration is lost again.
That's where I started...  ??? ??? ???

Any ideas?</snortglobal>

Can you access the internet from the pfSense console?

Can you access the internet from LAN?

Is the WiFi bridged with LAN? If not, have you added a firewall rule for the WiFi interface to allow access to the Internet?

Sorry for this long delay. Being actually the one who posted this request, implies at least an update from me ;-)
I can confirm that modifying the above mentioned files did the trick! Everything running flawlessly! ( using a del r210 with a Broadcom card and an Intel I3 cpu)
Thanks so much for your help!
Regards
max
Italy