@dA_vO:

Same problem here. :(

And you can tell that you're using exactly the same hardware and version of pfSense as akus despite him not posting enough to be able to tell - I'm impressed!

The symptoms may be similar, but the problem isn't likely to be the same.  If you're having problems you'll need to post more than "me too".  Details of the hardware you're using, version of pfSense you're using, what the problem is and where it happens.  I'd also suggest you search the forum and read the wiki.

Thanks for the quick response and the info.

I installed version 1.2.3 before the office filled up with people. It is running now for 2 hours without any issue. The boot process was normal.

I also suspected some hardware hassle. Typically I would assume timing or temperature being involved in such a case. I just do not have any explanation why this happens at the same point during the boot process and never during normal operation.

When the office gets empty I will perform more boot tests to see whether the issue is solved with the new FreeBSD or not.

Christian

@hopeless:

yes but my problem is that I cant access the web gui…..

The second part of my previous answer attempted to respond to your issue accessing the web GUI.

boot number 3 - Safe mode, you will have to be quick when pressing 3 in the menu.
then edit /boot/loader.conf and add

hw.ata.ata_dma="0"
hw.ata.atapi_dma="0"

this will take care of the DMA and your system will start fine with the default boot.

Thanx,

I DL one of the images at this site, and installed it! Only problem I had was that I could'nt find what image to use. The one I DL seemd to be for PC, and I use a net48xx (former m0n0wall), and it wouldn't start by it self. Had to use Terminal after every reboot  ;D

Well with your information in mind I DL the image for 128MB from pfsense, worked perfect. I did however have some problems with physdiskwrite and Vista (runed as admin). Moved over to a XP machine everything OK.

So, thanx a lot!

1.2.1 is no longer the current, supported version.

what version?
i have it under services -> upnp

I've got it working :)

There was an error with grub so I did a new install without that and now it is working. Now it is time to play with some of the nice packages ;)

Thank you. I didnt even think about the crossover cable. I do have one in a box around here somewhere. These are pretty old cards "'99"

Thank you again ;D

The question has been asked and answered before.  Try using the search function above ;)

yes i went through the bios with a fine-tooth comb.

In the end the problem still remains unresolved, due to time constraints and not wishing to recompile kernels, i just swapped out the hardware for some DL150's, which it loaded onto fine.

thanks perry.

i'll look into that!

Thanks.

Hello.. Sorry to pull up an old thread but I was wondering if this issue still exists IP380's?  Also is there any way to get the NON embedded version on the IP530's?

Thanks,
Matt

If you current 1.2.2 setup is broken, it wouldn't change must upgrading to 1.2.3 :)

release announcement http://blog.pfsense.org/?p=351
Save the config file before a upgrade
Diagnostics -> Backup/restore

This the onboard adaptec controller on an IBM eserver 226.
Pretty sure it does hardware RAID.

Win2008 sees it as a single RAID disk as does Untangle and Endian during install.

No worries I've installed it to a single disk and just having a play now.

I like pfsense some of the features but am probably going to settle on the commercial
version of Endian. HEaps of features. Nice interface.

Regards & Thanks

Mark

same problem i had in the this post I described in post with subject "upgrade problem"

I also have had an upgrade problem going from 1.2.1 to 1.2.2.  I have the full install of pfsense on an 80gb hard drive, so space isnt an issue.  I did the autoupdate and it found the newer version and downloaded it.  However, as soon as the download finished it just gave an error that it couldnt do the update.

So I manually download the image from the updates directory (latest.tgz) and installed it manually.  However, that failed as well of course because the manual update process has to have the file named pfsense*.tgz.

Renamed the latest.tgz to pfsense_latest.tgz and it worked perfect.

Does the autoupdate process require the file to be named pfsense_* before it will run like the manual process does?

@richardb:

Hi
Also I have not changed default gateway on PC (200) from the router address (193)

If I change it to (221) the pfsense address then I lose internet access

Should the default gateway for lan side pc's be the wan address on pfsense or the ip address of the router?

If you want the LAN side PCs to connect to the pfSense web GUI then their default gateway needs to know how to get to the pfSense LAN address. When a LAN side PC attempts to connect to the pfSense web GUI at 192.168.1.1 it will see the destination is in a different subnet so will send it to the gateway. Does the gateway know where to send it next? I suspect the router (193) doesn't.

If the LAN side PCs run Windows, the commands ping and tracert can be helpful investigating these sort of problems. The equivalents on many Unix systems are ping and traceroute.

As to what the default router should be I'll leave that to someone else because I don't have experience or knowledge of how bridge mode works.