@jimp:

Use the console. There is a menu option to change the LAN IP.

DOH!!  Forgot about console access.  It worked.  Thanks.

If you have a USB CD-ROM or a USB to IDE or SATA adapter, either should work for installing from the CD.

I haven't heard of whether anyone has had any success with making a working bootable pfSense installer on a USB flash drive using the iso image.

You should be able to use the menu option on the console which moves the config to a USB drive or floppy, and then it will use that to save, and read it at boot time.

@jimp:

Is there maybe a serial port header inside that you could hook a cable to?

I thought some of them had a header that you could use with the old PC style serial port internal plugs (they go from the standard serial port to what looks like a series of jumpers)

Thanks for all your advice. If I could find a cable like that, I would rather find the part # of the original serial port connector on Alix boards and order one. That saves time and money.

OR,
I could risk ruin my board by updating BIOS blindly.

@helmsman:

ok…so I guess the WAP would be on the 'WAN' interface?  Would the default gateway be the 'LAN' card?

Also, I don't see a way to set a default gateway on the LAN interface.  Is this possible?

So basically this firewall is meant to be an Internet firewall and what I'm trying to do is not really what the firewall was designed for?

I would use the pfSense LAN interface to connect to the WAP(s) and connect the pfSense WAN interface to your LAN. I would use pfSense as the DHCP server for the wireless clients, then pfSense will automatically tell your wireless clients what the default gateway is (pfSense).

The default firewall rules in pfSense essentially allow any access from the pfSense LAN side and block (unsolicited) access from the pfSense WAN side so you will need to add firewall rules to both pfSense interfaces to give the access controls you are looking for. (The firewall rules apply to incoming packets on the corresponding interface.) No internet required! But if you have internet access and you want want wireless clients to access the internet that can also be controlled by the firewall rules.

If you have a DHCP server on your LAN you could have the pfSense WAN interface get its address from the DHCP server OR you could assign it as a static address. In the latter case, if you also want to allow some internet access you would have to configure a gateway on the WAN interface.

Oleeee!!!

You are right! I've done two partitions 4GB and the rest. And pfsense boot correctly.
Thanks Jim.

Now, I try to find out, how to use the other espace (in the partition 2) to the primary partition.
Thanks a lot!

@jimp:

Are the IPs on the LAN side routed to the WAN CARP IP address? They should be, or the next hop up will have no idea how to get them back to your LAN segment. Traffic may go out and never return.

No, they're not yet. I wanted to confirm that was indeed what needed to happen. Funny thing is that I can do an icmp ping and get a reply even though it's not routed through the wan carp ip yet. I'll contact our uplink provider.

The installation documentation covers what they are and how you use them.

Following the link you posted lists 4 different NanoBSD images and an ISO.  If the mirror you selected doesn't list the ISO then post details so that it can be fixed and try another mirror.

As for the network card, it's possible that chip just isn't supported on the underlying OS (FreeBSD 7.2)

You might try the 2.0 beta.

You can post about the freeswitch package in its own thread on the packages board here.

As for the file size of packages, it's impossible to do since the packages may vary based on dependencies and builds, etc.

There's passive PoE and then there's 802.3af.

Passive PoE is what is used by the Alix boards, Ubiquiti APs, etc.  It simply sends DC over 4/5 and has return on 7/8 and can range anywhere from 5-24V depending on the device (most are in the 15-20V range).  Using a Passive PoE adapter with a non-PoE device can cause a lot of damage.

802.3af is what you're going to get out of a PoE switch.  It is commonly used for IP Phones, security cameras, name-brand wireless access points, etc.  It runs 48V DC and has a detection process where power is only provided to a device that needs it, meaning you can use a PoE switch with non-PoE devices.

If you want to use a device that requires Passive PoE with an 802.3af PoE switch, you can use an adapter like this:

http://www.ubnt.com/8023af

Bumping won't help you get answers faster, all it will achieve is to annoy people.

Some of your questions have been answered in other threads (such as the case of the USB CDROM) - please search the forum.  Instead of CF look at devices designed as hard disk replacements, either SSD or Flash Disk modules (such as these from a supplier I've used before).

It's normal, just disregard it. Common thing to see with FreeBSD, google it for more info if you're interested.

@afunez2010:

I read the upgrade guide, and see that i have to backup my configs, and then install the new version and restore my backup!!

No you don't, that's not what it says. Follow the instructions under "Full installation" here.
http://doc.pfsense.org/index.php/Upgrade_Guide

When the interface mismatch screen comes up at boot, just make sure you assign as many interfaces as you had previously assigned and none of your rules will disappear.

You write the 1G image to 1GB flash memory, the 2GB image to 2GB flash memory and so on. Use the LiveCD installer to install on regular hard drives.

I have also had this problem see my post here

http://forum.pfsense.org/index.php/topic,24753.msg128448.html#msg128448

replacing the mbr fixes the boot for me.

you should see some indication of booting on the screen, I always get
a backslash with blinking cursor then the text

everything else goes out on the serial port.

.

I have sorta done this,

1. write embedded image to CF card, try to boot from card in USB to CF card adapter
   got blinking cursor of death.

2. open CF card with hex editor and replace the first 446 bytes (1BEh) of the
   MBR with the MBR found in /boot/mbr on the freebsd 8.0-RELEASE-i386-bootonly.iso
   CD. that fixed the boot

I also just tested installing from the pfsense cd to a usb thumb drive
after install finished and booting from the USB drive, I made it to setup
network interfaces, so I think it will work.

EDIT:

I wrote pfsense 1.2.3 embeded release to the thumb drive, when booting from it
I got the blinking cursor of death, so I replaced the mbr with the mbr found on
freebsd 8.0-RELEASE-i386-bootonly.iso /boot/mbr with a hexeditor then I was
able to boot and get to the config network interfaces screen.

you can also decompress the embeded image and delete the first 32,256 bytes
from the image and write it to your drive, which seems to work also.