Thnx!

Thank you so much!!!  i already installed the pfSense in my pc.  Thank you so much…..

OMG! I am sorry (and very tired) - I retyped the name of the script instead of the image file  :-[ - now everything runs well. Thank you for pointing this out so quick!  :)

I ended up putting in an IDE HDD instead of the SATA drive and it seems to be working now.

Didn't produce any results with the pin-shortening, however as I can (did it today) connect to the D-link gateway via console with no problems, the cable and serial port is fine on the receiving computer. I'm starting to get very amazed over how difficult this is, I have tried surely 20 different ways to solve this without any luck.

Perhaps your harddisk is in poor condition, lots of soft read errors and the retries are taking a long time. Do you have a fairly new motherboard? If so, I suggest you try a recent snapshot build of pfSense 1.2.3. A number of people have found the hardware support in 1.2.3 is better. I have seen 1.2.3 boot promptly on a system on which 1.2.2 hung.

The embedded version is split into two paritions, one called pfSenseCfg, and in the folder "conf" there is a file called "trigger_initial_wizard" - deleting this file should make the wizard go away, as far as I know.

@4920441: So… is there a way how I could assign the vlan where the ppp client is connecting to, gets a local IP address AND pppoe is able to use it, too? Is therre no 'elegant' way, or do I have to assign the appropriate vlan interface simply another, second IP address? Cheers, 4920441

I would definitely suspect the media at this point. I suppose it could be the controller, but that is much less likely than the CF dying. The real way to know would be to pull the card out and mount it in another system and see if the file is still corrupted there, but it may be safe to assume the card is about to die.

i solved my problem by  adding: hint.acpi.0.disabled="1" to the end of /boot/device.hints from the diagnostics -> edit file menu option

BIOS? Mine is running 1.33c. I think I only had to fiddle with the settings on the SATA setup, but here are the settings for reference: show ConSpeed = 9600 ConLock = Enabled ConMute = Disabled BIOSentry = Enabled PCIROMS = Enabled PXEBoot = Disabled FLASH = Primary BootDelay = 2 FastBoot = Disabled BootPartition = Disabled BootDrive = 80 81 FF FF ShowPCI = Enabled Reset = Hard CpuSpeed = Default

Thank you Chris. That helped me alot  ;D

I sort of have the same issue, everything seems to be working okay on the LAN side except I cannot access the internet from the LAN side workstations. When I check interface status both LAN and WAN look okay no apparent errors indicated. My ISP is Cogeco in Oakville Ontario CANADA, I entered all the technical details that my NETGEAR router had about Cogeco into pfSense box and pfSense box 'looks' okay using same parameters, I see no obvious errors. If anyone has any suggestions of what I should look for or try I would appreciate it. Thanks <marvin></marvin>