Okay… lesson learned!

I'm by far no expert so I figured it could be bad to put a rule such as: ******

It works with the two rules:

protocol: UDP,
source: any,
sourceport: 68
destination: any
destination port: 67

and

LAN net ****

What is the best option? the pass all only rule or the set of two rules?

thank you very much!

Thank you ipfftw:

what model of wireless airlink101 you used?

Ok, thank you :)
i hope so it will be all these stuff available in near future :)

Reboot. You can clear protocol stats by netstat -z -I ath0 (or whatever interface name you have), but this will not clear input/output errors.

It is not normal for it to rotate. Sound like you have the wrong connectors for that cable. Most connectors are cable specific.

pfSense is built on FreeBSD which providse the device drivers. The FreeBSD supported hardware list at http://www.freebsd.org/releases/7.1R/hardware.html doesn't list the Realtek 8185L as a supported device. You will probably need to get another device, preferably one thats on the FreeBSD supported device list.

If you want to use the pfSense box as a wireless access point you will need to choose a device with access mode support (not all supported wireless devices support operating in access mode).

I often have this problem too - it seems to have gone away once I specified the pfsense box's IP in the DHCP server section as the default gateway and DNS server.  It should pass that through by default but I've noticed it doesn't always.  My SSH connections are fast again for the time being.

You can set lan as 192.168.1.1 and wifi as 192.168.2.1.  Then in the Firewall Rule of LAN interface set rule to allow your wifi subnet to access only to the IP of samba shares on the LAN.

Set your netgear AP into routing mode (NOT NAT mode).
Also create a static route on the pfSense for the 192.168.1.1/24 subnet pointing to the 192.168.0.5 IP.

No sooner than when the underlying version of FreeBSD does ;)

Thanks Omen, appreciate that man.

Normally the firewall is initialised to prevent access from WAN (your wireless network) to LAN. If you want to retain that configuration you'll have to write firewall rules to allow access from WAN to LAN OR initiate your tests from LAN.

If you are new to pfSense you may find it easier to add another NIC to your box, use it for WAN, make the wireless NIC OPT1 and bridge OPT1 with LAN. This is a more "usual" type of configuration and there is a tutorial for that configuration - see the pfSense docs page at http://doc.pfsense.org/index.php/Main_Page and click on the Tutorials link and look for the link to add a WiFi interface.

I have these two:

http://linitx.com/viewproduct.php?prodid=11919
http://linitx.com/viewproduct.php?prodid=11736

Atheros AR5414 - R52H 802.11a/b/g High Power minipci and the pci to minipci adapter work flawlessly with pfsense 1.2.2.

The high power really (350mw) does make a difference, before I was using netgear WG511t, also atheros.

Update:

Posting from my laptop connected to pfsense (hotspot).  Seems like everything is working just fine.

Still leads me to wonder why I'm unable to pass traffic when connected with an xv6800 Pocket PC running WM 6.1??

Hi,

yes, I followed the man page, and I can configure the card on the command line.  I changed the loader.conf, copied the corresponding ipw kernel modules to the proper place and added all parameters from iwi replaced with ipw, and I even created the structure in /usr/share do point to the directory containing the README because of the license parameter. The card is detected fine now (and has to, as otherwise I guess I wouldn't be able to configure it via cli)

Well, probably not so important then, as I guess I'll have to get an atheros based card if I want to have an ap. But before I just wanted to test everything…

Thanks,
Klaus

@wallabybob:

If you have your access point connected to a switch then all the wireless clients are effectively on the same LAN as all the computers connected to the switch.

If you have the access point connected to the pfSense box through an additional NIC card in the pfSense box then I think you have more configuration options, for example, you can bridge the wireless LAN and LAN so that things look much like connecting the access point to the switch OR you can treat the wireless LAN as a separate network with restricted access to the LAN.

Also, pfSense supports a number of wireless LAN cards so you can turn your pfSense box into a router-firewall-wireless access point. I have such a system at home which happily supports three family laptops with wireless access and about six wired computers. Currently the wireless support in pfSense is 802.11b and 802.11g only which is probably plenty fast enough for many home applications.

Thanks for the detailed information. I'm going to do some testing with different configurations before putting it into productions. Since my switch supports VLAN's, i'll try to put the W.A.P. on its on VLAN. Unfortunatley i don't have enough room in my pfsense for another card since its on a 1u server.

@mildmanneredreporter:

I have had an IPCop box running for several years, but broke it with a Net-to-Net application. So I am trying to shift to pfSense and am unable to access the Net wirelessly, even though I am clearly on the wireless network. I believe its a DNS problem that I cannot fathom.

I have built the pfS box and have the LAN running. It works fine. Wireless looks like this:

Cable modem >> pfSense >> Linksys WRT54GS >> Laptop

This worked fine as:

Cable modem >> IPCop >> Linksys WRT54GS >> Laptop

so I know that the wireless AP works. I can even shift back to the IPCop box and get wireless net access running. My laptop will also join the wireless WRT54GS network flawlessly even on pfS. I can see the laptop on the pfSense routing table. But that's as far as I can get.

I followed the config instructions here:
http://www.freesoftwaremagazine.com/articles/configure_professional_firewall_using_pfsense?page=0%2C1

I use the OpenDNS servers, and have them correctly listed in my General Setup. They work on my LAN. I have tried turning DNS forwarding off and on, checking the DNS mapping boxes and not checking the DHCP registration boxes in the DNS forward service. I just can't get out of my house on my wireless network.

Any idea what I'm doing wrong here?

UPDATE: For some reason, two reboots got it going again.

Thanks for the fast reply. Working :)