I have solved the problem. The Access Points are new ones and therefore they had the same IP-Adresses. I had to change the IP-Addresses.

It sounds as if you have a number of wireless routers connected to the LAN port of a number of pfSense boxes through a LAN port on the wireless routers. Is that correct?

Please give more details on "connections to the internet will cease to work": connections from wireless clients? If so, can wireless clients access the wireless router? the pfSense box?

@nez:

Also the boxes cannot grab the ipaddress from the modem unless you refresh them a few times.

Which modem? I expect the wireless boxes would be asking pfSense to give them an IP address.

A selection of recent snapshot builds can be found by following the appropriate architecture link from http://snapshots.pfsense.org/ then the appropriate build type link.

If you are running the "full" version you can download a "full update" file (e.g. pfSense-Full-Update-2.1-BETA0-i386-20120918-2019.tgz) then uploading it to your pfSense box in a "manual" firmware update. It would be a good thing to save your pfSense configuration file BEFORE the firmware upgrade.

Oh ok thanks that make sense.

Well i dont know why that happened, i was using putty. here is a copy from a ssh connection on linux box.

<interfaces><wan><enable><if>ue0</if>
                        <ipaddr>dhcp</ipaddr>
                        <gateway><media><mediaopt></mediaopt></media></gateway></enable></wan>
                <lan><enable><if>msk0</if>
                        <ipaddr>10.0.0.1</ipaddr>
                        <subnet>24</subnet>
                        <media><mediaopt></mediaopt></media></enable></lan>
                <opt1><if>ath0</if>
                        <wireless><standard>11g</standard>
                                <mode>bss</mode>
                                <protmode>off</protmode>
                                <ssid>MASON-SECURE</ssid>
                                <channel>0</channel>
                               <authmode></authmode>
                                <txpower>99</txpower>
                                <distance><regdomain><regcountry><reglocation><wpa><macaddr_acl></macaddr_acl>
                                        <auth_algs>1</auth_algs>
                                        <wpa_mode>2</wpa_mode>
                                        <wpa_key_mgmt>WPA-EAP</wpa_key_mgmt>
                                        <wpa_pairwise>CCMP TKIP</wpa_pairwise>
                                        <wpa_group_rekey>60</wpa_group_rekey>
                                        <wpa_gmk_rekey>3600</wpa_gmk_rekey>
                                        <passphrase><ext_wpa_sw></ext_wpa_sw>
                                        <ieee8021x><enable></enable></ieee8021x>
                                        <enable></enable></passphrase></wpa>
                                <auth_server_addr><auth_server_port><auth_server_shared_secret><auth_server_addr2><auth_server_port2><auth_server_shared_secret2></auth_server_shared_secret2></auth_server_port2></auth_server_addr2></auth_server_shared_secret></auth_server_port></auth_server_addr></reglocation></regcountry></regdomain></distance></wireless>
                        <alias-address><alias-subnet>32</alias-subnet>
                        <spoofmac><enable><ipaddr>dhcp</ipaddr>
                        <dhcphostname></dhcphostname></enable></spoofmac></alias-address></opt1></interfaces>

ok got it thank you guys for the reply your a big help i will try to see if my card is supported by pfsense, actually what i did was my pfsense wan is connected on the main router which is from our service provider then another 24 port switch is connected to the lan port of pfsense then i installed a wireless card on pfsense box so what i am trying to aim is to make my pfsense box is to work as firewall for lan and be an access point that all my computers connected to switch which is connected to pfsense lan be linked to my wireless card which is also installed on the same pfsense box. because now i have my lan and wireless having internet connection but i noticed this two cannot link together.

thank you

native language arabic

Sorry…forgot to update the thread. Yes that totally works. thank you all for the feedback.

He's asking to help the heroes, so, how can we help you Bob?  :D
Ilham, i think you have to connect your Nanostation (configured as an access point) to one of the NIC on the computer where you have installed PFSense, then with another wire, you have to make sure that this computer(on his second NIC) is receiving the internet(WAN) from your HUB, then you can connect your laptop wireless to the Nanostation or use a wire to the hub if you don't want to use the wi-fi.

teh card recognized in pfsense, but there werent wireless parameters to setup….

@doremi:

Oh gosh. So I got my phone and laptop to connect to it, but there's no internet. I re-configured my pfSense to what is shown on the pfSense documents. Am I doing this wrong? Maybe I was mistaken, but I can't just turn my laptop into a WiFi router? Am I able to turn it into a repeater, maybe? I'm renting a downstairs/basement and the WiFi isn't great here. I thought since I have a spare laptop it could be of use to strengthen my WiFi instead of going out to buy a reapeater or something.

):

You still haven't revealed how you expect your pfSense to connect to the Internet: over a Ethernet cable to a WiFi router upstatirs? Over a WiFi link to a Wifi Router upstairs? Over a 3G link to the mobile phone network? Over a taut string between two tin cans? Magic? I would recommend the first option

You can have pfSense act as WiFi router or a WiFi "repeater" or a number of things, but you may have to add particular interfaces to the laptop to get it to do what you want.

@bman212121:

That is a great little chart they have going there. If you toss aside the WAN to LAN benchmarks as they don't mean anything for using the routers as APs, you'll see that most of the devices cannot break 100mbps over wifi regardless of what settings are used.

Still relevant to some degree, because WLAN to LAN is also handled by the firmware on the device, not just WAN to LAN, and thus depends on CPU speed and efficiency of the code in the firmware.  The latter is relevant on some devices.  For example, on one device I have it could only get about 65 Mbps over the wireless on the stock firmware and a little over 100 Mbps with a more current open source alternative.

@wallabybob:

From the file of PCI identification codes distributed with Ubuntu 12.05 this device:
@rsagris:

none2@pci0:4:0:0: class=0x028000 card=0x13018086 chip=0x00828086 rev=0x34 hdr=0x00
    class      = network

Is a Centrino Advanced-N 6205 AGN
The current source code for the iwn driver should recognise this device, but the device id is not in the table of supported devices in FreeBSD 8.1 (so not in pfSense 2.0.x), nor in FreeBSD 8.2. It is in the table of supported devices for FreeBSD 9.0 and for FreeBSD 8.3 (and hence pfSense 2.1). pfSense 2.1 is not yet released but snapshot builds are available from http://snapshots.pfsense.org.

If you install (or upgrade firmware to) a snapshot build of pfSense 2.1 you will need to add it to the pool of devices pfSense uses by going to Interfaces -> (assign) and clicking on the "+" at the bottom right of the page.

Thanks for the help, I'll re-install later tonight!

I am resurrecting an old thread here, but it seems to be one of the only references out there to the problem I am having.

I have installed pfSense on an HP Mini 1154NR with a Broadcom wireless card installed. I copied the firmware to the /boot/kernel folder and the boot/firmware folder and made the permissions match using chmod.

When I run the command "kldload /boot/kernel/bwn_v4_lp_ucode.ko" I get this error:

Jul 19 18:51:14 pfSense kernel: firmware_register: cannot register image bwn_v4_lp_lp0initvals14, firmware table full! Jul 19 18:51:14 pfSense kernel: module_register_init: MOD_LOAD (bwn_v4_lp_ucode_fw, 0xc5365e70, 0) error 6

It appears from other postings that raising the default value of the FIRMWARE_MAX setting in the subr_firmware.c file and then recompiling the kernel image esolves this problem, but that is well above my skill level at this moment.

Perhaps the OP and myself have overlooked something and are making this too difficult?

Tom

@jimp:

Status > Wireless shows available access points within range.

We don't yet have a "connect" button on that page, though, I don't think.

Thanks! That is exactly what I had in mind. I am surprised I missed it because I have spent some hours already messing around with pfSense and looking around the menus.  It is great to know that the wifi adapter does indeed "see" the wireless network I am trying to connect to.

The login dialogue for pfSense user admin confuses scp. Use another pfSense user OR login to pfSense and "pull" the file to pfSense rather than "push" it OR use the Upload function in pfSense web GUI Diagnostics -> Command Prompt.

@AudiAddict:

I found a setting to do it manualy (dev.ath.0.diversity) but not sure where to check the current setting(s) and where to change this?

The settings dev.ath.0.diversity are for a different type of device (ath) than the one you are using (run).

@markuhde:

I know this doesn't make as neat of installation for you, but honestly, the best solution is to use a separate AP.

I am leaning toward this as well. I have had nothing but problems with wireless cards. USB wireless cards, i tried 3 or 4 makes/models and none were supported /detected. Even PCI cards are really flaky.. A friend told me its because most cards are not designed to work as an AP. With cheap access points available sometimes on craigslist, its a nice option to just go with the tried and true wired ap. As an aside, pfsense as a wireless AP use to work with an old nic card i had, but that card died. Was generic no name funny enough.

I am using 1.2.3 though so perhaps usb nics are now supported and or work.

right now my personal card has an annoying problem where every 15 minutes or so it starts into this "auth" "deauth" cycle and pretty much just doesnt connect till an interface disable /reenable.  annoying to say the least. So for 40$ you cant go wrong with an old cisco ap is what im beginning to think. as fun as screwing around with my wireless interfaces are….