Losing my grip here and cannot think how to find the management IP address on a working wifi device.
The device should have been configured with a fixed IP below the range being issued by DHCP but within the same subnet.
Unfortunately I can no longer access the device this device from my browser. It seems likely that when saving the fixed IP it has been mis-typed and now has an out of band fixed IP.
Of course the DHCP addresses are served by the router and the wifi device is transparent to traffic passing through. The wifi device therefore works correctly but I cannot access the management controls.
I can see the MAC address of the wifi device on the wifi side but not on the lan side, although they are often adjacent. Unfortunately at this point and not helped by the heat today, I cannot think how to proceed.
Can somebody please help,
On a related matter, I would much prefer to have all management device addresses within an out of band subnet. Is this the correct approach for multiple devices residing on different subnets?
Usually, I would expect this to be the gateway IP address for your LAN. In any case, you could run an nmap scan of the entire local subnet and that will return connected hosts/ports.
Hi Deano,
It has me beat. There are three APs on the one switch which is also connected to the router, from which addresses are served. The APs are supposed to be transparent to traffic but the device static address should show up. The addresses are .5, .6 and .7 of the /24 subnet and all APs are giving SSIDs and available for wifi connection so must be active.
I have used a scanner to check 256 x 256 addresses thinking that there might have been a typo in the higher block and have tried to access all the identified active device IPs with browser. I cannot see the missing device.
Before I crawl through the loft to do a hardware factory reset I wonder what else I might try. I do have access to the end of the copper without needing to crawl so could just plug the device into a laptop but then what? Could I poke into the device from the laptop and if so which tool and and must I use twisted cable.
Hi
Install nmap/zenmap and do a scan of the network for devices and ports open, could be something like port 8080 or such, not the default of 80, may even need https (port 443).
It might be useful to provide more info about the devices you’re using. Are they Ubiquiti devices for example? (They have their own UNMS system for remote management, but also typically provide SSH and local web management access.)
As noted,
ordinarily, you should be able to connect to the DG address of the WiFi client.
I don’t know what you may mean by the Admin website possibly assigned to an address outside the DHCP scope’s NetowrkID, that’s hard for me to imagine.
In any case, there’s usually a simple solution…
Go find yourself a patch cable and make a wired connection.
The wired connection should always be configured with its own scope and network settings so if you munged up your wireless somehow, your wired should be unaffected and “just work” Again, just connect to your assigned DG address.
Hi and many thanks for the replies. Been off line as our feed was cut (by digger I believe.) I had already tried a scanner from a windoze laptop and am now back on my openSUSE machine.
None of the previous scans have worked although I am still able to use the AP. The device is an Engenius ECB350 11N device.
I have had a bit more luck with latest scan with openSUSE laptop plugged into the relevant switch and have found a Seneo device (?old name?) with an address .166 on the required subnet. It is also shows the right MAC address but I cannot access the address with browser. It just shows it trying to connect and times out.
My last thought was to plug the device (I have the copper at this end) and try and ssh into it but none of these attempts received any response. Looks like device is corrupted so I shall have to do a loft crawl unless somebody has further suggestions.
It would have been useful for you to post the output here. Did it show that the device was listening on port 80 (or port 443)? (That would indicate a listening http or https server.)
My last thought was to plug the device (I have the copper at this end) and try and ssh into it but none of these attempts received any response. Looks like device is corrupted so I shall have to do a loft crawl unless somebody has further suggestions.
Budge
Difficult to advise further without definitive output and we’re not in front of it. Perhaps you will need to factory reset it.
Hi Deano et al.,
Sorry about delay in getting info to you pending broadband fault repair.
I have scanned the subnet and the only details that appear relevant are as follows.
Host Details:-
Host is up (0.00050s latency).
MAC Address: 88:DC:96:11:6C:06 (Senao Networks)
Network Distance: 1 hop
Nmap done: 1 IP address (1 host up) scanned in 24.43 seconds
Full Scan Output Log;-
Starting Nmap 7.70 ( https://nmap.org ) at 2019-07-28 10:59 BST
NSE: Loaded 43 scripts for scanning.
Initiating ARP Ping Scan at 10:59
Scanning 172.27.169.166 [1 port]
Completed ARP Ping Scan at 10:59, 0.23s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 10:59
Completed Parallel DNS resolution of 1 host. at 10:59, 0.00s elapsed
Initiating SYN Stealth Scan at 10:59
Scanning 172.27.169.166 [1000 ports]
Completed SYN Stealth Scan at 10:59, 21.11s elapsed (1000 total ports)
Initiating Service scan at 10:59
Initiating OS detection (try #1) against 172.27.169.166
Retrying OS detection (try #2) against 172.27.169.166
NSE: Script scanning 172.27.169.166.
Initiating NSE at 10:59
Completed NSE at 10:59, 0.00s elapsed
Initiating NSE at 10:59
Completed NSE at 10:59, 0.00s elapsed
Nmap scan report for 172.27.169.166
Host is up (0.00050s latency).
All 1000 scanned ports on 172.27.169.166 are filtered
MAC Address: 88:DC:96:11:6C:06 (Senao Networks)
Too many fingerprints match this host to give specific OS details
Network Distance: 1 hop
TRACEROUTE
HOP RTT ADDRESS
1 0.50 ms 172.27.169.166
Read data files from: /usr/bin/../share/nmap
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 24.43 seconds
Raw packets sent: 2049 (94.700KB) | Rcvd: 1 (28B)
This is definitely the problem device but as I explained I do not have easy physical access. Also it is powered by PoE so I cannot watch what is going on in the device while booting.
Since I cannot log in as web page login does not appear I am stuck unless you can suggest some command lines which might work.
I get no response from ping and ssh to admin@172.27.169.166 gets nothing back either.
Budge
The easiest way to check if a port of a system is listening is using
henk@boven:~> telnet 10.0.0.137 80
Trying 10.0.0.137...
telnet: connect to address 10.0.0.137: No route to host
henk@boven:~> telnet 10.0.0.138 100
Trying 10.0.0.138...
telnet: connect to address 10.0.0.138: Connection refused
henk@boven:~> telnet 10.0.0.138 80
Trying 10.0.0.138...
Connected to 10.0.0.138.
Escape character is '^]'.
Connection closed by foreign host.
henk@boven:~>
I think I covered al possible cases:
First case: 10.0.0.137 does not exist, after a few seconds it times out with the shown message.
Second case: 10.0.0.138 does exist, but t does not listen on port 100, it immedeatly comes back with the “refused” message.
Third case: 10.0.0.138 exists and it is listening on port 80, after confirming connection, it just waits. Because we are not realy a HTTP client, a few new lines will be enough to let the server close the connection, but it is there.
Thus telnet to the system trying the ports you think could be open, is a way to go.
Hi and thanks for the suggestions. Sadly no progress on any port. I am reconciled to doing a factory reset when it is not too hot for a loft crawl.
Thanks again,
Budge
I’m curious. Does this mean you have your electronics (router, etc…) in the loft? And does that loft get extremely hot? If so, maybe, just maybe, it’s the heat that’s affecting your systems.