No Internet Access Through Netgear WNAP210 (Wireless Access Point)
-
There is only one port that can be plugged in on the Netgear WNAP 210
Sorry, I had assumed without looking that it was a combo WiFi AP/router. I see it is an AP that supports multi BSSID, multi VLAN.
In its AP mode it should "just work".
You need a pass rule on OPT! to allow traffic source OPT1 destination all - that will simply allow everything through to the internet.
But you already said you could plug a computer into OPT1 by cable and it works, so I assumed you have a pass rule on OPT1. -
Can the wireless client ping pfSense?
Did you disable block private networks on pfSense WAN like you have to do if you put it behind another router?
Put your modem in bridge mode and let pfSense get the public IP address from your ISP.
-
Sorry for the late reply. Other things needed attention.
No, Computer C cannot ping pfSense.
Yes, did disable block private networks…
Currently pfSense is in a test environment while I try to get everything working properly.
-
Sorry for the late reply. Other things needed my attention.
I did try the following: https://forum.pfsense.org/index.php?topic=47519.0
I thought this was created by default but if not:
If you look at the LAN tab, then the OPT1 tab they should look the same. 1 rule each.Select from the Menu: Firewall -> Rules then click the OPT1 tab. There should be 1 rule, which is the same as the under the LAN tab, except that it is named OPT1.
* OPT1 net * * * * none Default allow OPT1 to Any ruleIf not add it by clicking the little '+' sign in the small grey button to the right and it will open a rule form, 'e' to edit.
Select the following:
Interface: 'OPT1'
Protocol: 'Any'
Source: 'OPT1 subnet'
Destination: 'Any'
Description: 'Default allow OPT1 to Any rule' This will allow everything outbound.If there is a rule pointing to LAN you may want to remove this, or modify it to allow only the traffic to access particular services.
But still no Internet access :-\
-
People who understand how things work have no problem getting pfSense to do what's expected. People who don't have a grasp of the basics have trouble. Same with any networking appliance.
-
People who understand how things work have no problem getting pfSense to do what's expected. People who don't have a grasp of the basics have trouble. Same with any networking appliance.
OK, why don't teach me what exactly I am doing wrong if it so painfully obvious to you that you need to look down on me?
-
If you have cascading routers setup, well then 1st:
If ISP router-LAN ==10.0.0.1/24; pfSense-WAN =>10.0.0.2;
then pfSense-LAN =>192.168.1.1/24; pfSense-OPT1 =>192.168.2.1/24; -
@hda:
If you have cascading routers setup, well then 1st:
If ISP router-LAN ==10.0.0.1/24; pfSense-WAN =>10.0.0.2;
then pfSense-LAN =>192.168.1.1/24; pfSense-OPT1 =>192.168.2.1/24;pfSense WAN is on the same subnet as the modem/router.
WAN: 192.168.1.2
LAN: 192.168.2.1
OPT1: 192.168.3.1
/24 was implied for all.
-
That. is. not. good. for. clarity.
pfSense-box is a router. I gave you a solution.
-
@hda:
That. is. not. good.
pfSense-box is a router. I gave you a solution.
Why is that not good? IP modem / router 192.168.1.1 –> pfSense WAN 192.168.1.2
Why does the pfSense WAN and LAN have to be on different bit block ranges?
-
Clear & reliable config of the network is prerequisite. You make errors like in reply #6.
