Note that each non-existent address will take a second to time out, so the whole scan will take upwards of four minutes.
Running it will step through all possible subnet addresses to see if there is a device on this address, and report if so. Since your router is 192.168.1.254, then any IP addresses in your subnet will probably be in the range 192.168.1.1 to 192.168.1.254, so I would propose creating the following batch file, called for example OnLine.cmd:- offįor /l %%f in (1,1,254) do ping -n 1 -w 1000 %IPrange%.%%f > nul: 2>&1 & echo %IPrange%.%%f on line Since you refer to ipconfig, I presume you are on some version of Windows, so I shall offer a solution based on this assumption. In each network tested, follow the common steps to finding the IP ( nmap, ipconfig, arp -a, etc.) For more common IPs you can check this article. If you know your access point default (or configured) IP but couldnt reach it, just check the IP's first 3 decimal numbers to know the subnet to use ( would probably be a 192.168.100.0/24 network) If done correctly, your computer might not have internet access for the moment but you will be able to log into the AP's configuration through its 192.168.1.X IP. What you can do to access it (or find it) is disabling DHCP on your computer, and set your device's IP address in the range of your AP network. Meaning your default access point's IP might be outside your local network. When you set your router in Reapeater Mode, the connection between the router and AP is done outside the network layer. If you can't find the repeater or access point (AP) IP address on your local network anywhere it might mean that your repeater's IP ISN'T in your local network. Most answers focus on the local network and finding the IP through nmap, ipconfig, main router's configuration, etc. I had this same problem today and no forum or blog post had the actual solution to my problem (that I could find).
0 kommentar(er)
