WAP not responding but seeing ….
-
I am trying to get to the web configuration for a wireless access point. When I hit it via the url I see
PRIVATE tcp 10.255.0.21:80 <- 10.2.0.235:44607 CLOSED:SYN_SENT
PUBLIC tcp 10.2.0.235:44607 -> 10.255.0.21:80 SYN_SENT:CLOSEDCan somebody educate me on what this exchange means and what I might try to do to get it responsive again?
Thanks, from a newbie!
Rob -
why would you be going through pfsense to get to a AP.. Is this access point on a different segment then where you coming from?
looks like 10.2.0.235 talked to 10.255.0.21
Could you draw your network.. Where is this WAP.. Is it on your wan of pfsense? On a different segment/vlan?
-
We have a PRIVATE switch that goes to an interface on pfsense that has dhcp server (10.2.0.0). This interface has its own WAN (uverse 1)
We have a PUBLIC switch that goes to an interface on pfsense that has a dhcp server (10.255.0.0) going to its own WAN (uverse #2)I setup the private network to be able to find resources on the public network. The public switch has 5 WAPs on it. Every so often, one of these public waps is unreachable, can't get to its admin screen nor ping it. If I power down all the public WAPS and recycle the pfsense box followed by turning on the public waps … all are responsive. I just hit this again and I was hoping to see what is happening so I don't have to power recycle everything.
Does that help any? Sorry for the newbie description. I am still learning.
Rob
-
so both of these wans are on pfsense and you just do PBR to tell which network uses which wan.
And these waps all use pfsense interface on private and public as their gateway.
What are you rules on private and public interfaces?
How are these waps IPs setup? Quite often waps might not have gateway on how to get off their own segment. Can you ping the WAP from the pfsense interface on that segment?
-
Thank you for your help and patience.
Can you ping the WAP from the pfsense interface on that segment? - No. It gives 100% packet loss trying to ping 10.255.0.1 to 10.255.0.21 (the one failing right now).
How are these waps IPs setup? - DHCP and I have a mac address mapping for each wap in the pfsense DHCP config. So they get specific ips.
I've attached the rules for the public and private interface. On the public rules you'll see PublicNetworkAlias it is 10.255.0.0/23 and the PrivateNetworkAlias is 10.2.0.0/24
Rob
-
"Can you ping the WAP from the pfsense interface on that segment? - No."
Well that tells me something wrong with network to the wap or the wap themselves. Do they maybe loose their lease and not renew.. You say if you bounce them then everything works?
