How to make accesspoint in pfsense

firefox

i also try this guied

http://doc.pfsense.org/index.php/Access_Point2

"IP configuration

Bridge with LAN – therefore no IP address and no gateway" <–---------- ????

if the option is on static
there has to be ip ?

wallabybob

There is a guide that says to put a permanent IP address
There is a guide that says it does not matter and leave the default editor

If you can identify the guides someone might be able to explain the apparent contradictory advice.

Not all supported USB WiFi dongles will operate as APs? What is the chipset in your dongle?

@firefox:

i try this guide
http://pauldotcom.com/wiki/index.php/Pfsense#Setup_the_Wifi_Interface_using_the_Web_UI

That guide describes creating a bridge between the WiFi interface and the pfSense LAN interface. That is fine if you want to treat Wii clients the same as LAN clients when it comes to access restrictions. However, for beginners I suspect it might be less troublesome to configure the WiFi interface as a separate interface with its own IP address space, DHCP server and firewall rules.

firefox

That guide describes creating a bridge between the WiFi interface and the pfSense LAN interface. That is fine if you want to treat Wii clients the same as LAN clients when it comes to access restrictions. However, for beginners I suspect it might be less troublesome to configure the WiFi interface as a separate interface with its own IP address space, DHCP server and firewall rules.

i do want to treat Wii clients the same as LAN clients when it comes to access restrictions

I did everything in that directory one by one
Except for one thing
I gave a different ip address 192.168.0.3

The computer recognizes the card
I also find the network with a laptop
But when I click connects to the network
Computer waiting to receive ip

this is the card
http://www.tp-link.com/en/products/details/?model=TL-WN7200ND

1.jpg_thumb

2.jpg_thumb

3.jpg_thumb

4.jpg_thumb

5.jpg_thumb

firefox

More screenshots

I added one more thing that was not in the guide
under "Interfaces" –-> "Groups"
i made a group from "wlan" and "lan" {See last picture}

Sorry about the quality of the images
You can not rise here large images

6.jpg_thumb

7.jpg_thumb

8.jpg_thumb

wallabybob

Thanks for the screenshots - they are helpful.

Can you also post a screenshot of the Interfaces -> (assign) page?

For bridging WiFi and LAN there are a couple of system tunables that need to be adjusted. Have you done that?

I'll leave further comment until I get answers to those two questions for the answers will give me a fuller understanding of what needs to be done.

firefox

Here is a screenshot requested

What is tunables ? = Adjustments

9.png_thumb

wallabybob

Here is what I think you need to do.

1. Change interface type of the WiFi interface to None (so it doesn't have an IP address).

2. Set the system tunables as described in step 3 of the post at http://forum.pfsense.org/index.php/topic,56298.0.html

Hereafter, if you are prompted to Save (update configuration file) and then Apply (to running system) click just Save but not Apply. You will reboot at the end to Apply all changes at once.

3. On Interfaces -> (assign) click the "+" at the bottom right to add a new interface to pfSense. Note the name of the new interface, I'll assume it will be OPT3. In the following description change OPT3 to whatever name was asigned.

4. On Interfaces -> (assign) click on the Bridges tab, then click on the e button to the right of bridge0 so you can change the bridge members to OPT3 and WLAN.

5. On Interfaces -> (assign) use the pull downs to change OPT3 to fxp1 (your previous LAN interface) and change the LAN interface from fxp1 to bridge0.

6. Reboot and verify things are working correctly.

After reboot you should have fxp1 and run0 as members of bridge0, bridge0 as LAN (so LAN characteristics including firewall rules apply identically to bridge members) and traffic should flow freely between devices on the two interfaces.

firefox

I do not understand why add another interface

In any case I did these steps
But I get to 6
And does Reboot

During the restart
The computer go to the point where I have to choose again Interfaces
Without it impossible to continue
If I choose interfaces all will reset

wallabybob

@firefox:

I do not understand why add another interface

So pfSense knows there is another interface available to it to use. Do you have another way of getting pfSense to use interface bridge0?

@firefox:

During the restart
The computer go to the point where I have to choose again Interfaces
Without it impossible to continue
If I choose interfaces all will reset

MAYBE you hadn't added the line to /boot/loader.conf.local so the firmware for run0 is available at boot time. If the firmware is not available then pfSense may see one of the configured interfaces (run0) is not available and so attempt to reassign interfaces since the previous interface assignment is wrong.

MAYBE you need to add a boot delay so there enough time for all USB devices to be detected and probed.

I think at the assign interfaces question it should be possible to get to the shell by typing one to a few Ctrl-Cs. Then you should be able to add the necessary line ("runfw_load="YES") t /boot/loader.conf.local and reboot.

firefox

First of all thanks for the help

MAYBE you hadn't added the line to /boot/loader.conf.local so the firmware for run0 is available at boot time

how do i do that ?

can i do this from the gui ?

in all the boots
when i needed to assign interfaces
it show me some thing like this

type the name of the wan interface or press a
fxp0 = wan pppoe bla bla bla

type the name of the lan interface { all firewall ruls bla bla bla }
fxp1 = lan

type the name for optinal interface wan2
dc0 = wan2

type the name for wlan interface
run0 = wlan – but when i assign this -- i got a error message

so only the first tree where assign

wallabybob

@firefox:

can i do this from the gui ?

Diagnostics -> Edit File
type the name for wlan interface
run0 = wlan – but when i assign this -- i got a error message

What is the text of that error message?

firefox


enter the WAN interface name or 'a' for auto-detection: fxp0

enter the LAN interface name or 'a' for auto-detection
NOTE: this enables full firewalling/nat mode.
(or nothing if finished): fxp1

optional interface 1 description found: WAN2
enter the optional 1 interface name or 'a' for auto-detection
(or nothing if finished): dc0

optional interface 2 description found: WLAN
enter the optional 2 interface name or 'a' for auto-detection
(or nothing if finished): run0

invalid interface name 'run0'

optional interface 2 description found: WLAN
enter the optional 2 interface name or 'a' for auto-detection
(or nothing if finished):

Diagnostics -> Edit File
type the name for wlan interface

where do i do it ?

10.png_thumb

wallabybob

The run0 'invalid interface name' is what I would expect if the firmware isn't loaded at boot time.

@firefox:

Diagnostics -> Edit File
where do i do it ?

I have never used it but I would expect you type the line```
runfw_load="YES"


> /boot/loader.conf.local

in the _Save / Load from path:_ box then click _Save_.

firefox

The first thing worked
Once I made what you said in the box
The computer automatically recognize the wireless card
And directly reached cli interface with 14 options

After that I did all the steps again, of your previous message

Here is what I think you need to do.

1. Change interface type of the WiFi interface to None (so it doesn't have an IP address).

2. Set the system tunables as described in step 3 of the post at http://forum.pfsense.org/index.php/topic,56298.0.html

Hereafter, if you are prompted to Save (update configuration file) and then Apply (to running system) click just Save but not Apply. You will reboot at the end to Apply all changes at once.

3. On Interfaces -> (assign) click the "+" at the bottom right to add a new interface to pfSense. Note the name of the new interface, I'll assume it will be OPT3. In the following description change OPT3 to whatever name was asigned.

4. On Interfaces -> (assign) click on the Bridges tab, then click on the e button to the right of bridge0 so you can change the bridge members to OPT3 and WLAN.

5. On Interfaces -> (assign) use the pull downs to change OPT3 to fxp1 (your previous LAN interface) and change the LAN interface from fxp1 to bridge0.

6. Reboot and verify things are working correctly.

After reboot you should have fxp1 and run0 as members of bridge0, bridge0 as LAN (so LAN characteristics including firewall rules apply identically to bridge members) and traffic should flow freely between devices on the two interfaces.

But it still does not work
There reception
I can find the network with a laptop or cell phone
But they do not get ip

11.jpg_thumb

12.jpg_thumb

wallabybob

The counter on pfSense dashboard reports 0 bytes received on the WLAN interface. You could use those counters to verify pfSense is seeing something (possibly DHCP requests) from WLAN clients.

On my run device I have set WPA Pairwise to AES because a Linux client wouldn't connect when it was set to TKIP. But I have no idea if that would fix your problem. You might have to disable/enable the WLAN interface to get configuration changes to take effect.

The Status -> Wireless page should also be consulted to see if pfSense has associated with your client. I am not sure exactly what "associated" means but it is a significant step in getting wireless station to communicate.

firefox

There's something I do not understand

After making all settings
Opt3 interface should be with the ip

Lan interface
Should be listed bridge0

Perhaps this is the problem

Thanks again for the help

firefox

On my run device I have set WPA Pairwise to AES because a Linux client wouldn't connect when it was set to TKIP

it worked
i have access to the internet and lan

But now there is another problem
The system does boot after 30 seconds wireless connection

this is the error log

Crash report begins. Anonymous machine information:

i386
8.1-RELEASE-p13
FreeBSD 8.1-RELEASE-p13 #1: Fri Dec 7 16:55:26 EST 2012 root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8

Crash report details:

Filename: /var/crash/bounds
1

Filename: /var/crash/info.0
Dump header from device /dev/ad0s1b
Architecture: i386
Architecture Version: 1
Dump Length: 71168B (0 MB)
Blocksize: 512
Dumptime: Fri Feb 22 15:44:06 2013
Hostname: pfsense.firefox.co.il
Magic: FreeBSD Text Dump
Version String: FreeBSD 8.1-RELEASE-p13 #1: Fri Dec 7 16:55:26 EST 2012
root@snapshots-8_1-i386.builders.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8
Panic String:
Dump Parity: 632959541
Bounds: 0
Dump Status: good

Filename: /var/crash/textdump.tar.0
ddb.txt��0600��0��0��140000��12111711106� 7061� ��ustar��root��wheel��db:0:kdb.enter.default> run lockinfo
db:1:lockinfo> show locks
No such command
db:1:locks> show alllocks
No such command
db:1:alllocks> show lockedvnods
Locked vnodes
db:0:kdb.enter.default> show pcpu
cpuid = 0
dynamic pcpu = 0x51d080
curthread = 0xc499bc80: pid 0 "run0 taskq"
curpcb = 0xeab3ad90
fpcurthread = none
idlethread = 0xc4590a00: pid 11 "idle: cpu0"
APIC ID = 0
currentldt = 0x50
db:0:kdb.enter.default> bt
Tracing pid 0 tid 64063 td 0xc499bc80
run_drain_fifo(c49cb000,c499bc80,0,0,0,…) at run_drain_fifo+0x5f
run_ratectl_cb(c49cb000,1,0,c12d0b3c,0,...) at run_ratectl_cb+0x5c
taskqueue_run(c486bb80,c486bb98,0,c0ede918,0,...) at taskqueue_run+0x89
taskqueue_thread_loop(c49d7074,eab3ad38,0,0,0,...) at taskqueue_thread_loop+0x45
fork_exit(c0a7a1a0,c49d7074,eab3ad38) at fork_exit+0x88
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xeab3ad70, ebp = 0 ---
db:0:kdb.enter.default> ps
pid ppid pgrp uid state wmesg wchan cmd
25445 35603 25 0 S nanslp 0xc133ea24 sleep
23430 15132 249 0 S nanslp 0xc133ea24 sleep
56580 10101 10101 0 S piperd 0xc4a04000 rrdtool
416 1 416 0 Ss select 0xc4eabb64 ntpd
15132 1 249 0 S wait 0xc4e74aa0 sh
10101 1 10101 0 Ss select 0xc4991da4 apinger
43049 41818 43049 0 S+ ttyin 0xc45e1c70 sh
41818 41595 41818 0 S+ wait 0xc4e74d48 sh
41612 13725 41612 0 Ss (threaded) sshlockout_pf
64110 S nanslp 0xc133ea24 sshlockout_pf
64103 S piperd 0xc4e4c188 initial thread
41595 1 41595 0 Ss+ wait 0xc4e74550 login
40746 40685 40200 62 S piperd 0xc4a04dc8 unlinkd
40685 40200 40200 62 S select 0xc4c71424 initial thread
40200 1 40200 62 Ss wait 0xc4c6dd48 squid
37712 37202 37202 0 S nanslp 0xc133ea24 minicron
37202 1 37202 0 Ss wait 0xc4c6c000 minicron
37001 36453 36453 0 S nanslp 0xc133ea24 minicron
36453 1 36453 0 Ss wait 0xc4c6caa0 minicron
36220 35882 35882 0 S nanslp 0xc133ea24 minicron
35882 1 35882 0 Ss wait 0xc4c6c550 minicron
35603 1 25 0 S+ wait 0xc4af1d48 sh
41984 1 41984 0 Ss nanslp 0xc133ea24 cron
31258 1 31233 65534 S select 0xc4c70724 dnsmasq
30007 1 30007 1002 Ss select 0xc4c70c24 dhcpd
22980 21308 21248 0 S accept 0xc4afb03e initial thread
21602 21308 21248 0 S accept 0xc4b5f6ae initial thread
21308 1 21248 0 S kqread 0xc4ac8600 lighttpd
14375 1 14375 0 Ss select 0xc486b8e4 inetd
13725 1 13725 0 Ss select 0xc4991b24 syslogd
13419 1 25 0 S+ piperd 0xc4a03dc8 logger
13379 1 25 0 S+ bpf 0xc4995900 tcpdump
9468 1 9468 0 Ss select 0xc49fede4 hostapd
6414 1 6414 0 Ss (threaded) mpd5
64085 S select 0xc49fe7e4 mpd5
264 1 264 0 Ss select 0xc4990024 devd
251 249 249 0 S kqread 0xc4a01d00 check_reload_status
249 1 249 0 Ss kqread 0xc4a01b80 check_reload_status
40 0 0 0 SL mdwait 0xc49af000 [md0]
24 0 0 0 SL sdflush 0xc136d480 [softdepflush]
23 0 0 0 SL syncer 0xc1352594 [syncer]
22 0 0 0 SL vlruwt 0xc45d5d48 [vnlru]
21 0 0 0 SL psleep 0xc13522c8 [bufdaemon]
20 0 0 0 SL pgzero 0xc136e134 [pagezero]
19 0 0 0 SL pollid 0xc133df7c [idlepoll]
18 0 0 0 SL psleep 0xc136dd5c [vmdaemon]
17 0 0 0 SL psleep 0xc136dd24 [pagedaemon]
9 0 0 0 SL ccb_scan 0xc1308c54 [xpt_thrd]
8 0 0 0 SL pftm 0xc04f7020 [pfpurge]
7 0 0 0 SL waiting_ 0xc13599d8 [sctp_iterator]
16 0 0 0 SL tzpoll 0xc130da8c [acpi_thermal]
15 0 0 0 SL (threaded) usb
64045 D - 0xc4725d0c [usbus3]
64044 D - 0xc4725cdc [usbus3]
64043 D - 0xc4725cac [usbus3]
64042 D - 0xc4725c7c [usbus3]
64040 D - 0xc4711dac [usbus2]
64039 D - 0xc4711d7c [usbus2]
64038 D - 0xc4711d4c [usbus2]
64037 D - 0xc4711d1c [usbus2]
64035 D - 0xc46fadac [usbus1]
64034 D - 0xc46fad7c [usbus1]
64033 D - 0xc46fad4c [usbus1]
64032 D - 0xc46fad1c [usbus1]
64030 D - 0xc46e5dac [usbus0]
64029 D - 0xc46e5d7c [usbus0]
64028 D - 0xc46e5d4c [usbus0]
64027 D - 0xc46e5d1c [usbus0]
14 0 0 0 SL - 0xc133e884 [yarrow]
6 0 0 0 SL crypto_r 0xc136caac [crypto returns]
5 0 0 0 SL crypto_w 0xc136ca88 [crypto]
4 0 0 0 SL - 0xc133c124 [g_down]
3 0 0 0 SL - 0xc133c120 [g_up]
2 0 0 0 SL - 0xc133c118 [g_event]
13 0 0 0 SL sleep 0xc12df260 [ng_queue0]
12 0 0 0 RL (threaded) intr
64051 I [irq1: atkbd0]
64049 I [irq15: ata1]
64048 I [irq14: ata0]
64047 I [irq22: dc0]
64046 I [irq20: fxp0 fxp1]
64041 I [irq23: ehci0]
64036 I [irq18: uhci2]
64031 I [irq19: uhci1]
64026 I [irq16: uhci0]
64025 I [irq9: acpi0]
64021 I [swi2: cambio]
64020 I [swi6: task queue]
64019 I [swi6: Giant taskq]
64017 I [swi5: +]
64007 I [swi3: vm]
64006 RunQ [swi4: clock]
64005 I [swi1: netisr 0]
11 0 0 0 RL [idle: cpu0]
1 0 1 0 SLs wait 0xc458ed48 [init]
10 0 0 0 SL audit_wo 0xc136ce20 [audit]
0 0 0 0 RLs (threaded) kernel
64063 Run CPU 0 [run0 taskq]
64024 D - 0xc46a0280 [acpi_task_2]
64023 D - 0xc46a0280 [acpi_task_1]
64022 D - 0xc46a0280 [acpi_task_0]
64018 D - 0xc46a04c0

firefox

Well
After the advice that wallabybob Gave

Finally the wireless devices connected and received ip

So this issue is resolved

Many thanks for the help

There is another problem

After a period of time where there are wireless connections
The system is down and up again

I searched for it here in the forums and in Google

From what I understand it's a problem of encryption
I tried to change the encryption settings
And raised the amount of time the devices are connected

Max is an hour maybe a little more
System still falls and rises again

Is there anything else other than encryption ?

Should I write that the problem has been fixed in this Thread
And open a new Thread to the new problem?

wallabybob

@firefox:

After a period of time where there are wireless connections
The system is down and up again

Do you mean the system crashes and restarts?

@firefox:

Should I write that the problem has been fixed in this Thread
And open a new Thread to the new problem?

Yes, its a distinct problem. I suggest you create a new topic in the Wireless forum and post as full a description of the problem as you can including pfSense build and the output of pfSense shell command```
/etc/rc.banner
ifconfig

firefox

Where to write it ?

/etc/rc.banner
ifconfig