If your  wired and wireless clients are on the same IP subnet, that's what you want.

@Nanafriend:

As far as I know WPA2 isn't the best way to go as many other wireless adapters are not compatible with it.  I read several times that there isn't any difference between WPA and WPA2, at least in turns of cracking.  You want to use WPA - Pre shared key(psk), with tkip only.

Don't use TKIP at all anymore, it is crackable (or close to it, Google for recent info on this). WPA with AES is fine, and WPA2 works on almost everything. Some laptops with XP may not work with WPA2 unless the wireless card manufacturer provides software that supports it.

Yes

Search this forum for more help.  Compatible cards and setup.

"to a small camping were they use wireless 3*AP (linksys wrt-54gl),"  I am not sure I understand the scenario but it likely doesn't matter.  You are attempting to make the pfsense box the primary router and then make the others… simple wireless access points?  The 'best' option is to run cat5e or cat6 rj-45 cables to and from each one.  I don't really understand why you feel the need to fulfill this idea exactly.  I doubt you can monitor all of what goes on inside of each of those boxes but you can likely check out everything that goes on inside of your pfsense box using squid and Bandwidthd.  From what I see in Bandwidthd it shows you exactly what happens with each individual IP and subnet and all that.  It is a pretty deep program it seems like.  If your pals won't listen to you when you say, 'no torrents' for whatever reason, then just yank their wire and put it at that.  Or you can use the traffic shaper to disable torrents or even all P2Ping.  Traffic shaper is under the firewall tab, 5th down.  I don't understand what  "I have thought of a text in the beginning of your site, and dont it," means.  I assume you mean like.. alix boards or something, you won't be able to use your current settings, everything will be fresh and new and I think there are several limitations versus going the full X86 route with a hard drive.

@df:

Hi Ktims,

I'm also using Alix and therefore i must ask, would you mind sharing your kernel config ?
I have to admit i'ld like to make some use of the LED support too ;)

Ps: Is there any chance to see the LED support added to the current pfsense kernel config ?

Sure. I have been experiencing some freezes when mucking in Advanced Options in the webUI, so I'm not going to vouch for the stability of my kernel, but that could easily be (and probably is) something else. I haven't had a chance to hook up a serial console and see what's happening.

config
tarball of /boot/kernel

It's based on 7.0-RELEASE. I have added the content of src/sys/dev/glxsb to the kernel tree and modified src/sys/conf/files.i386 to include the lines that reference those files so it will compile. That gets you hardware cryptodev. I have also copied src/sys/i386/i386/geode.c from HEAD. That gets you /dev/led support. If all you're interested in is LED support I would grab the pfSense-embedded kernel config linked above by lsf (you might need an older revision, I couldn't find where IPSEC_NAT_T and ALTQ_FAIRQ where coming from, they don't seem to be in 7.0) and build it with the replaced geode.c and no other changes.

I based my changes on this article by Kvedulv.

lol, I think this thread needs to be put out of it's misery. I don't think anyone is getting anything out of this. ;)

My wifi works for days in bridge mode, but eventualy no wireless clients can connect, stuck at authentication. When I don't use the bridge everything keeps working fine.

Backend only, you can modify the hostadp config generated from pfsense to allow such use.

The file in question is /etc/inc/interfaces.inc (look for function interfaces_wireless_configure) and edit the config section that comes after:

                case 'hostap':                         if (isset($wlcfg['wpa']['enable'])) {                                 $wpa .= <<

This is the portion that takes all the variables set in the web GUI and creates the hostapd_"if-name".conf file. "man hostapd" for more information.

Did you add rules to allow such traffic in on the wifi interface ?

I meant you should connect a directional antenna to the computer (the pfSense) connecting to the accesspoint.
A directional antenna has benefits for both sides.

The CP can currently only one one interface be enabled.

@chrisssooo:

Hi,
i have do it on a embedded system.

You must do it over the WebGUI becourse the write permissions is only over it.
Use pfsense 1.2.1 RC2 becourse FreeBSD 7.0

Step 1:
Download the 4 Kernel modules: http://deponie.yamagi.org/freebsd/iwi/
Go in the WebGUI in "Diagnostics->Command Prompt".
Upload all 4 Kernel Modules over the "Upload" function.
The Files will be upload to /tmp/
After Upload use also in "Diagnostics->Command Prompt" the "Execute Shell command" function to move the files to the right location.
1. Type in Command: "mv /tmp/if_iwi.ko /boot/kernel/" and click on "Execute"
2. Type in Command: "mv /tmp/iwi_* /boot/kernel/" and click on "Execute"
Now the Kernel Modules are on the right location.

Step 2:
Now edit the /boot/loader.conf File.
Go on WebGUI in "Diagnostics->Edit file".
Type in the field "Save/Load from path"  this Text: "/boot/loader.conf" and click on "Load".
Add this 7 Lines at the end:

if_iwi_load="YES" wlan_load="YES" firmware_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" legal.intel_iwi.license_ack=1

and click on "Save"
Reboot pfSense.

Step 3:
Now you can Assign you card in the WebGui over "Interfaces->assign" whit the "Plus" and configure it.
But when you read this Thread you must know:
ITS ONLY POSSIBLE TO SET THIS CARD TO "Infrastructure" AND "Ad-hoc" … "Access point" DONT WORK!!!

I hope its work for you :)

Thanks a milion this worked like a charm. This should be stickied somewhere as its a sure fire and quick way to get those cards working.

Well, I spent this weekend trying to figure out what was causing this.  The card's rated at a maximum of 18 dBm at 6 megabits according to the datasheet (so, about 63 mW, according to this calculator).  Unfortunately, it doesn't list what power output it has on lower modes.  I tried turning down the power anyway (to about 60%), but unfortunately it didn't seem to help.

I did some more searching and found a Google cache of this post from the now-closed 1.2.1 RC forum of somebody having a similar issue and it seems like it could be a FreeBSD 7 issue.  I tried reverting to 1.2, but it didn't help much.  I could load YouTube, which gave me a connection error before, but I couldn't actually play more than a few seconds of any video.  So, if it is a FreeBSD issue, it's one that was somehow missed in 6.2 and 7.0.

Just to make sure it wasn't the iPod itself, I pulled out my old WRT54G and turned it into an access point.  It works just fine.  So, I've got a solution for now, but I'm going to continue to try to find out more information about what might be happening, as I'd really like to use my pfSense unit as the AP instead of having a separate one.

I'll look into whether it might be the power supply.  I didn't think of that possibility.  It'd be nice if I could just replace that, as it can't be very expensive.

excellent. thank you for your help.

thank you! works perfect now (again) :)

Hi,

I use a mini ITX motherboard. A VIA PD series motherboard.
I just installed 1.2.1 final release and my wireless NIC started working.  Although I seem to be losing connection every 10 minutes or so…

dmesg | grep ath

ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: <atheros 5212="">mem 0xea000000-0xea00ffff irq 11 at device 20.0 on pci0
ath0: [ITHREAD]
ath0: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:19:5b:89:e7:d2
ath0: mac 10.5 phy 6.1 radio 6.3

So far wireless is not what I would call very stable for me unfortunately.  :-</atheros>

That such a friend!
At the moment it achieves placing client mode but without result of entry into the Internet but no longer do that ay that I lack any information please?