Thanks!

Its possible you may need to boot the pfSense kernel without ACPI. If necessary, try booting the livecd, selecting the ACPI off kernel, and restoring a saved config file.

I got bitten by this a few days ago. monowall 1.2 worked, monowall 1.3* (b7, b13) didnt get traffic in or out of either ethernet card, pfSense 1.2 was the same as monowall 1.3* until I booted ACPI off, then all was fine again.

& Now if I just knew how to install pfSense to hard drive with the ACPI off kernel… &

Sorry man, you're out of luck!

pfSense is FreeBSD and NOT Linux.
Repeat after me: FreeBSD is NOT Linux.
OK, your turn now!  2, 3, 4, louder, I can't hear you!

pfSense is a complete distribution like your FC. You cannot run CentOS on top of that either.
Well, except for a VM, but that's a different story…

new switch  ??? ? nobody will pay  :P

i think i have to separate my Wans from switch, and of course climb up my tower to move the wireless closer to the Pfsense.

and there will be nothing at the top of tower.  :-X

:D
thanx guys.

@Perry:

Your in luck. You just won the free copy of…...
When it's Ready

haha

1.2.1 is just about there. Only issue is possible wireless problems and there may be some packages that still do not function. It's labeled RC now for a reason, it's absolutely stable aside from wireless in some configurations and maybe some packages.

You'll want to use WAN rather than LAN on your LAN segment in scenarios like this. You'll want the default gateway to be assigned from DHCP, and the default gateway in 1.2 must reside on the WAN interface. You'll just need to adjust the firewall rules appropriately so you can access the management interface from the WAN side. Since it's inside your network, you'll likely want to disable NAT as well (enable AON and delete auto created rule).

@oswazi:

I had similar problem, you need to make sure that your Network cards are supported by FreeBSD.

Fixed it for you.

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

The more appropriate solution is to enable SSH keepalives in your SSH clients, which will keep the state active. Leaving inactive states hanging around for long periods isn't good.

If you can get console access you can reset the webconfigurator password and OS password. Otherwise you would probably have to burn ISO CD and re-install Pfsense and setup. Let me know if you need any help with this.

Do you have access to another computer?

Here's a procedure I have used. I booted the CD and installed to a USB drive (a 2.5inch notebook drive in a USB caddy) which I then connected to the computer on which I actually wanted to run pfSense. I had to configure the BIOS to boot off a "USB Hard Disk" and now it works fine. This sort of thing may get you past the "CD problem". Once you have the software installed you probably won't need to use the CD again for a good while.)

There are a number of variants, for example:

install to a hard drive on the other computer then move the hard drive to the computer on which you had the trouble.

install to a USB flash drive, take it to the real target computer, boot it then copy (dd) the USB flash drive to the hard drive on the target computer

Never mind that was a stupid question…
TIA.

For anyone who may find this thread in the future… some of those old Compaq servers are a real pain to get any BSD or Linux distro running on. I have some Compaq servers of that same era and tried pfSense, stock BSDs, several Linux distros and none would boot regardless of BIOS settings, having all the latest firmware and BIOS revision, etc. They run Windows 2000 and 2003 no problem.

Sometimes your best bet is to do as Gob did and find a different piece of hardware.

Also, is pfSense compatible with Serial-ATA hard drives?  i've tried installing on serial-ata hard drives & the 99 install completes just fine.  But after rebooting, pfSense or FreeBSd gets got in a loop, continuously scrolling some messages on screen.  i can't tell what messages because it goes by too fast.

They are supported but this issue is caused by FreeBSD 6, only happen on some chipset/motheboards combination it is fixed on 6.3 and better.

Can someone please give me a step by step to do what was mentioned here?

once you're up and running you'll need to use Diagnostics -> Edit File, open /etc/fstab and change ad0 to ad2 or however it shows on your ALIX. Save that file and reboot to test, and you should be set.

I have an ALIX setup and running just fine but I cant for the life of me figure out how to change my fstab. Currently it wants to boots from ufs:da0s1a and I have to type in ufs:ad0s1a when I reboot this is from installing to an adapter card. When I go to Diagnostics -> Edit File, no matter what I type in nothing happens and the screen stays blank.

Thanks ahead of time.

Is it possible that your CF card s just very slow on writes and the installation would eventually finish if you wait long enough?

iv set it to boot from cd and iv even unpluger the hard drive but it still does not see the disk
is there some other way to burn it on to the disk to make it run?

see http://devwiki.pfsense.org/wikka.php?wakka=BootTroubleShooting

grub might fix that, among other possibilities there. Please report back on what you find.

The core developers have been working very hard on the upcoming releases pfSense 1.2.1 and 1.3. Today I was work on 2 phone systems so I've also been very busy.

I believe the package url is: http://files.pfsense.org/packages/
Can you manually see the location from behind the firewall?

I just installed squid on my  pfSense 1.2-RELEASE
built on Wed Apr 23 21:04:50 EDT 2008. It installed fine.

This could have been a routing issue on the internet.
Try the package install again and see if it is working now?

Looks like you plugged the hard disk into a different socket on the motherboard.  Try moving the swapping the cables around.

http://devwiki.pfsense.org/FlashHowtoScript