The cause of this may have happened some time ago, and I am only just noticing it now, but I can’t seem to access the Web GUI for my wireless access point from any box within my LAN.
I have a Buffalo WZR-600DHP wireless router that is setup on my network exclusively as a wireless access point for local wireless devices. It is not doing any routing, but is purely a wireless access point. It has been setup this way for a couple of years and I know I have been able to access the web interface since it was setup as an AP.
The last significant change I made to my network was to install a managed switch and create two VLANs on the switch for establishing private and a guest wireless network SSIDs on the access point. This change occurred about a year ago and it has been working as expected.
My network configuration to the access point looks like this:
Incoming WAN ---> pfSense Gateway / Router / Firewall ---> Managed Switch (Netgear) with 3 VLANs (1=home wired vlan, 20=private wireless vlan, 30=guest wireless vlan) ---> Buffalo AP
pfSense Router = 192.168.123.2
Netgear Switch = 192.168.123.4
Wired LAN = 192.168.123.xxx
Private Wlan = 192.168.124.xxx
Guest Wlan = 192.168.133.xxx
Buffalo AP = 192.168.123.5 (according to my setup notes)
I think I recall being able to access the Web GUI of the access point since I setup the VLANs, but not entirely sure since I had not needed to access it since then. I know I accessed it during the process of setting up the VLANs. I don’t have any notes during this process that indicates I needed to do anything special to access the Web GUI.
I have tried numerous different things to connect, including disconnecting the Access Point from my router and making a direct wired connection to a laptop, even trying a crossover cable, and plugging into LAN or the WAN ports of the AP. And too many other possibilities to list here. Nothing has been successful yet. The results I think that are pertinent to describe here as a starting point to continue this are the ping and network scan results listed below. The results I am seeing in a ping test from both a PC in the LAN and the pfSense router indicate that the IP address for the AP doesn’t exist.
From LAN PC, 192.168.123.20
C:\WINDOWS\system32>ping 192.168.123.5
Pinging 192.168.123.5 with 32 bytes of data:
Reply from 192.168.123.20: Destination host unreachable.
Reply from 192.168.123.20: Destination host unreachable.
Reply from 192.168.123.20: Destination host unreachable.
Reply from 192.168.123.20: Destination host unreachable.
Ping statistics for 192.168.123.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
From pfSense box (router), 192.168.123.2
PING 192.168.123.5 (192.168.123.5) from 192.168.123.2: 56 data bytes
--- 192.168.123.5 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
At first from this I thought that maybe I had messed up my routing when I setup the VLANs, or maybe the AP was actually assigned a different IP address than what I had listed in my notes. So, I started Nmap from the LAN PC and did a scan of the 192.168.123.0/24 network. The results from this did not identify the AP anywhere in the network, but correctly identified everything else.
So, I expanded the Nmap test and did a scan on the 192.168.0.0/16 network. The results of this did not identify the AP anywhere in the network. However, the scan did successfully find computers in the network on the other side of the VPN the LAN PC was connected to at the time of the scan.
So now I have run out of ideas to test, and am wondering if someone can point me to where my knowledge is lacking. I am thinking the issue might lie in my VLAN configuration, since my experience with VLANs is pretty limited and I might not see a configuration error while looking right at it.
Can someone please educate me on where I should be looking next. Thanks.