The settings under diag>nanobsd all seem right, the correct partition is selected.. it all appears fine.

It should noted this is an ancient CF install on a watchguard x700, being upgraded, modified, hacked,
countless times over the years, there is no question about it, this is no doubt my own fuckup somewhere.
You know the drill, its buried in the rack, and its always just 'easier' to hack than fix. If it works (TM), and all that.

The only reason the problem has come to my mind recently is an (non IT gear related, all RCCB) RCD issue that
has caused some semi-infrequent, yet very annoying power drops (ups can only last that long, and cant
afford diesel or independent power.. electrician has been called, its the 3rd time trying to find this @*!# fault).
Thus I'm giving up; and making the network fully autonomous, so it can pull itself from cold->operational by itself.

Nevermind, the only sensible approach to all this is to use this brilliant excuse to do what I've should have done
some time ago; do a clean install, and perhaps use this opportunity to move my ass to pfSense 2.0..

Thanks, your reply finally put some sense in me :)
MeatPuppet

Hi,

to silence the log messages in the future is certainly correct.
I´m not worried about these log messages, but how I get my RRD graph working now?
What can be done on my side?

Tobi

md == memory disk. Some big packages use too much space in the md-mounted partitions, you just can't install those on embedded. Why you would want a file server on your firewall at all, much less one running from CF, is beyond me. Don't do it.

You do not need to change the root password. The root password is the admin password you setup in the GUI.
As far as starter Tips go…

You can track bandwidth usage with iftop or in the GUI under status->traffic graph

To reduce lag get top notch gig NICs. The cheap stuff has always caused problems

You can track overall bandwidth usage with the RRD graphs.

To have DNS working completely have DHCP register DNS entries under Services->DNS forwarder

Port forwarding is completely different than IPcop. Start your port forward entries in Firewall->NAT

The final tip I have is to check the forums. Everything you need to know about gaming with pfsense and problems you may run into are documented within the forum and the wiki.
Also dump your ISP. Find an ISP that doesn't limit your usage. You're paying for it so why should you pay more for your bandwidth.

I went through the installation
I have a strange problem
I can not access the web interface from a PC with Linux

Is there a way to set up the router quickly

There's lots and lots of settings

is there an option to access the web interface from the computer the pfsense is install on

Me very stupid at times!!  Found it and fixed in 10 seconds after I posted.

Sorry!!

@Summer:

is it possible to install pfsense on a machine  and then move the disk with pfsense installed to another machine that hasn't the same architecture?

I have done this a couple of times.  think jimp has covered all the issue I had.

Odds are the search list isn't in the right format, there is a recent ticket for that. Clear out the search list and see if it works.

To help anyone else who has this problem, I think it was down to the firewall rules somehow going.  I might have somehow deleted them when I was editing the config file.

that is possible, but problem could reside almost everywhere

Will do.

Many thanks

I re-installed, this time using the default kernel rather than the embedded kernel.  Everything works fine.  The webgui comes right up.

The embedded kernel and my hardware dont seem to get along.

pfSense automatically listens for connections to the settings page from all interfaces, but only opens the firewall by default on the LAN interface (you can disable the "anti-lockout" rule in settings, but be careful). If you wanted to access the settings page from the WAN, for example, just add a rule to the WAN to allow access from anywhere to the WAN IP address, protocol HTTPS (port 443) TCP, and you will be able to access it remotely. Same is true of any other interface, add a similar rule for access to the interface IP, from any or specific IPs as desired. Or, add explicit block rules if you want to or if you've opened it up with other rules. I also tend to change the listening port to something other than 443 so I don't interfere with port-forwarding of HTTPS and am on a non-standard port (less likely to be target of random scans from Internet or guesses internally).

Well, I tried it and the outcome is documented here:

http://forum.pfsense.org/index.php/topic,41193.0.html

Learn from my fail. (ok, not a total fail, as I did have a config backup and fresh install image on hand for a quick recovery. Learn from my example  :).

Of course I don't know for sure that flashing a vga image caused the problem, but it's the only obvious hypothesis from my POV.

The same config worked on the same hardware right before the update. It also worked on the same hardware after doing a clean install of 2.0-RELEASE. The only obvious thing that changed besides the date of the build was that I flashed a vga-enabled image on a non-vga box.

You should be able to upgrade that way, but backups are always ideal.