Welcome, Guest. Please login or register.
Did you miss your activation email?
+  pfSense Forum
|-+  pfSense English Support» Wireless» Cant get pfsense work as an accesspoint
Username:
Password:
 
 

Pages: [1]   Go Down
  Print  
Author Topic: Cant get pfsense work as an accesspoint  (Read 2789 times)
0 Members and 1 Guest are viewing this topic.
vildsvin123
Newbie
*
Offline Offline

Posts: 13


View Profile
« on: July 04, 2011, 01:32:24 pm »

System: pfSense 2.0 RC3

ISP ->pfSense --->Switch
                    ---> Wifi?Huh??
Ale0 -> WAN
Re0 -> LAN DHCP 192.168.0.1 /24
Opt1 -> D-Link DWA-547 Wireless card

LAN is working fine, DHCP works and internet connection also works. The Wireless work if I had it as an own DHCP, 192.168.1.1 but then the computers on the LAN cant talk to the wireless computers, both are in the same subnet, 255.255.255.0.

My question, how do I bridge so all settings for LAN automatically will be used by the wireless card? And all computers can talk to each other, use the same DHCP?

I have take a look at some other threds here but some dont work and some of them I dont understand. Sorry for my english.


Logged
Noe
Newbie
*
Offline Offline

Posts: 6


View Profile
« Reply #1 on: July 06, 2011, 10:29:20 pm »

Not sure what you did wrong but they should be on different network and still communicate since those are local interfaces on the router, check Diagnostic>Routes.

You can bridge the two interface under Interface(assign) look for the bridge tab.
Logged
XIII
Sr. Member
****
Offline Offline

Posts: 582



View Profile
« Reply #2 on: July 07, 2011, 01:25:29 am »

You can have them as separate networks but still be able to talk to each other without the need for bridging, would allow you to have it so that WiFi users need to authenticate before access is given (Captive Portal) if all you want is to have the WiFi and LAN Networks be on the same broadcast domain then bridging would be the route to go. All computers can talk to each other and would use same DHCP range. What do you mean by same settings?

To set up bridging you need to go to Interfaces->OPT1 and then under IP Configuration theres an option to bridge, select Re0. You will need to setup firewall rules to allow WiFi clients to get a DHCP address.

Go to Firewall -> Rules -> OPT1 Click the Plus sign. Under protocol select any. That should be it.
Logged

-Chris Stutzman
Sys0:2.0.1: AMD Sempron 140 @2.7 1024M RAM 100GHD
Sys1:2.0.1: Intel P4 @2.66 1024M RAM 40GHD
freedns.afraid.org - Free DNS dynamic DNS subdomain and domain hosting.
Check out the pfSense Wiki
vildsvin123
Newbie
*
Offline Offline

Posts: 13


View Profile
« Reply #3 on: July 09, 2011, 01:30:23 pm »

Thanks for the help! I finally bridge the interfaces and then add a rule in the fire wall and then it worked:)
But now I got another problem, after a few days the wireless was down, when i reboot the system it worked again. What could that be? The log says "Log/System: kernel: ath0: stuck beacon; resetting (bmiss count 4)"
Logged
wallabybob
Hero Member
*****
Offline Offline

Posts: 4792


View Profile
« Reply #4 on: July 09, 2011, 06:50:30 pm »

I also have an ath wireless NIC on my pfSense. My Linux laptop reports the wireless link down from time to time and it recovers if I disable/enable wireless on the netbook. Windows laptops used by other family members don't seem to have this problem. I suspect the Linux driver, only because one form of WPA2 crypto stopped working when I did a Linux upgrade.

I also see the "bmiss" message from time to time. It doesn't seem to be anything to worry about (once in the last 21 hours).

Logged
XIII
Sr. Member
****
Offline Offline

Posts: 582



View Profile
« Reply #5 on: July 11, 2011, 11:31:09 pm »

I see it from time to time, read somewhere on the forum where jimp stated what it was but cant remember. As long as it seems to be working fine otherwise I would say you can ignore it, I do.
Logged

-Chris Stutzman
Sys0:2.0.1: AMD Sempron 140 @2.7 1024M RAM 100GHD
Sys1:2.0.1: Intel P4 @2.66 1024M RAM 40GHD
freedns.afraid.org - Free DNS dynamic DNS subdomain and domain hosting.
Check out the pfSense Wiki
vildsvin123
Newbie
*
Offline Offline

Posts: 13


View Profile
« Reply #6 on: July 12, 2011, 04:29:52 am »

Now it seems to work just fine and i ignore the bmiss shit Grin Thanks for the help
Logged
vildsvin123
Newbie
*
Offline Offline

Posts: 13


View Profile
« Reply #7 on: July 13, 2011, 04:48:24 pm »

It doesent work, after 4 days the wireless just dont work, after a rebot it works again. any suggestions?
Logged
jgleadall
Newbie
*
Offline Offline

Posts: 14


View Profile
« Reply #8 on: July 16, 2011, 10:30:57 am »

I had the same problem with a EMP-8602+S High Power 802.11a/b/g miniPCI atheros based Radio Card on an ALIX system. I eventually sent it back to the manufacture and called it defective, after testing it themselves, they agreed. might want to consider trying another radio.
Logged
vildsvin123
Newbie
*
Offline Offline

Posts: 13


View Profile
« Reply #9 on: July 20, 2011, 12:32:50 pm »

After another two days the whole system died. I returned the wireless adapter and now have a standard router as AP. my patience ran out, it might have gone to get it but so much trouble, it should not have to be. Google Translate <3 Thanks everybody
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

 

Page created in 0.029 seconds with 20 queries.