@GruensFroeschli:

If you switch NICs around you need to assign them afterwards under:
Interfaces –> assign.

when i start to install–--

add hardware
network adapter
chose manufacture==level one
chose cd drive

installed
but it s till not working (it appeared with error code 10)....

The cause of all my troubles appears to have been the finicky BIOS of this box. The trick is to have one setting for when booting of CDROM and installing to HDD, and then change the settings back to Optimal Defaults after having installed.

Oh, that as well as disabling DMA access to the HDD with appending of hw.ata.ata_dma="0" to the /boot/loader.conf.

AND - you MUST unplug the CD drive (even if there's nothing in it and the BIOS is configured to boot from the HDD first!)

It may sound like the bleedin' obvious to people reading this now, but it confused the hell out of me!

If you're after an existing custom install on such platforms then you're pretty much limited to the likes of DD-WRT, OpenWRT etc (all based on Linux).

I have two IP530's running pfSense 1.2.2 from the harddrive. I installed pfSense the following way onto the drive without having to use the CF card.

Take the drive and the CF card out of the IP530. The CF card is not needed any more, the ones from mine were only 8MB any way. Hook the drive upto another computer. Boot the pfSense live CD (configure the network settings just to let it boot, they will be re-done when it boots in the nokia). Select option 99 after it has booted. Install to the drive and select the embedded kernel at the end of the install. ONLY put the harddrive back in. Power on the nokia. pfSense will boot from the HD but when trying to mount the file system it will fail and show a command prompt. Enter ufs:/dev/ad1s1a (I'm trying to recall from memory the exact device name. An example is shown, all you have to make sure of is that ad0 is replaced with ad1, this is because the CF is seen as ad0) The system will then boot into pfSense, it will ask you for your network setup, enter all then info and let it boot to the menu. Select option 8 - Shell Edit /etc/fstab with VI and replace both instances of ad0 with ad1. After you save the file you can reboot the machine and everything will boot automatically.

Let me know if you run into any problems.

Robbert

:P :P :P :P

Me being an absolute twirp.  This server was used in the DMZ before and it was still connected to the old juniper firewall on the DMZ port!!!

What a T*T !!  :)  hehe

Works fine now.

Probably solved but…
It happened to me several times. It had to do with my DVD drive. If you burn and install with the "same drive" your problems "should" go away. It worked for me, after several hangs I tryied the drive witch I used to burn the cd and the problem went away. If you still have problems installing try to burn the cd with low speed settings.
Hope it helps someone

The trouble is that the driver you're referring to is specific to the underlying version of FreeBSD.  To get it you'll either need to back-port it (not necessarily simple) or update the entire of FreeBSD.

I've currently given up on my ide connection, I have no idea as to why it stopped working… now it doesn't even identify the laptop drive in bios... I wonder if there was hardware besides the resistor missing on the board (I soldered on the ide connector & added a resistor to select master (as mentioned in the alix documentation), but that went really smoothly...other than the not working bit ;) )...

Onto the current problem.

I would love to use a cf to just boot from a notebook drive that's connected via usb, but I can't get the default freebsd boot-loader to see the drive and I haven't been able to try with grub, as it just fails to install grub on the cf while hooked up to a desktop.

(if anyone could offer ideas as to how to get grub working, it would be appreciated)

Not being able to get grub working, I decided to just mount the usb drive at boot, and run the more disk intensive stuff from it (squid definitely doable...would be possible to send all logging there?)

But...of course... it still fails to find the drive (this early in the boot process)...

Welcome to pfSense 1.2.2 on the 'pfSense' platGform... EMounting filesysOtems...M_LABEL: Label ufs/pfSense removed. mount: /dev/da0s1 : No such file or directory done. Creating symlinks......done. Launching PHP init system...umass0: <western 0="" digital="" external="" hdd,="" class="" 0,="" r1<br="">da0 at umass-sim0 bus 0 target 0 lun 0 da0: <wdc wd60="" 0ve-00hdt0="" 0000=""> Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 57231MB (117210240 512 byte sectors: 255H 63S/T 7296C) done.</wdc></western>

Running mount /mnt works fine once its started up. Here's my fstab:

Device        Mountpoint      FStype  Options         Dump    Pass# /dev/ad0s1a     /               ufs     rw,noatime      1       1 /dev/ad0s1b     none            swap    sw              0       0 /dev/da0s1      /mnt            ufs     rw              1       1

If I can't even get this working on bootup… what would be the easiest way to run mount /mnt later during the bootup process.

Any thoughts/ideas/suggestions at this point would be greatly appreciated.

Issue may have been related to KVM/VM, but solution would be by re-scanning for changes in interfaces.

Seems somewhat OK in standard standalone box

-J

Assuming you've already tried another download in case it was just a bad ISO file?

1.2-Release works perfectly at DL360/DL380.

Ok, just reinstalled system. not really way, but works…  ::)

By 5. I mean being able to assign URL/Port/Protocol policies to groups of users based on, as your suggestion was, RADIUS user groups.

I'll look into the package combo and do some more reading. Thanks.

N/M tried a different HDD, the first was bad

OK - thanks.
I'll try a manual firmware upload on Friday and also check out the BIOS.

loader.conf contains:

utoboot_delay="1"
vm.kmem_size="435544320"
vm.kmem_size_max="535544320"
kern.ipc.nmbclusters="0"

Once more with feeling… pfSense uses FreeBSD - FreeBSD is NOT Linux.

Once more, again, with feeling… just because your hardware meets the minimal requirements doesn't mean it'll work.