APU set up with Wi-Fi
-
Oops, I missed the Wi-Fi tab.
That fixed it, Wi-Fi working.Now I can try some of the snort and firewall advanced things, but the basics seem to be running for now.
Oh, I need to set the security to a MAC filter like my old router, so I will research how to do that.Thanks for the help:-)
-
It was working, however my mobile was connecting to the old router which has the MAC filter setup.
I haven't been able to setup a MAC filter on pfSense yet.
Today I tried to move the mobile over from the old router Wi-Fi to the pfSense Wi-Fi, however the pfSense Wi-Fi network is not found?So, 2 problems:
1. pfSense Wi-Fi network not found.
2. pfSense MAC filter not available for security?
I prefer a MAC filter as:
everything is blocked.
only permitted devices can connect.
no encryption means faster transmission rates.
as secure as a 12 character password. (yes, maybe 8 character password if a hacker knows the first 4 MAC character common to manufacturers). -
It was working, however my mobile was connecting to the old router which has the MAC filter setup.
I haven't been able to setup a MAC filter on pfSense yet.
Today I tried to move the mobile over from the old router Wi-Fi to the pfSense Wi-Fi, however the pfSense Wi-Fi network is not found?So, 2 problems:
1. pfSense Wi-Fi network not found.If you can't see the network with your mobile device, i suggest installing a wifi analyzer akin to:
https://play.google.com/store/apps/details?id=com.farproc.wifi.analyzer&hl=en2. pfSense MAC filter not available for security?
A MAC filter provides zero security.
All you need is a device with which you can listen to traffic on the air, so basically everything which is capable of connecting to said access point. After that change your own MAC to one of the "allowed" addresses.I prefer a MAC filter as:
everything is blocked.
only permitted devices can connect.
no encryption means faster transmission rates.This is something you REALLY don't want to do.
No encryption does not increase the speed.
Everyone with a wlan capable device can listen to whatever you transmit over the air.
The only thing that changes is the time it takes to connect to the network.
And even then we are talking about 5ms increased time until you are connected.
You really need to have WPA2 (or at least WPA).as secure as a 12 character password. (yes, maybe 8 character password if a hacker knows the first 4 MAC character common to manufacturers).
Not sure what you are talking here about. The password has absolutely nothing to do with the MAC addresses.
For WPA2 the password has a minimal length of 8 characters and can be up to 63 characters. -
Thank you for the reply.
My mobile has a regular Wi-Fi finder which finds other working Wi-Fi networks.
Other devices also find Wi-Fi networks and not the pfSense Wi-Fi network.
So I don't think there's a need to download another Wi-Fi finding app.Ok, I will setup the pfSense Wi-Fi network on WPA2 password encryption, once the pfSense Wi-Fi works.
-
What channel is your pfSense wifi card using? It may be one that your phone cannot use, 12,13 or 14 for example.
Steve
-
Another thing which could be wrong: Did you set the channel specifically or did you set it to "auto"?
I've seen cards not work with the "auto" setting. -
Thanks.
I think I found the right information under pfSense > Dashboard: Interfaces: WIFI > Common wireless configuration - Settings apply to all wireless network on ath0. > Channel: Auto.
There are 37 other manual channels to choose from?I should mention all devices on Wi-Fi don't find the pfSense Wi-Fi network.
-
Ok, I just tried 3 channels from the choice of 37 channels.
11b/g/n - 1 (2412 MHz @ 31.5 / 20)
11a/n - 36 (5180 MHz @ 31.5 / 30)
11a/n - 100 (5500 MHz @ 31.5 / 30)No change though.
-
You're still running 2.1.X right? Then you shouldn't be seeing any 'N' channels. Are you using 'A'? Use 802.11G mode only and you should be OK.
Steve
-
Yes, I'm on pfSense Version 2.1.4-RELEASE (amd64) FreeBSD 8.3-RELEASE-p16.
The Wi-Fi Interface Standard is 802.11g.
The Wi-Fi Interface Channel is Auto. -
802.11g channels are 1-11 almost everywhere, 1-13 in some places including the UK and some other places can use 14 (Japan?). If you're using G mode then it shouldn't allow you to select anything in the 5GHz ranges. My own card here is G only so I can't be 100% sure what you'll see. Anything in the logs?
Steve
Edit: confusing typo
-
802.11g channels are 1-11 almost everywhere, 1-13 in some places including the UK and some other places can use 14 (Japan?). If you're using G mode then it should allow you to select anything in the 5GHz ranges. My own card here is G only so I can't be 100% sure what you'll see. Anything in the logs?
Steve
Didn't you mean 2.4GHz ;)
5GHz is 802.11aYes, I'm on pfSense Version 2.1.4-RELEASE (amd64) FreeBSD 8.3-RELEASE-p16.
The Wi-Fi Interface Standard is 802.11g.
The Wi-Fi Interface Channel is Auto.Don't set the channel to auto.
Set it as a test to 2412 (channel 1) b/g -
Ok, I set the Wi-Fi to:
Standard: 802.11g
Channel: 11b/g/n - 1 (2412 MHz @ 31.5 / 20)Weird, now the mobile finds the network, but didn't just before.
I also updated pfSense which might have helped.Anyways, now that the mobile is finding the pfSense Wi-Fi network, I might be able to somehow turn off the old router Wi-Fi and then set pfSense with WPA2 and a secure password for users.
Bye bye old MAC filter list on the old router Wi-Fi :-( -
Use 1, 6, or 11 please. Pretend 2-5 and 7-10 don't exist.
-
Didn't you mean 2.4GHz ;)
Yes. I meant to write 'shouldn't be able to select 5GHz' and somehow failed. ::)
Steve
-
Thank you.
Wi-Fi network seems to be working and WPA2 password authentication working.
See how it goes with some other mobiles when visitors test it during the week.
