I'll try the VPN. If the wiki isn't enough, I'll came back to the forum. ;D

O.K. im came back I had a power problem in the AP I have 192.168.42.x for the lan interface and 192.168.54.x for the wi1 interface the first picture is the firewall rule the second is ifconfig command the Third is Divided to tow the upper is in the wifi pfsense net and the lower is in other wifi you can see that i can ping google thank you all eli :) [image: Terminal-ifconfig.png] [image: Terminal-ifconfig.png_thumb] [image: Terminal-ping.png] [image: Terminal-ping.png_thumb]  

My knowledge about networking is really low.I know some things on theory and practical simple things just what is dhcp,How to config network on my bsd machine or connect 2 computers together.The reason i start pfsense is because i want to learn about firewalls,networks and because i really like pfsense and more general because i like computers very much and allways trying to learn more things setting projects on my self.Is not only to set up a firewall.Is to learn from this experience.But is really to hard for me to understand all this at this point.So to read some things before i start,i think is really good idea :) Thanks for the urls.I will start reading immediately :) George

If your web user reads pages out of the cache then the speed at which they can read that data may be limited by the disk read speed or it may be limited by the available network bandwidth between them and the system holding the cache. For example, your disk might be capable of reading at 100MBps (800Mbps) and you may have a 100Mbps link between the user and the cache. That configuration is limited by the network. In practice, I expect that for a small number of users no-one is likely to notice.

I remove completely hdd drive and i put a flash.Boot from cd and make the install on flash.Now it is working!!!! :)

Did that IDE disk have anything on it previously? It may need a complete zero wipe to be sure nothing left on it is causing an issue. Or try some of the other suggestions here: http://doc.pfsense.org/index.php/Boot_Troubleshooting

It may have needed the whole disk wiped then. # dd if=/dev/zero of=/dev/ad0 bs=1M

With PF V.2.0 ==> installation is OK: The name of the eth card  is "Marvell Technology Group Ltd  Yukon Ultra 2 Id 0xba Rev 0x00" but Captiveportal isn't working. Thanks

@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