Thanks, i already removed most of the config files content and then i restored it manually.  :(

Thanks,i will try this once i receive my cable to use a 40gb 2.5 inch hdd on my router hardware.

That early in the boot process it's way into FreeBSD territory - probably nothing we can do there, but if you can find a BIOS update or tweak some BIOS options, especially ACPI, it may help.

2.0 asks you half-way through the boot process whether or not you want to install.  Reboot, keep an eye on it, and press "I" when it tells you to.

As to your CF RAID, whether or not it works really depends on what chip powers it.

I've given up - after a few fresh-installs, new creation of new VM and "pain in the head" log file reading I'll wait till  pfSense gets an update - maybe then it will work.
Actual FW is m0n0 which indeed is very good, but I'm missing pfSense features ;-)

Exactly what I needed. Thanks a million!  ;D ;D ;D

That seems to have worked.  I'm in the GUI now. Thank you.  Strange with no errors that it would be different the second time around, but I'm happy it seems to be working now.

There are some posts in the same way.

Getting All I saw people trying, Try this:

change sata mode in bios

retry install

burn another media in low speed

install 1.2.3 and upgrade

Ok. You have answered my question.  I downloaded the wrong file.  I'll now download the correct file.

To answer Bruce, I have a HP Pentium with 1G of RAM a disconencted harddisk (as Public IP does not need it), 2 NIC cards and the other normal bits and pieces you find on a motherboard that is 5 years old.

The outcome I want is to have pfsense replace my ZoneCD from PublicIP, which looks like is no longer in existense.  My wife has a 40 seat Cafe in which we offer free wifi for our customers with 2 and data caps per day per user.

Wouldn't mind a hand with that but I'll search the form for help, unless you can point me in the right direction.

Peter

RESET STATES…Fixed it.
Thank you.

I had tried the rules for the 192.168.1.x networks before but to no avail... but that was because I never "reset Firewall states".    Once I did that it was all working .

Thanks again.

Updates don't happen with pfSense but every so often any way. Usually on the order of a year plus between updates. Officially released updates anyway. You can pull from GIT, but I would only do that if it fixes a certain problem you are actively having.

Thank you so much for the clear and informative answer :) I dunno what I'd do without pfSense!

Sorted :)

@Jason:

Can I just create entries for those on the System Tunables page?

No, loader variables are not the same as sysctl tunables.

@bainwave:

Thanks bob for your speedy help.

few more questions still hunting me..
1. I have  CISCO Catalyst 2950G switch, can I club all my 3 broadband connections with a single NIC?
if yes, how could I achieve this?

All my broadband connections are having a pool of (20) public ip's.

2. Now can i configure all my public ip's into this pfsense in order to run my show?

Am in a work group environment, can I control the users & computers from this pfsense?

Once again Thanks for your advise.

You need to setup VLANs on pfSense upon the first boot up.  Configure 1 VLAN each for the 3 WANs and 1 LAN.

If for example, you use VLAN 10, 20, 30 and 100 for WAN 1, 2, 3 and LAN respectively; then you continue with the interface setup assigning VLAN 10 for WAN, VLAN 100 for LAN; the remaining interfaces can be configured from the webgui.

Let's assume you use ports 1, 2, 3 on the switch for WANs 1, 2 and 3 respectively.  You'll then need to configure Port 1 to be native VLAN 10, Port 2 to be VLAN 20 etc.  Now, these ports need to strip the VLAN tag on egress and tag on ingress (default VLAN ID per port).

Next, assuming Port 4 is connected to pfSense, you'll need to trunk VLANs 10, 20, 30, 100 to Port 4.
The rest of the ports that are connected to LAN will then need to be in VLAN 100 (tag on ingress aka default VLAN ID) and strip the VLAN tag on egress.

eg.
In priviledged access mode type:
vlan database
vlan 10 WAN1
vlan 20 WAN2
vlan 30 WAN3
vlan 100 LAN
exit
copy running-config startup config

configure terminal
interface fastethernet0/1
switchport mode access
switchport access vlan 10
interface fastethernet0/2
switchport mode access
switchport access vlan 20
interface fastethernet0/3
switchport mode access
switchport access vlan 30
interface fastethernet0/4
switchport mode trunk
switchport trunk allowed vlan 10,20,30,100

interface fastethernet0/5          <–--  repeat bolded section for all the ports you need to be on LAN
switchport mode access
switchport access vlan 100

end
copy running-config startup-config

After that you can configure the remaining VLAN interfaces in pfSense for your WAN2 and WAN3 links accordingly.

Thank you very much Nachtfalke!

@wallabybob:

Why not backup the config file through the web GUI: Diagnostics -> Backup/Restore click on Backup/Restore tab
This uploads the config file to system running the browser: you can copy/save it to your preferred destination.

Hi wallabybob, thanks for reply. Looking to actually run the config from another location not save it. I want to be able to run the config from a "write" protected device.

Why wouldn't changing the cables around "fix" the problem?

unplug cable from em0
unplug cable from em1, put it in em0
plug other cable into em1

problem solved, now both boxes match what they're using em0 and em1 for.

dmesg is correct. We do not use the stock e1000 driver from FreeBSD 8.1-RELEASE (which is what 2.0 is based upon).

Thanks for your help :)