Try with 1.2.1 RC2 if it still is a no go then try 2.0
http://blog.pfsense.org/?p=207

I tried 1.3RC2… I'm successful on the installation... Thanks :D

If you donate to ermal's bounty for the traffic shaper he has a build that includes his new traffic shaper running pfSense 1.2 running on FreeBSD 6.3. After donation of whatever amount he will send you a link to it.

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

I've installed pfSense 1.x to 2.0 successfully on many systems.

Make sure there is not a usb thumb drive plugged in during the install to the hard drive.
With IDE systems make sure the hard drive is the primary and the CD-ROM is secondary.

There is no console upgrade in 1.0, you can upgrade in the GUI using the Firmware page as described in the upgrade guide to go from 1.0 to 1.2 or 1.2.1.

@HalNineThousand:

I didn't mention in the first post that I was puzzled because the line about media failure said to check the cable, so I figured that was off.

That error refers to the onboard network interface not detecting a link (the hint was in the reference to PXE).

Ok After further looking into this.

I have switched modems now and that means I have changed everything except the underlying software. I have even changed ADSL providers to see if that is the issue.

When disconnecting from a remote PPTP server there are issues that have presented themselves on totally different modems. These issues are not apparent when using PPPoe within the pfsense box.  Both modems reboot themselves when disconnecting. The connections hang and then about 3 minutes later both connections work again.

I have used different hardware for everything and it seems like a software issue.

I would really appreciate some kind of help here. I know the devs are busy but this seems like a pretty important issue not just for me but for pfsense.

Last I checked you can't upgrade embedded installs.  I'm sure if that's no longer the case somebody will say shortly ;)

Thanks perry it works perfectly!

Hello,

indeed, lighthttpd provides you GUI  :D

cheers,

The answer to this thread is given.

I'm locking this thread since schlumpf still doesnt know how to express himself.

This might help you:
http://forum.pfsense.org/index.php/topic,8358.0.html

See my replies in http://forum.pfsense.org/index.php/topic,11592

@GruensFroeschli:

Hehe. The same happend to me a few weeks ago.

Lesson learned: always leave SSH open so you can log in and revert to the config.xml.backup just in case you wrote something wrong….

Happens to the best of us I guess…  ;)

All is working well now and I'm a happy camper so far. I'm using 4 of the 5 interfaces on this IP330 on a 22/2 connection and while the CPU utilization is averaging 80%, I'm not noticing any performance problems. Maybe a slightly slower web interface while looking at the graphs, but not unbearably so. It should do the job for our needs.

Reinstall to 1.2.1 fixed it. Thanks for all the help guys  ;D

For the second - look at the Multi Wan forum ;)

As for the issue of your static IP WAN - have you configured the static IP and set the default route?

@Cry:

Does the system boot?  What's displayed on the (serial) console?

I have solved the problem. Actually, there was no problem with pfsense but rather with the fact that Windows Vista I am using (don't ask me why) is apparently incapable of displaying any data over serial cable.

After I used a WinXP machine, everything worked fine. The boot-up process was interrupted at a point where you should provide information on vlans and name the interfaces. After that, all the services come up and you can access the webconfigurator through a web client on default IP and password.