Thanks a lot! everything is ok now.  ;D

@madapaka:

This is a common dilemma, the unexpected usually happens during reboot especially if the machine has been up for a long time, most problems though are caused by hardware related problems and not by software updates. I've updated all 7 pfSense boxes that I manage and so far I did not encounter any problems.

Yeah, and other things you only hit when rebooting a box that hasn't been rebooted in months or years. The only problems I've seen with 1.2.3 upgrades thus far is boxes that didn't boot back up because of a missing keyboard, sitting at a "F1 to continue" BIOS prompt, and another where a different hardware problem and resulting BIOS prompt kept the box from booting back up. In both scenarios, obviously a reboot would have had the same effect as the upgrade.

Thanks, that worked like charm on 1.2.2-RELEASE.

Will be running a litte more testing, but I am pretty sure I will be running pfSense in production very soon.

Thank you very much for your quick help!

Kind regards,
Niklas

The startup reports
@Antonix:

Dec 26 22:31:14 pfSense kernel: dc0: <macronix 10="" 98715aec-c="" 100basetx="">port 0xf800-0xf8ff mem 0xfedffc00-0xfedffcff irq 9 at device 11.0 on pci0
Dec 26 22:31:14 pfSense kernel: miibus0: <mii bus="">on dc0
Dec 26 22:31:14 pfSense kernel: dcphy0: <intel 21143="" nway="" media="" interface="">PHY 31 on miibus0
Dec 26 22:31:14 pfSense kernel: dcphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Dec 26 22:31:14 pfSense kernel: dc0: [ITHREAD]
Dec 26 22:31:14 pfSense kernel: dc1: <macronix 10="" 98715aec-c="" 100basetx="">port 0xf400-0xf4ff mem 0xfedff800-0xfedff8ff irq 10 at device 12.0 on pci0
Dec 26 22:31:14 pfSense kernel: miibus1: <mii bus="">on dc1
Dec 26 22:31:14 pfSense kernel: dcphy1: <intel 21143="" nway="" media="" interface="">PHY 31 on miibus1
Dec 26 22:31:14 pfSense kernel: dcphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Dec 26 22:31:14 pfSense kernel: dc1: [ITHREAD]
Dec 26 22:31:14 pfSense kernel: dc2: <macronix 10="" 98715aec-c="" 100basetx="">port 0xf000-0xf0ff mem 0xfedff400-0xfedff4ff irq 11 at device 13.0 on pci0
Dec 26 22:31:14 pfSense kernel: miibus2: <mii bus="">on dc2
Dec 26 22:31:14 pfSense kernel: dcphy2: <intel 21143="" nway="" media="" interface="">PHY 31 on miibus2
Dec 26 22:31:14 pfSense kernel: dcphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Dec 26 22:31:14 pfSense kernel: dc2: [ITHREAD]</intel></mii></macronix></intel></mii></macronix></intel></mii></macronix>

which suggests the NICs are recognised by the dc driver and that the problem is likely only that the driver can't (or doesn't) determine the MAC address for the NICs. Do you know what the MAC addresses should be?

Generally MAC addresses can be set by shell command of the form:

The command # ifconfig dc0 will show a number of parameters for interface dc0, including the MAC address.

Would you please attempt to set the MAC address by command and verify it was set to the specified value. If that works you should be able to get somewhat further in getting your firewall to do useful things.

I expect you will have to pursue this problem with the FreeBSD community. A quick google search didn't show any obvious evidence that anyone else has seen this problem.

You need to pull the CF or storage media and image it on another system.

Also, the CF is kept read-only so that it isn't worn out by constant writes. Logs are kept on a RAM disk (both /var and /tmp are kept in memory).

Disabling ACPI in the device.hints file works.  Thanks to all for the help on this.

If you have changed a small number of items, describe textually what you did (or for rules, post a screenshot of the page).

@MeroMarko:

Helloooo.
Can A Good person help me? plz

Run the Setup Wizard.

Under System > Setup Wizard > fill in the blanks including the new ip address.

Thank you this is clear :)
I dont see any problem with this way of setup.

Where did you ping the modem-router? From a client behind the pfSense or from the pfSense itself?
What kind of WAN is in front of the modem-router?

What do your logs from DHCP show?

You can just disable CARP on the master to force it to fail over. Or shut down the master. Normally I do what dotdash recommended.

Link removed. No plans for any further 1.2.x snapshots.

yes pfsense can

Disabling packet mode during boot block installation solved the issue.

I updated the squid package and shortened the tab names so they should go back to tabs instead of the drop-down list.

They are usually announced in various places, the two main ones are:

The pfSense blog (you could use the RSS feed):
http://blog.pfsense.org/

Mailing lists (including an announce list):
http://www.pfsense.org/index.php?option=com_content&task=view&id=66&Itemid=71

i think it's the motherboard. I have an Asus P5K PRO, i tried with a p4V88+ and it worked perfectly with same cables, hardware, so and software. I don't know why, because i have the same setting both in the bios and so.