You can do it with 1 ethernet interface and one wireless interface (i just set up 10 such systems).

First you assigne the ath0 as WAN and the sis0 as LAN.
You now can access the webinterface.
Create rules so you can acces the pfSense from the WAN.
Now swap the LAN and the WAN interfaces.
You should be able to access the pfSense from the WAN now and configure the ath0 as LAN.

i use a D-Link card , and it works perfectly, this card have an atheros chipset … i just have a litle problem with
i try to enter to the webconfig when im connected via Athros interface, bridge with LAN and with my english  ;D, but this hardware
works in pfSense ... like any atheros chipset nic... i use D-Link DWL-G520

Saludos

You may want to try out pfSense 1.2.1 which uses FreeBSD7. For me it has fixed the disconnect issues.
Link to download pfSense 1.2.1 can be found here http://blog.pfsense.org/?p=207

Update: 6.3 Fix all my connectivity issues.

Seems unlikely. They have a drop out of any functionality. I have something odd going on where pings seem to make it come 'unstuck'.

Don't suppose anyone wants to buy an ALIX 2C2 with mini-pci wireless etc?  :D

Motherboard:      GA-PCV2
Memory:              512MB
Wireless Card:      TP-Link TL-WN651G
Wireless Chipset:  ath0: <atheros 5212="">…
Wireless Mode:    AP
Problem:            None known
$ athstats
905044 tx management frames
73185 tx frames discarded prior to association
6417 tx failed 'cuz FIFO underrun
71328 tx failed 'cuz bogus xmit rate
810843 tx frames with rts enabled
94307 tx frames with an alternate rate
45 tx frames with 11g protection
5142838 rx failed 'cuz of FIFO overrun
79 rx failed 'cuz frame too short
74587 rx management frames
19003302 beacon setup failed 'cuz no mbuf
379584516 beacons transmitted
64921 periodic calibration failures
8289 tx used alternate antenna
Antenna profile:
[2] tx  506092 rx  219413
[3] tx  465718 rx    3015
$ uptime
8:48AM  up 22 days, 13 hrs, 1 user, load averages: 0.22, 0.11, 0.03</atheros>

First, use something better than WEP, like WPA with a strong passphrase (long, including upper and lowercase letters, numbers, and symbols). That'll keep out unauthorized users.

@mechanicalmetal:

Also you say to bridge my wifi router into my WAN network on pfsense, wouldn't this be a security issue since my LAN is pushing out the protected network? Should I just go into my router and select static network and plug it directly through my home network?

You can firewall on a bridge no differently than you can on a routed or NATed interface. If you want them both on the same subnet, that's your only option. You can't have two identical subnets in two separate broadcast domains, so bridging is the only way to use the same subnet on both the wireless and wired networks. It's usually the most desirable for home users because it's the only way things like Windows network browsing will work properly.

We have a mock network in our lab and today We installed the FreeRadius server on the gateway. We turned on the captive portal on the client pf3 and pointed the ath to pf1 and could not ath to radius on the 10.0.1.0 network Which we needed to ath buildingb. We turned on the captive portal on the pf1 and recieved a double login when trying to ath from pf3. Ath was working to the radius, but we had to login twice. We added the pf3 Wan ip to the pf1 captive allowed ip address with a from instead of to, and then We only recieved one login page which is functional. Now all members will have to ath before they can access the internet.

Take a look at these sysctls:

sysctl dev.ath.0.slottime=$slottime
sysctl dev.ath.0.acktimeout=$timeout
sysctl dev.ath.0.ctstimeout=$timeout

For Atheros cards they are easily controlled by /sbin/athctrl.sh (this can also be set in GUI).

-Espen

Decex, have a look at this thread http://forum.pfsense.org/index.php/topic,10233.0.html

I don't know much about linksys router, but i have 2 solution:
the first one : put your router in bridge mode if you can.
the second one : plug your cable from pfsense in the WAN port, and set it to DHCP. the rest is a normal setup.
my router was a dlink so i don't know if you can put all the same setting.

@cooldude1015:

Ahh I see that makes sense.

Obviously I haven't been clear enough.

@jahonix:

@cooldude1015:

Ok so what I tried to do was set the pfsense at 192.168.1.0

You must not use  .0 (this is the network) or  .255 (this is the broadcast) on your LAN subnet, btw.

Did you read articles about subnetting already? Do so! … Wikipedia is great for that.

@cooldude1015:

In terms of settings On Tomato:
LAN
IP: 192.168.1.2
Gateway: 192.168.0.1
DHS: 192.168.0.1
Subnet: 255.255.255.0

Do you see that 192.168.0.0  and 192.168.1.0  are different subnets?
Please read the available articles about netmasks and subnetting carefully. You have to understand these basics before working with them!

no

hi hadi57 please check your inbox i have pm for you.

Hey

I finally got around to following the directions mentioned here: http://www.maroouch.com/ar5215/ar5215.html

I set my RegDomain and now my card works perfectly.  I didn't need to install pfSense v1.2 beta as suggested in an earlier post.

Thanks everyone.
RC

UPDATE: That fixed it and my DC++ problem! thanks!

@molski:

So even if the card was working properly, it wouldn't work, is what you're saying?

Um… No.
I'm trying to say that the CM9 should work fine.
FreeBSD should detect it and load the driver. IF the card was unsupported, then you should still see a dmesg where the OS probes it, something like:
pci0 <network>at device 12 (no driver attached)
I was pointing out that dmesg previously posted showed the cypto chip with no driver attaching (expected behavior in 1.2), but did not show a network device with no driver. That made me suspect the physical seating of the card.</network>

following the link and using pfSense RELENG 1.2 the system found the card without any problems. now I can move forward.

wallabybob thanks for the support and the link!