I'm not aware of any other way to check signal levels under FreeBSD than via ifconfig. I don't think wlandebug helps at all with signal strengths, and I don't think any of the driver sysctls do either.

as he says in the post:

windows itself has no native eap-ttls support. you have to go with  third party like w2secure which is free. (at least the eap-ttls-implementation)

to simplify:

on eap-tls the client is in need of a certificate to authenticate the machine over a certificate authority to the server, then authenticate the user with password through a secure connection in a more or less secure way (MS-CHAP).

on eap-ttls (tunneled) to client pushes its credentials trough a tunnel where ONLY the server has to prove authentication (therefore you have to install the CA on the clients), then establishes a secure connection. (a bit like https)
since the user credentials are sent trough a secure tunnel, it doesn't matter that auth. for the user are doing PAP which is unencrypted ASCII.

you can see ttls often a university's or companys, with regular changing users..

Ah yea, thanks for that.

Wish the search function would have brought that up. Must have missed the right keywords. :P

Seems like 2.0 might resolve the issue all together. Might give that a try since this is just a research system at the moment. So far its quite impressive even with the occasional quirk.

@wallabybob:

Your LAN shouldn't be bridged with WAN. (But that may not be your only problem.)

Your physical setup is very similar to mine.

Have you been able to access the pfSense web GUI? If so, I suggest you enable DHCP server on the LAN interface and (if you have a switch) connect a switch to the LAN interface then plug a client computer in the switch and configure the client computer to get IP address by DHCP. After restarting the client computer it should have an IP address and a default route to 192.168.2.3

Thanks, you put me in the right direction.
Everything works as expected. Now I will tweak with Rules for better protection.

Is your AP a bridge or a router? If its a bridge then you shouldn't have DHCP server running on both pfSense and the AP unless you take care to ensure they don't conflict in their address assignments  but it would be less hassle to have only the one DHCP server. If the AP is a router and the DHCP server is running only on the downstream interfaces then that shouldn't be a problem.

DHCP clients typically get their IP address, name server IP address and default gateway from the DHCP server. My guess is that things go bad when your client renews its DHCP lease and gets a new (different) name server address and/or default gateway.

I suggest you use pfSense as your only DHCP server (you might need to enable DHCP forwarding on your AP) and see how things go OR restart everything and record your client computer's IP address, name server IP address and default gateway and then when things go bad chek the current values against the original values to see if any of them have become incorrect.

Not really helpful, but I heard a long time ago a story (which was likely a tall tale) about ranchers running ARCnet over their fence wiring.

Too bad you couldn't use wire fences as a giant antenna :-)

use more nic's on your pfsense box ;) and have them configured each for different gateways, subnets, and smaller group of computers. do not bridge any of them. and if you are an administrator, install on each computer a robust firewall, antivirus, and internet security software.

I've had good results with a Marvell 88W8363.  Note that the driver was not available until FreeBSD 8, however.  This means it will not work on pfSense 1.2.3, only 2.0.

Thanks all,

I have managed to get things up and running… 
Had to reconfigure all interface the other way round :

LAN –> WAN
WAN --> WLAN

Things are running smoothly, I only had to force the gateway for It to work.
But now It seems ok…

Thx.

Mini-pci to pci adapters (with more than one slot) are not very common.  At the moment I can only find a 4 slot adapter.  The adapters have bridge chips so I guess it comes down to OS support for the bridge.

Ok. I follow what you are saying regarding the N card.

It would seem I would be better off with one of these then:

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=370387009123

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=330430725233 <–This one is a 5212

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=270581080563

Correct?

Thanks for the help. Once I get all the parts I will post about using a mini-pcie card if it works.

Bob

As I said, it is not possible if both have the same gateway.

Interface routing might work only in rare cases where the WAN is an actual point-to-point link which does not require a gateway.

I do understand WME was the original name for WMM but I guess my question should be can I set the following settings somehow for WMM devices (ie, wireless voip phone)

WMM access category
WMM Power Save
WMM Admission Control
DSCP (Differentiated Services Code Point)

In the GUI config for the interface it only has a check box to enable or disable WME.  I'm not apposed to logging in through a shell and adjusting a config file I just have no experience in this particular realm.

Thanks

I have three ap's 2 are operating on G and the other is on B/G

Yes I have followed every step, I am way ahead keeping track of notes in updates in src/sys/UPDATING

Well, I even added a 6dbi omni antenna attached to a pigtail. I am expecting for atleast the two ap's in G mode would appear in the list?
What could it be? Does anyone have the same card running on freebsd 7.2?

(Partly copied and pasted from another post of mine.)

The only 802.11n chipsets I know of that work as an access point in FreeBSD are the ones supported by the ath driver (Atheros) and the mwl driver (Marvell 88W8363).

Some supported 802.11n chipsets I know of for Atheros are 5416 (802.11b/g/n) and 5418 (similar to 5416, but I think also supports 802.11a and 5 GHz 802.11n).  802.11n rate control is not yet implemented in the FreeBSD driver for Atheros chipsets, so only up to 802.11a/g speeds will work.

The Marvell 88W8363 is an 802.11n chipset with support for 802.11a/b/g/n, but the driver doesn't seem to support 802.11n rates yet and was just added in FreeBSD 8.0, so it is not possible to use the card in anything before pfSense 2.0 beta.  I've only seen one model of card that I know uses it, a mini PCI card (though converters to regular PCI are available), and it only seems to be available on eBay from around 2 to 4 different sellers in China.

Thanks for the info.

WiFi is just for the internet, the file transfers are all done via ethernet hence the need for gigabit eth.
I'll probably keep the WRT54G as the WiFi AP anyways because it seems it will do a much better job than a WiFi card in the pfSense box.

Cool!

Ah,

you are right, i changed too much and also set the wlan-adapter to dhcp…
Changed it back.
Does this look correct?

LAN interface (vr0)
Status up
MAC address 00:0d:b9:1c:cc:ec
IP address 192.168.1.100 
Subnet mask 255.255.255.0
Media 100baseTX <full-duplex>In/out packets 6049689/8669774 (1.65 GB/1.38 GB)
In/out errors 0/0
Collisions 0
Bridge (bridge0) learning

WLAN interface (ath0)
Status associated
MAC address 00:80:48:68:5e:36
IP address 0.0.0.0 
Subnet mask 255.0.0.0
Media autoselect mode 11g <hostap>Channel 2
SSID Michas
In/out packets 995/8541 (179 KB/39 KB)
In/out errors 3407/0
Collisions 0</hostap></full-duplex>