@coyote: manual connect through the blackberry? = yes did you try both the 2.4Ghz and 5? = my pfsense router or rather my stick support only 2.4GHz did you try setting G only in the router? = yes, you can select only between 11b and 11g I also set my playbook with a static IP; that should at some routers help to a persistent connection: no chance. Next, I want to try one or two different sticks with different chipsets. the techniclan usb stick was with rt2870 + rt3070. If that doesnt help, then I'll leave as it is, without wlan. I dont want a 3rd box for the internet. Which router do you have now? I see.. I have a Buffalo WZR-300HP2..I bought a couple of these..and they have been great..it comes with DDWRT in it..in fact I was just actually talking to an employee who affirms that opening applications that require SQL was faster under the old setup (Buffalo)..now I have everything here running on PFsense. At home my playbook didnt like the Buffalo but blackberry did an upgrade and it worked perfectly without having to tweak the settings..But going back to rt2870, I have had similar usb sticks before with Ralink and it is a hit and miss type of thing…I always have good luck with Atheros they just seem to work in my setups and actually buffalo is atheros at least on this one

On the pfSense Wifi interface add a firewall rule to allow access to the printer and to block access to the LAN. Firewall rules are processed top down until the first match.

Just because a card supports multiple bands doesn't mean it actually has multiple radios on it. I've not had my hands on any cards that might actually have two radios so I'm not sure how they "look" to the OS. With VAPs, the channel must be identical for each entry, at least last I knew. There may be some work that improved that in cards that have multiple radios, but it wouldn't be supported in our GUI just yet.

@rekd0514: I assume the SSID should be the name of the hotspot AP. Is that right? In pfSense the wireless interface SSID should be the WiFi network name configured in the hotspot. This might not be the same as the name of the hotspot AP. @rekd0514: Also should the IP address assigned to the wireless interface be within my DHCP server range? The pfSense interface type should be set to DHCP to get configuration information from the AP.

Two that were suggested to me were http://www.ubnt.com/unifi#UnifiHardware and http://www.engeniustech.com/networking/productsdatacom/business-networking/indoor-access-points-client-bridges I didn't go for either one but bought a cheap refurb Dlink 1525 with switchable bands, well worth $20 but not a penny more. I've got to find something else before I do any serious WiFi use.

Unfortunately that's sort of the state of using VAPs. Some cards do support 4+ virtual APs but you don't know if you've exceeded your card's limit until the driver panics. I'm not sure if the driver behaves better on 2.1 for that or not. Possible, but without some conclusive testing, it's hard to say. Usually Atheros cards support 4 VAPs.

I do not know Linux very well but perhaps this could help you: http://uellue.de/blog/single.php?date=1180101420 http://www.rinta-aho.org/docs/wlan/wlan.html

If you want to save yourself time and headaches, forget about wifi cards to use directly in pfSense. Get an external AP and connect it to a new interface or VLAN on your pfsense box and manage the access rules on the FW. I did the same at home and it works great: http://forum.pfsense.org/index.php/topic,59799.0.html

@stan-qaz: Sorry I can't help with the card, I usually just hook a cheap router up on the LAN side and connect to its LAN ports after disabling DHCP. Saves fussing with compatibility and lets me put it where I need the signal too. I do thank you for the help, and that's a smart idea….that I quickly thought about as a work around....till I realized not possible because I only have one eth NIC then I thought about routing statements....but that idea was tossed when I realized that doesn't help either...since I am trying to remove this $40 dollar netgear that I hate oh so much, being a person who loves Cisco with all his heart can't quite stand to have anything else, unless of course he makes one himself.....sounds weird refereeing to myself in the third person. (sigh) thank you sir for your help.

@patrick2le: I am looking for driver for airlink AWLH3028 802.11g on pfsense (freebsd) As best I have been able to discover that device uses an unsupported Realtek chipset. If this is a PCI or PCI-Express device then please provide the output of pfSense shell command``` pciconf -l If you are looking to get something going quickly you would probably be better off getting a card with a supported chipset (e.g. a suitable Atheros version).

Thought: I can add a nic card to the pfsense box itself… :) I will need a SFF card to fit. I think I will research this option.

1. Do you think your card has a supported chipset? If so, why do think that? 2. If the chipset is supported then you shouldn't need to do anything special to load the drivers because the kernel has (or will have) drivers for all supported chipsets. 3. If the chipset is supported then you will need to click on the "+" button on the buttom right of the pfSense Interfaces -> (assign) page to add the interface to the pool of interfaces used by pfSense. Please post the output of the pfSense shell commands``` dmesg ; pciconf -l

fthomasr: Cool!  Yeah I have one set up at my office now this way.  Works good for me, I just wire to the router/nearby switch, (no wifi from my laptop). Watch out for virtual interfaces on the same WiFi adapter.  When I tried to make an AP it (with the BSS bridge),  The Atheros I am using gets stuck on loading the interface during the boot sequence, bricking the router essentially.  Heads up anyways. Hopefully that gets worked on someday too. @fthomasr: Ok so I took my lab router over to the site and it also could not connect to the WRT54GL no matter what WiFi security settings I tried(also DHCP or Static), despite being associated each time. I upgraded to 2.1 beta and tried DHCP. Just as wm408 no connection either. Also just as wm408 found the connection worked only with a static. This was fine for me as that's what I wanted in the end. Thanks wm408 for starting this thread and posting your findings. It was helpful for me.

I wrote I did it twice First time Wireless interface was not enabled The second time the wireless interface was enabled fxp0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=9 <rxcsum,vlan_mtu>ether 00:09:6b:d1:03:04 inet6 fe80::209:6bff:fed1:304%fxp0 prefixlen 64 scopeid 0x1 nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active dc0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=80008 <vlan_mtu,linkstate>ether 00:80:ad:73:b7:fe inet6 fe80::280:adff:fe73:b7fe%dc0 prefixlen 64 scopeid 0x2 nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (none) status: no carrier fxp1: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500 options=2008 <vlan_mtu,wol_magic>ether 00:02:b3:0b:ab:2e inet6 fe80::202:b3ff:fe0b:ab2e%fxp1 prefixlen 64 scopeid 0x3 nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active pflog0: flags=100 <promisc>metric 0 mtu 33200 enc0: flags=0<> metric 0 mtu 1536 lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384 options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 nd6 options=43 <performnud,accept_rtadv>pfsync0: flags=0<> metric 0 mtu 1460 syncpeer: 224.0.0.240 maxupd: 128 syncok: 1 run0: flags=8902 <broadcast,promisc,simplex,multicast>metric 0 mtu 2290 ether 54:e6:fc:93:bf:57 media: IEEE 802.11 Wireless Ethernet autoselect <hostap>(autoselect <hostap>) status: no carrier pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492 inet 109.226.48.72 --> 109.226.1.20 netmask 0xffffffff inet6 fe80::209:6bff:fed1:304%pppoe0 prefixlen 64 scopeid 0x9 nd6 options=43 <performnud,accept_rtadv>run0_wlan0: flags=8902 <broadcast,promisc,simplex,multicast>metric 0 mtu 1500 ether 54:e6:fc:93:bf:57 inet6 fe80::56e6:fcff:fe93:bf57%run0_wlan0 prefixlen 64 scopeid 0xa nd6 options=43 <performnud,accept_rtadv>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: no carrier ssid "bla bla bla" channel 2 (2417 MHz 11g) regdomain NONE country IL authmode AUTO privacy OFF deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 30 scanvalid 60 pureg protmode OFF wme -apbridge dtimperiod 1 -dfs bridge0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 ether 02:11:79:20:3d:00 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: fxp1 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 3 priority 128 path cost 200000 member: run0_wlan0 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 10 priority 128 path cost 370370</learning,discover,autoedge,autoptp></learning,discover,autoedge,autoptp></up,broadcast,running,simplex,multicast></hostap></performnud,accept_rtadv></broadcast,promisc,simplex,multicast></performnud,accept_rtadv></up,pointopoint,running,noarp,simplex,multicast></hostap></hostap></broadcast,promisc,simplex,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></promisc></full-duplex></performnud,accept_rtadv></vlan_mtu,wol_magic></up,broadcast,running,promisc,simplex,multicast></performnud,accept_rtadv></vlan_mtu,linkstate></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,vlan_mtu></up,broadcast,running,simplex,multicast> And the second time fxp0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=9 <rxcsum,vlan_mtu>ether 00:09:6b:d1:03:04 inet6 fe80::209:6bff:fed1:304%fxp0 prefixlen 64 scopeid 0x1 nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active dc0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=80008 <vlan_mtu,linkstate>ether 00:80:ad:73:b7:fe inet6 fe80::280:adff:fe73:b7fe%dc0 prefixlen 64 scopeid 0x2 nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (none) status: no carrier fxp1: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500 options=2008 <vlan_mtu,wol_magic>ether 00:02:b3:0b:ab:2e inet6 fe80::202:b3ff:fe0b:ab2e%fxp1 prefixlen 64 scopeid 0x3 nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>) status: active pflog0: flags=100 <promisc>metric 0 mtu 33200 enc0: flags=0<> metric 0 mtu 1536 lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384 options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 nd6 options=43 <performnud,accept_rtadv>pfsync0: flags=0<> metric 0 mtu 1460 syncpeer: 224.0.0.240 maxupd: 128 syncok: 1 run0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 2290 ether 54:e6:fc:93:bf:57 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: running pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492 inet 109.226.48.72 --> 109.226.1.20 netmask 0xffffffff inet6 fe80::209:6bff:fed1:304%pppoe0 prefixlen 64 scopeid 0x9 nd6 options=43 <performnud,accept_rtadv>run0_wlan0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500 ether 54:e6:fc:93:bf:57 inet6 fe80::56e6:fcff:fe93:bf57%run0_wlan0 prefixlen 64 scopeid 0xa nd6 options=43 <performnud,accept_rtadv>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: running ssid "bla bla bla" channel 3 (2422 MHz 11g) bssid 54:e6:fc:93:bf:57 regdomain NONE country IL authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 30 scanvalid 60 pureg protmode OFF wme -apbridge dtimperiod 1 -dfs bridge0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 ether 02:11:79:20:3d:00 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: fxp1 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 3 priority 128 path cost 200000 member: run0_wlan0 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 10 priority 128 path cost 370370</learning,discover,autoedge,autoptp></learning,discover,autoedge,autoptp></up,broadcast,running,simplex,multicast></hostap></performnud,accept_rtadv></up,broadcast,running,promisc,simplex,multicast></performnud,accept_rtadv></up,pointopoint,running,noarp,simplex,multicast></hostap></up,broadcast,running,simplex,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></promisc></full-duplex></performnud,accept_rtadv></vlan_mtu,wol_magic></up,broadcast,running,promisc,simplex,multicast></performnud,accept_rtadv></vlan_mtu,linkstate></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,vlan_mtu></up,broadcast,running,simplex,multicast>

FYI if anyone is interested. I use "Fing" on my droid to interrogate my networks. does just about everything, all from my smart phone. list all IPs and MAC addresses. I can even login into my router from within "Fing"

Now I blocked the wireless option No one has the password And now it is still crashes and restarts this is Crash report  with out wireless Crash report begins.  Anonymous machine information: i386 8.1-RELEASE-p13 FreeBSD 8.1-RELEASE-p13 #1: Fri Dec  7 16:55:26 EST 2012    root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 Crash report details: Filename: /var/crash/bounds 4 Filename: /var/crash/info.0 Dump header from device /dev/ad0s1b   Architecture: i386   Architecture Version: 1   Dump Length: 71168B (0 MB)   Blocksize: 512   Dumptime: Sun Feb 24 12:16:09 2013   Hostname: pfsense.zohar.co.il   Magic: FreeBSD Text Dump   Version String: FreeBSD 8.1-RELEASE-p13 #1: Fri Dec  7 16:55:26 EST 2012     root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8   Panic String:   Dump Parity: 180370485   Bounds: 0   Dump Status: good Filename: /var/crash/info.1 Dump header from device /dev/ad0s1b   Architecture: i386   Architecture Version: 1   Dump Length: 69632B (0 MB)   Blocksize: 512   Dumptime: Sun Feb 24 12:17:39 2013   Hostname: pfsense.zohar.co.il   Magic: FreeBSD Text Dump   Version String: FreeBSD 8.1-RELEASE-p13 #1: Fri Dec  7 16:55:26 EST 2012     root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8   Panic String:   Dump Parity: 2697346101   Bounds: 1   Dump Status: good Filename: /var/crash/info.2 Dump header from device /dev/ad0s1b   Architecture: i386   Architecture Version: 1   Dump Length: 69632B (0 MB)   Blocksize: 512   Dumptime: Sun Feb 24 12:19:06 2013   Hostname: pfsense.zohar.co.il   Magic: FreeBSD Text Dump   Version String: FreeBSD 8.1-RELEASE-p13 #1: Fri Dec  7 16:55:26 EST 2012     root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8   Panic String:   Dump Parity: 2043100213   Bounds: 2   Dump Status: good Filename: /var/crash/info.3 Dump header from device /dev/ad0s1b   Architecture: i386   Architecture Version: 1   Dump Length: 70656B (0 MB)   Blocksize: 512   Dumptime: Sun Feb 24 12:29:32 2013   Hostname: pfsense.zohar.co.il   Magic: FreeBSD Text Dump   Version String: FreeBSD 8.1-RELEASE-p13 #1: Fri Dec  7 16:55:26 EST 2012     root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8   Panic String:   Dump Parity: 4022418485   Bounds: 3   Dump Status: good Filename: /var/crash/textdump.tar.0 ddb.txt���������������������������������������������������������������������������������������������0600����0�������0�������140000������12112364151�  7066� �����������������������������������������������������������������������������������������������������ustar���root����������������������������wheel������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������db:0:kdb.enter.default>  run lockinfo db:1:lockinfo> show locks No such command db:1:locks>  show alllocks No such command db:1:alllocks>  show lockedvnods Locked vnodes db:0:kdb.enter.default>  show pcpu cpuid        = 0 dynamic pcpu    = 0x51d080 curthread    = 0xc499bc80: pid 0 "run0 taskq" curpcb      = 0xeab3ad90 fpcurthread  = none idlethread  = 0xc4590a00: pid 11 "idle: cpu0" APIC ID      = 0 currentldt  = 0x50 db:0:kdb.enter.default>  bt Tracing pid 0 tid 64063 td 0xc499bc80 run_drain_fifo(c49cb000,c499bc80,0,0,0,…) at run_drain_fifo+0x5f run_ratectl_cb(c49cb000,1,0,c12d0b3c,0,...) at run_ratectl_cb+0x5c taskqueue_run(c486bb80,c486bb98,0,c0ede918,0,...) at taskqueue_run+0x89 taskqueue_thread_loop(c49d7074,eab3ad38,0,0,0,...) at taskqueue_thread_loop+0x45 fork_exit(c0a7a1a0,c49d7074,eab3ad38) at fork_exit+0x88 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xeab3ad70, ebp = 0 --- db:0:kdb.enter.default>  ps   pid  ppid  pgrp  uid  state  wmesg    wchan    cmd 34986 21030  249    0  S      nanslp  0xc133ea24 sleep 4549 33950    25    0  S      nanslp  0xc133ea24 sleep 1278 17458 17458    0  S      piperd  0xc4a03930 rrdtool 51494    1 51494    0  Ss      select  0xc4c79624 ntpd 21030    1  249    0  S      wait    0xc4e797f8 sh 17458    1 17458    0  Ss      select  0xc49fee24 apinger 41116 39984 41116    0  S+      ttyin    0xc45e1c70 sh 39984 39656 39984    0  S+      wait    0xc4e78d48 sh 39934 12174 39934    0  Ss      (threaded)          sshlockout_pf 64110                  S      nanslp  0xc133ea24 sshlockout_pf 64103                  S      piperd  0xc4a04188 initial thread 39656    1 39656    0  Ss+    wait    0xc4e78550 login 38928 38628 38573    62  S      piperd  0xc4e50188 unlinkd 38628 38573 38573    62  S      select  0xc4c77aa4 initial thread 38573    1 38573    62  Ss      wait    0xc4c74d48 squid 36013 35612 35612    0  S      nanslp  0xc133ea24 minicron 35612    1 35612    0  Ss      wait    0xc49ed7f8 minicron 35318 34760 34760    0  S      nanslp  0xc133ea24 minicron 34760    1 34760    0  Ss      wait    0xc4c742a8 minicron 34496 34291 34291    0  S      nanslp  0xc133ea24 minicron 34291    1 34291    0  Ss      wait    0xc4c737f8 minicron 33950    1    25    0  S+      wait    0xc49f0000 sh 39345    1 39345    0  Ss      nanslp  0xc133ea24 cron 28670    1 28528 65534  S      select  0xc4c78264 dnsmasq 27682    1 27682  1002  Ss      select  0xc4c77e24 dhcpd 21472 19978 19813    0  S      nanslp  0xc133ea24 initial thread 20306 19978 19813    0  S      accept  0xc4aa4512 initial thread 19978    1 19813    0  S      kqread  0xc4acb900 lighttpd 13160    1 13160    0  Ss      select  0xc486a1a4 inetd 12174    1 12174    0  Ss      select  0xc486b864 syslogd 11530    1    25    0  S+      piperd  0xc4a03dc8 logger 11191    1    25    0  S+      bpf      0xc4bc3400 tcpdump 8136    1  8136    0  Ss      select  0xc4991d24 hostapd 5149    1  5149    0  Ss      (threaded)          mpd5 64085                  S      select  0xc49ff3e4 mpd5   264    1  264    0  Ss      select  0xc4990024 devd   251  249  249    0  S      kqread  0xc4a01d00 check_reload_status   249    1  249    0  Ss      kqread  0xc4a01b80 check_reload_status   40    0    0    0  SL      mdwait  0xc49af000 [md0]   24    0    0    0  SL      sdflush  0xc136d480 [softdepflush]   23    0    0    0  SL      syncer  0xc1352594 [syncer]   22    0    0    0  SL      vlruwt  0xc45d5d48 [vnlru]   21    0    0    0  SL      psleep  0xc13522c8 [bufdaemon]   20    0    0    0  SL      pgzero  0xc136e134 [pagezero]   19    0    0    0  SL      pollid  0xc133df7c [idlepoll]   18    0    0    0  SL      psleep  0xc136dd5c [vmdaemon]   17    0    0    0  SL      psleep  0xc136dd24 [pagedaemon]     9    0    0    0  SL      ccb_scan 0xc1308c54 [xpt_thrd]     8    0    0    0  SL      pftm    0xc04f7020 [pfpurge]     7    0    0    0  SL      waiting_ 0xc13599d8 [sctp_iterator]   16    0    0    0  SL      tzpoll  0xc130da8c [acpi_thermal]   15    0    0    0  SL      (threaded)          usb 64045                  D      -        0xc4725d0c [usbus3] 64044                  D      -        0xc4725cdc [usbus3] 64043                  D      -        0xc4725cac [usbus3] 64042                  D      -        0xc4725c7c [usbus3] 64040                  D      -        0xc4711dac [usbus2] 64039                  D      -        0xc4711d7c [usbus2] 64038                  D      -        0xc4711d4c [usbus2] 64037                  D      -        0xc4711d1c [usbus2] 64035                  D      -        0xc46fadac [usbus1] 64034                  D      -        0xc46fad7c [usbus1] 64033                  D      -        0xc46fad4c [usbus1] 64032                  D      -        0xc46fad1c [usbus1] 64030                  D      -        0xc46e5dac [usbus0] 64029                  D      -        0xc46e5d7c [usbus0] 64028                  D      -        0xc46e5d4c [usbus0] 64027                  D      -        0xc46e5d1c [usbus0]   14    0    0    0  SL      -        0xc133e884 [yarrow]     6    0    0    0  SL      crypto_r 0xc136caac [crypto returns]     5    0    0    0  SL      crypto_w 0xc136ca88 [crypto]     4    0    0    0  SL      -        0xc133c124 [g_down]     3    0    0    0  SL      -        0xc133c120 [g_up]     2    0    0    0  SL      -        0xc133c118 [g_event]   13    0    0    0  SL      sleep    0xc12df260 [ng_queue0]   12    0    0    0  RL      (threaded)          intr 64051                  I                          [irq1: atkbd0] 64049                  I                          [irq15: ata1] 64048                  I                          [irq14: ata0] 64047                  I                          [irq22: dc0] 64046                  I                          [irq20: fxp0 fxp1] 64041                  I                          [irq23: ehci0] 64036                  I                          [irq18: uhci2] 64031                  I                          [irq19: uhci1] 64026                  I                          [irq16: uhci0] 64025                  I                          [irq9: acpi0] 64021                  I                          [swi2: cambio] 64020                  I                          [swi6: task queue] 64019                  I                          [swi6: Giant taskq] 64017                  I                          [swi5: +] 64007                  I                          [swi3: vm] 64006                  RunQ                        [swi4: clock] 64005                  I                          [swi1: netisr 0]   11    0    0    0  RL                          [idle: cpu0]     1    0    1    0  SLs    wait    0xc458ed48 [init]   10    0    0    0  SL      audit_wo 0xc136ce20 [audit]     0    0    0    0  RLs    (threaded)          kernel 64063                  Run    CPU 0              [run0 taskq] 64024                  D      -        0xc46a0280 [acpi_task_2] 64023                  D      -        0xc46a0280 [acpi_task_1] 64022                  D      -        0xc46a0280 [acpi_task_0] 64018                  D      -        0xc46a04c0

pfsense>NIC>Wireless Router Wireless router with PFSense = wireless networking Therefore, it is a specific question. A general question would be mor etoward "What routers are best to use for PFSense?" rather than "How do I set up a wireless router with PFSense and configure it?"

@kisw: I have the same chipset (TP LINK WN7200) but nothing happens when I connect the card to USB. How to make it work? Its possible two or more different chipsets are used in the WN7200. What are you expecting to happen? If the device makes electrical connection to the bus and it is a real USB device (not just a battery charger!) then the connection should be reported on the pfSense console and in the output of the pfsense shell command``` dmesg

Wallabybob my bad that I couldnt give you the exact nightly build of Pfsense I am using but I am not at work anymore and wanted to respond to the thread rather than leave it in limbo. I think my PFsense is from last Sunday that would be 2.1 Sunday nightly build

@wallabybob: Without more information it is a bit hard to say what happened. @greenpoise: (Any destination: Not in Type with Lan Subnet) . Presumably you mean: Destination: Not LAN subnet @greenpoise: I also set up my OPT1 as a DHCP Server with range from 192.168.2.6 - 192.168.2.50 (My AP address is 192.168.2.5)..Then, hell broke loose!! Now PFsense does not give me any connection. Connection from where to where? from a computer on LAN port? on OPT1 port? a WiFi client? What sort of connection: png? web page? ssh? etc What was reported on the connection attempt - timeout? unknown host? no route to host? etc @greenpoise: I can access PFsense but there is no internet within. I ping outside from PFsense and it works. No error messages…nothing.. Where did you look for error messages? PERHAPS you didn't reset firewall states after adding the firewall rule for OPT1. See Diagnostics -> States, click on Reset States tab and read. @greenpoise: I disabled my OPT1, deleted my firewall rule of my AP..set everything up as before..and still no internet… Again, without more details (see above for the details it would be helpful to have) it is hard to give an explanation. Nothing you have described has any obvious reason to affect operation on the pfSense LAN network UNLESS you have chosen duplicate or overlapping IP address ranges. Please tell us about your AP - is it a router, a router with network switch, a wireless bridge? In addition to answering the questions above I suggest you take a more step wise approach: 1. You check all your IP subnets have distinct (non overlapping) IP address ranges. If they don't, fix that and reboot pfSense. (I have found it sometmies seems to be necessary to reboot pfSense to clear out memory of old IP subnet assignments.) 2. Save your pfSense configuration. 3. Configure OPT1 (distinct IP address range), configure its DHCP server, enable it, verify you still have access to the internet from a computer on the pfSense LAN interface. 4. Plug in a computer to the pfSense OPT1 interface (cross over cable if necessary) and verify it gets correct DHCP assigned IP address, DNS and gateway. 5. Plug in the AP to the OPT1 interface and verify a computer can associate with the AP and gets an IP address from the correct range and gets correct gateway and DNS. Since I don't know if you are using the AP as a router or WiFi bridge I can't say what the correct values are. If you report back on which step you get to and what happened when you attempted to complete the next step I will try to assist you to get to the next step. My bad for the short description on the problem. I figured it out. Pfblocker was blocking my Opt1. I chose Opt1 as inbound interface and everything worked back to normal