@D0X: Hi there. I'm running 1.2.3 RC1 at the moment on a CF card, I remember I installed that from a CD to be able to install packages some months ago. But I like to run the latest nanobsd embedded version of 1.2.3 on a CF card, so I downloaded the 1GB image and "physdiskwrited" it to the CF card. Upon boot it just stops after the BIOS POST message, there's a flashing cursor and thats it. Tried another card, another cardreader and the 512mb image, but no good. Is this one of those serial boot only images? I want to boot it VGA + keyboard. What am I missing here? You are going to have to help us out. What make/model and BIOS version ?

There is an Avahi package you can install from System > Packages and it works just fine on 1.2.3 NanoBSD-based embedded images. I'm using it on my WRAP right now.

To use CARP you just need the same number of interfaces on both boxes. They do not have to be the same NICs. Carp does reqire an extra NIC on each box dedicated to keeping both boxes in sync. http://doc.pfsense.org/index.php/Configuring_pfSense_Hardware_Redundancy_(CARP)

Many thanx…

Got it! Thank You! :D

@gravyface: Thank you.  Has this been clarified anywhere in writing (besides here)?  I didn't see it in the docs, but would be happy to update it. Have a look here: http://doc.pfsense.org/index.php/Installing_pfSense

Just curious, which stencil are you using? I can't find it anywhere on Graffletopia :/ Merci :)

Super..!! Thx :)

@comppuwork: the daughter card is a AD3RTLANP 3 PORT NIC (realtech rtl8100c). the wan port works but the other 2 do not get anything at all. do i have a driver problem? can anything be done about it? i can return the firewall, but i really would like to get this one working. Sounds like a Jetway motherboard and daughter card. The 3 daughter card interfaces should be all the same. I'm not sure what you mean by "the wan port works but the other 2 do not get anything at all". Do you mean you tried all three daughter card interfaces as the WAN interface but only the one you are currently using registered receiving an IP address from your ISP? If thats what you meant, how did you go about trying the other interfaces as the WAN interface and how did you verify they "did not get anything"? What did you directly connect to the LAN port? A switch? A computer? what has me confused is that everything worked with monowall. I believe monowall is based on an earlier version of FreeBSD than the version used in pfSense. Occasionally there are unintended regressions where a newer version of FreeBSD breaks support for a device supported by an older version of FreeBSD. For diagnostic purposes, it would probably be useful to make the working "WAN" port the LAN port so you can connect to the pfSense GUI, complete configuration and more readily provide further system information that can be more easily provided if it can be capture on another computer? Are you connected to a cable ISP rather than a xDSL ISP? I've seen reports that it is common for cable modems to remember the MAC address of the downstream device and only talk with that device. This could impact your problem using the other ports as WAN ports.

Hi to everybody! Yesterday night I manage to install and configure my router pc. wallabybob you are right after I boot my pc, apareantly it is freezed but, buut  ;D on hyperterminal apear the initilaization. I said wau. Now it is working,I will test my router pc about few daysand after that it is in production envoirement. I  manage to configure my wifi card ralink 2561, bridge with lan interface, create on firewall rules an entry for wlan. I don't manage to test wpa wpa 2 on the wifi, seems I can't connect trought dhcp from wifi, from lan working very good, but I phink my os on my laptop has a problem, because my friend manage to conect trough dhcp of wifi. So my system is: MB 5ALI61 with socket 7 procesor AMD K6-2 550 underclock at 250 MHz(2.5X100MHz FSB) 256 MB SDRAM LAN 3COM Cyclone WAN 3COM Tornado (pppoe connection with dynamic ip  :-) WLAN edimax 7128 (ralink 2561 chipset) ADPTER CF to IDE TRAXDATA 2Gb Pro (working at ata 66) 12 V 5 ports switch power on from my router pc Mainboard even boots without no vga. I mange to coonect trough hyperterminal from laptop using an ATEN USB to SERIAL adaptor and a null cable modem. Port com1 on may router pc configure on 3F8 IRQ 4 (not auto) and port com created on my router configuration is speed 9600 data bits 8 Parity N stop 1. Power measured with a killawatt is 20 - 22W Thank you very much for your support wallabybob Problem solved. Thread close

I learned it !Thank you!!

I'm not sure of the details of how your configuration changed but suspect that you might have ending up changing your pfSense LAN IP address so consequently when your laptop attempts to get an IP address from the last used DHCP server (old pfSense IP address) it can no longer get one because the server doesn't respond. Perhaps if you power cycled your laptop you might restore communication with pfSense. (Assuming pfSense is configured to make a sensible response to laptop DHCP request.) If that doesn't work, you probably need to connect to the Alix serial console for further investigation.

A low level format did the trick :-)

if you can i would upgrade from console: ssh into box, select "upgrade from console", find the correct url at http://snapshots.pfsense.org (the full install ones are at the bottome of the page) and go from there. the console install feeds you info as its installing, I had the firmware update from within the web gui fail a few times, the console update worked however.

Hi there dsamms, the method described in you 1.2.2 hd install tutorial also works for pfSense2.0beta, therefore I think it should not be removed. Just did a successfull 2.0 install on my ALIX. FreeBSD 8 doesn't seem to include the ATA patch either. Too bad. But thanks to your tutorial pfSense2.0 is up and running now. The only further thing I had to do was to reset to factory defaults before I could assign an IP to the LAN interface properly. It bailed out with the folowing error before: Fatal error: Cannot unset string offsets in /etc/rc.initial.setlanip on line 200

Got the same problem on my HP vectra VLi8 with the latest bios (HZ.01.10). Upgraded from 1.2.2 to 1.2.3,  hangs after smist0: <speedstep smi="">cpu0. Tried failsafe and without ahci, same problem. Seems like i'll have to take my backup computer in use :/</speedstep>

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: ifconfig dc0 link 00:01:02:03:04:05 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.