just tested with pfSense-2.0-ALPHA-ALPHA-20090427-1036.iso

no problems anymore , so there must be something wrong in the releases after this one for me.

i don't know what , but it has to do with the Realtek of config file.

??? ??? ??? ???

Wow.  I would never have guessed that.  That's a shame; man pages are so useful…

Thanks anyhow,

Eric

Hmm…. Ahh... I see ... So all is done by serial and web interface ?
I nerd some more monday and thanks for your reply

Burn ISO image to CD Insert CD into CD-ROM drive Boot system from CD Select option to install to hard disk

There already is documentation out there, so I'm not going to type it all out here for you.  If you're having problems with a particular step, and the documentation (including the Wiki) doesn't cover it, then post details of your problem (not "it doesn't work").

I tried enabling polling to see what difference that might make.  I noticed about a 50% decrease in throughput with polling enabled.  Transfers across the WRAP box went from about 2MB per second down to 1MB per second.

For now, I will keep polling disabled and see if I have any issues with the new version.  So far, it has been working great.  ;D

Thanks again.

Awesome!  Thanks for pointing that out.  I must have missed it in the docs.

Eric

Perhaps your LAN systems are not given the correct DNS details. Do you need to specify DNS server(s) in System -> General Setup or need to change the setting in the box Allow DNS server list to be overridden by DHCP/PPP on WAN

Are your LAN systems assigned IP addresses by DHCP? If not, how do they know the address of the DNS server? If so, then they can find the DNS server address by DHCP but you have to specify the address in System -> General Setup or tick the box to say get it from DHCP assignment on the WAN interface (which assumes your ISP provides it by DHCP).

Not that it matters quite yet, but you may be interested in knowing that in 2.0, the RRD data can be backed up in the XML file that you get from the WebGUI, so it can also be restored.

Other things to note:

Remove the packages you don't want before you make your final backup. The settings will still be in the config xml (you can edit them out) but unless you uninstall the package, it will get reinstalled after the restore is finished. You should be able to put the config on a FAT formatted USB stick in <drive letter="">:\cf\conf\config.xml - The installer is supposed to pick up on this and install with that config to the hard drive. I haven't tested this, but it will speed the process up greatly vs. installing, getting it on the network, and restoring from the WebGUI.</drive>

Just to clarify: Does the "No dump device" message appear BEFORE the console prompts for the installation parameters OR does it occur on the reboot after an apparently successful install?

If you completed an install did you select GRUB as the boot loader or the FreeBSD boot loader? (I have no experience with GRUB as the boot loader for pfSense but have seen a couple of reports that people haven't been able to get it to work.)

On my installed system the startup reports:

vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
udav0: <shantou 0="" 2="" st268="" usb="" nic,="" class="" 0,="" rev="" 1.10="" 1.01,="" addr="">on uhub0
udav0: Ethernet address 00:60:6e:30:32:26</shantou></generic>

so after the ISA VGA report it looks as if the kernel is looking for USB devices. Do you get a different result if you remove all USB devices from the system? How about if you disable USB devices in the BIOS before booting. (I needed to do this on my AMD Athlon based system before I could get pfSense 1.2.2 to boot but that problem went away with pfSense 1.2.3.)

It works fine. Glad I could get rid of those awful 2Wire gateways.  ;D

From everything I have read, it should "Just Work" as long as the disk is dedicated to FreeBSD.  Since I accepted all of the defaults, I assume that this is what was set up.

I have run lots of tests.  Can someone who understands this tell me what information I might post, or what I might try, or tell me "Clearly this will never work because xyz" ?

Thanks.

I have tried the following permutations of BIOS settings and Geometry:

AUTO (Disk Config) and LBA
USER (Disk Config) and LBA with 3148 16 63 (I changed to a 1.6G disk)
USER (Disk Config) and LBA with 787 64 63
AUTO (Disk Config) and NORMAL

With AUTO, 3148 16 63 was offered and accepted in the PFSense "Select Geometry" dialog in both cases.

I always put the same geometry in the BIOS and the PFSense "Select Geometry" dialog.

For each of these four permutations, I tried the default Boot Boot configuration (No Packet, no Grub), with "Packet", and with "Grub"

In all cases the Default Boot configuration and the Packet install fine then fail on boot as described previously with the one second Beep every 10 seconds.

In all cases the Grub configuration failed installation, saying "Cannot mount selected partition".

yes, i had same problem, and i have 2 disks in RAID.
Playing with bios fixed my problem.

When trying to instal pfs sees two disks and one raid one disk, install only to raid disk no probs…

This was already reported in 1.2.1/1.2.3 http://forum.pfsense.org/index.php/topic,13278.0.html
As mentioned there, it has been updated and is current in snaps and 1.2.3RC1

Excellent post grab3. I would love to see a tutorial for this. If you want I could host a tutorial on my website. This is something that really interest me and I am sure many people!

hansru, that only works for D series.
I don't think ALIX C series support boot from a usb cdrom.

Hi
Yes  I apologise just put last two sections of IP address
I used these address4s before and pfsense seemed to work fine however I think that I must have bridged lan to Wan
I have now kept same addresses and bridged and it appears to be working.
Should I simply give wan card an "odd" address say 198.162.1.158 and unbridge
What is the advantage/disadvantage of bridged
Thank you again for your time

If you are trying to install pfSense to an embedded platform other than a ….
How to setup NIC team on a HP ProLiant DL 380 for fault tolerance and Load