I switched the interfaces from WAN/re1, LAN/re0 to WAN/re0, LAN/re1 and so far no timeouts.  I will continue to monitor.  The kernel panic when booting with ACPI disabled is still worrisome, but I will post that in a different forum.

There is no option for that at the moment on the page for configuring the wireless interface, but you could change the script to add the parameter.  In /etc/inc/interfaces.inc go to the bottom of the interface_wireless_configure function.  There you should see this: /* configure wireless */ $wlcmd_args = implode(" ", $wlcmd); mwexec("/sbin/ifconfig {$if} $wlcmd_args", false); Before the $wlcmd_args = implode(" ", $wlcmd); line you can add ifconfig parameters to $wlcmd.  If you only have one wireless interface assigned you could change it to this (replace your_ap_mac_here with the AP MAC, with colons as the separator): /* configure wireless */ $wlcmd[] = "bssid your_ap_mac_here"; $wlcmd_args = implode(" ", $wlcmd); mwexec("/sbin/ifconfig {$if} $wlcmd_args", false); If you have multiple wireless interfaces, you could do something like this (assuming ath0 is the assigned interface for the example): /* configure wireless */ if ($if == "ath0_wlan0") $wlcmd[] = "bssid your_ap_mac_here"; $wlcmd_args = implode(" ", $wlcmd); mwexec("/sbin/ifconfig {$if} $wlcmd_args", false);

The iPad has one of the worst WiFi antennas I have seen in a device.  It's rang is very limited; even my iPhone can get a signal when my iPad can't.

The driver for the chipset reported to be in the current generation of the WN321G supports Access Point mode. The driver for the chipset in the previous generation of the WN321G supports Access Point mode. Access Point mode is when a WiFi station controls conversation with a number of WiFi clients (which then operate in Infrastructure mode).

@abby: Can I use a USB based pfsense that would detect my wireless card? You are planning to run this on bare metal or in a Virtual Machine? @abby: I tried downloading the pfSense-2.0-RELEASE-4g-i386-nanobsd_vga.img.gz and copied the pfSense-2.0.1-RELEASE-1g-i386-nanobsd_vga.img to a flash drive but my machine would not boot with it. How did you copy it to the flash drive? Can you provide more detail than "my machine would not boot with it"? Do you want the machine to act as a wireless Access Point or to connect to a wireless Access Point? The Intel card you have doesn't appear to be supported and I suspect you will save yourself a lot of time messing around with the windows drivers if you bought a supported $15 USB WiFi NIC, but I would need to know more about how you want to use it before I'm prepared to suggest one.

Can you use the W322UA as an Access Point? If so, configure it that way before enabling.

@dale58: An 192.168.2.0/23 for example has valid IP range of 192.168.2.1 - 192.168.3.254 192.168.2.0 is the [b]NetID[/b] 192.168.0.255 is the Broadcast IP. OK, sorry to nitpick this but if this is truly a 'super-net' of two class C addresses, then the Broadcast address would be 192.168.3.255 not 192.168.0.255.  I've heard this called a sub-net of a Class B range or a super-net Class C.  Either way you're getting 510 addresses together.  Please note that I have seen many of these and "ALWAYS" block (remove) the .254 & .0 addresses (ie: 192.168.2.254 and 192.168.3.0) from DHCP so they are not assigned to devices.  Too many times I've run across these addresses and the workstation will not correctly route traffic.  Troubleshooting this the first time is no fun. Of course it's 192.168.3.255 that's the BC. I wrote that wrong ;) You're doing it right on the DHCP. Limit the scope a bit is always a good idea.

Ok, I've updated the stick with a new firmware and now it seems so that i get connected. Next problem is, that I don't get an ip-adress. What could be the reason for this? Mar 19 13:37:19 ppp: [opt2_link0] LCP: authorization successful Mar 19 13:37:19 ppp: [opt2_link0] Link: Matched action 'bundle "opt2" ""' Mar 19 13:37:19 ppp: [opt2_link0] Link: Join bundle "opt2" Mar 19 13:37:19 ppp: [opt2] Bundle: Status update: up 1 link, total bandwidth 28800 bps Mar 19 13:37:19 ppp: [opt2] IPCP: Open event Mar 19 13:37:19 ppp: [opt2] IPCP: state change Initial –> Starting Mar 19 13:37:19 ppp: [opt2] IPCP: LayerStart Mar 19 13:37:19 ppp: [opt2] IPCP: Up event Mar 19 13:37:19 ppp: [opt2] IPCP: state change Starting –> Req-Sent Mar 19 13:37:19 ppp: [opt2] IPCP: SendConfigReq #1 Mar 19 13:37:19 ppp: [opt2] IPADDR 0.0.0.0 Mar 19 13:37:19 ppp: [opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Mar 19 13:37:19 ppp: [opt2] PRIDNS 0.0.0.0 Mar 19 13:37:19 ppp: [opt2] SECDNS 0.0.0.0 Mar 19 13:37:21 ppp: [opt2] IPCP: SendConfigReq #2 Mar 19 13:37:21 ppp: [opt2] IPADDR 0.0.0.0 Mar 19 13:37:21 ppp: [opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Mar 19 13:37:21 ppp: [opt2] PRIDNS 0.0.0.0 Mar 19 13:37:21 ppp: [opt2] SECDNS 0.0.0.0 Mar 19 13:37:23 ppp: [opt2] IPCP: SendConfigReq #3 Mar 19 13:37:23 ppp: [opt2] IPADDR 0.0.0.0 Mar 19 13:37:23 ppp: [opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Mar 19 13:37:23 ppp: [opt2] PRIDNS 0.0.0.0 Mar 19 13:37:23 ppp: [opt2] SECDNS 0.0.0.0 Mar 19 13:37:25 ppp: [opt2] IPCP: SendConfigReq #4 Mar 19 13:37:25 ppp: [opt2] IPADDR 0.0.0.0 Mar 19 13:37:25 ppp: [opt2] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Mar 19 13:37:25 ppp: [opt2] PRIDNS 0.0.0.0 Mar 19 13:37:25 ppp: [opt2] SECDNS 0.0.0.0

Ok, this issue has been solved, i am now going to try to understand how the captive portal thing works, thank you all for your time  ;D

No problem with pfSense 2.1 snapshot builds… ! Are there any release date for pfsense 2.1 ? Thank you for your solution.

The DWA-510 appears to be a PCI card using the Ralink RT-2561 chipset so it should be controlled by the FreeBSD ral driver. What version of pfSense are you using? What exactly do you mean by "can't connect"? Can't connect to the Internet but have IP address from DHCP? Don't get IP address from DHCP? Don't get ping response from modem?  . . . etc What variant of WPA Pairwise were you trying - TKIP or AES? (One of my WiFi clients didn't associate if I selected TKIP on the AP but did if I selected AES).

Hi, and thanks for you reply (Eller tack, eftersom jag vet att du hänger på Swec, eh, rätt mycket). I actually baught one, but it wouldn't coop with my ESXi host, since it showed up that it would share the same PCI bus as my graphics card - hence ESXi wouldn't boot correctly so it wouldn't do. So what I do need is a networks card that supports multiple SSID on a PCI-express connection. Any ideas? Thanks! Zyber

I split this post off since it wasn't really related to the old thread (similar behavior but it's a different driver) and it wouldn't get much attention in an old thread. This is probably because that specific card doesn't support multiple access points. Unfortunately there isn't a way to probe the cards to test support, only to try and fail (spectacularly in this case). If there is any bug, it's a driver bug, and there isn't likely to be anything we can do for that. We are working on getting pfSense 2.1 out, and it will be based on FreeBSD 8.3, so there is some hope that it will be improved there. That said, if it's just lack of support in the chip, it may still panic, and there may be nothing we can do for that.

@SlowGrind: Try this link… http://forum.pfsense.org/index.php/topic,13427.0.html *.ko files download link broken. @wallabybob legal.intel_ipw.license_ack=1 legal.intel_wpi.license_ack=1 i ll added because system reports give the errors. how to find iwi_bss.ko, iwi_ibss.ko and iwi_monitor.ko files or how to install new firmware ?

@Efonne: "Settings apply to all wireless networks on (device name here)." was a bit tired methinks… Thanks!

There is no driver that wants to control the card: pci2: <network>at device 0.0 (no driver attached)</network> The wireless PCI cards I have been using seem to be no longer available (retail) and at least one user has reported trouble with the natural successor. Some users seem to have had success with cards based on Atheros chipsets rather than Ralink. 802.11n is not yet supported in pfSense but some Atheros 802.11n capable cards are reported to work in 802.11g mode.

Compex WLM54SAG23 (AR5414) works great since more than a year ago. No crashes. Haven't used cloned interfaces (yet) though.