• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How do I find my wireless router's IP?

F

Felecha

Golden Member

I have a LinkSys router BEFSR41, I think it is. Anyway, couple of years ago I got a NetGear WGT646 wireless router for my wife and her laptop. I know the wireless IP for setup was 192.168.0.1 but that no longer works. I remember having some kind of issue where I think the solution was to change that, but damn! I cant remember where I wrote it down. I want to get into the Admin webpage and 192.168.0.1 does not do it.

192.168.1.1 gets me into the LinkSys setup page. All the machines in the house show 192.168.1.1 as default gateway.


Is there some way to get a complete "map" of the IP's on the home network so I can find the setup for the NetGear?

Thanks

 
Run an IP scan for the entire subnet of your network (192.168.1.1 to 192.168.1.254) using Angry IP Scanner. This will show all of the active nodes in your network. Should be easy to find from here.
 
I have the Angry Scanner running, it's cool, and clear what it does - pings every IP in the specified range.

I guess I will let that run and then look at JackMDS's suggestion

Thanks a lot


 
Curious indeed, I went to my desktop, and ran networkscanner, which seems to be MUCH faster. I was running Angry Scanner on my wifes laptop.

Anyway, all 4 machines were found and the Linksys Router

192.168.1.1
192.168.1.100
192.168.1.101
192.168.1.102
192.168.1.103

But I ran it from 192.168.0.0 to 192.168.255.255. Where then is the wireless router???? If I DID change its IP, I would think I would set it to something like 192.168.0.100 or 192.168.100.1 or some kind of numbers that would be a rememberable base for a subnet. Too bad I dont seem to have written it down. Alas!!!

I must not understand something here. It IS running, 3 of the machines are connected to it.

 
Take off the Wireless Router, do a Hard reset, and connect it to one Wire computer by itself.

Make sure that the computer is on Auto obtain IP.

It should then connect to the Wireless Router, once connected configure the Wireless Router as described on this page.

Using a Wireless Router as a switch with an Access Point - http://www.ezlan.net/router_AP.html
 
But I ran it from 192.168.0.0 to 192.168.255.255. Where then is the wireless router????

Since you are on 192.168.1.0/24 - any pings sent to addresses outside the 192.168.1.0/24 subnet would be forwarded to your linksys on 192.168.1.1 - which likely dropped them, or forwarded them to the internet - where they were almost certainly dropped by your ISP.

One way to do this:

hard reset the router and research its default IP.

another way:

set your PC to each of the 254 subnets in 192.168, then rerun the IP scan. Also - nmap is a very good IP scanner.

still another way -

use wireshark - connect your PC directly to the router - turn on the router and watch for any packets. Any broadcasts will contain its MAC and possibly the source IP.



 
OK, I think I follow the ideas. I had also noted yesterday but did not mention, that when scratching my head and wondering what COULD I have reset the ip for the wireless router to, I tried 192.168.100.1, which turns out to be the webpage for the cable modem. And that address was not found in the IP scanners. So maybe the linksys was dumping the wireless ping returns

I unplugged the wireless and took it to my office and plugged the cable from my desktop into the wireless. So I had the wireless direct cabled to the desktop machine. Powered up the wireless, watched the connection "Acquiring network address". It ended up saying "Little or no connectivity" and here's the ipconfig. Local Area Connection 2 is my normal NIC name

thernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.243.111
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

I tried the cable into the "internet" port and into one of the regular 4 ports. Same thing. Hard reset of the router each time.

Plugged the desktop back into the regular network, it immediately reestablished its 192.168.1.111 connection.

[by the way, why does it get its normal ip back in a second, and acquiring network address takes forever?]

OK, still trying here

thanks
 

OK, wireshark has something I think

I wont give the whole output, but here are the points I think matter. Again, I started the shark and then plugged straight from the wireless into the desktop and watched the recording. LOTS and LOTS of calls like

18 2.004734 Apple_80:8a:15 Broadcast ARP Who has 192.168.1.67? Tell 169.254.148.116
203 29.050499 Apple_80:8a:15 Broadcast ARP Who has 59.92.44.239? Tell 169.254.148.116

So the wireless is 169.254.148.116?

Then a handful of

87 12.888524 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x2b843a56

and then a

444 65.810772 169.254.243.111 239.255.255.250 SSDP M-SEARCH * HTTP/1.1

and then a series of
445 65.835363 169.254.243.111 169.254.255.255 NBNS Registration NB <my desktop><00>

and

500 71.833882 169.254.243.111 169.254.255.255 NBNS Registration NB <my desktop><20>

All the while, interspersed with ongoing "Who has ***" calls

At the bottom I found this, which seems to identify the wireless again as 169.254.1480116

Address Resolution Protocol (request)
Hardware type: Ethernet (0x0001)
Protocol type: IP (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (0x0001)
Sender MAC address: Apple_80:8a:15 (00:23:6c:80:8a:15)
Sender IP address: 169.254.148.116 (169.254.148.116)
Target MAC address: 00:00:00_00:00:00 (00:00:00:00:00:00)
Target IP address: 0.69.220.85 (0.69.220.85)


But trying to go to 169.254.148.116 in a browser does not get anything. Neither can I ping it [all this time I am ONLY connected to the wireless


 
But then .... if the wireless router itself is 169.254.148.116, how do the computers all get 192.168.1.*? Is that because the LinkSys router is doing the assignments?
 
And as for reset to defaults, there is a button on the bottom of the wireless, which says set to factory defaults, and it also says explicitly that it will be found at 192.168.0.1 and the userid and password for default. So I CAN do that, but there was some reason I needed to do whatever I did 2 years ago now ....
 
Originally posted by: Felecha
Curious indeed, I went to my desktop, and ran networkscanner, which seems to be MUCH faster. I was running Angry Scanner on my wifes laptop.

Anyway, all 4 machines were found and the Linksys Router

192.168.1.1
192.168.1.100
192.168.1.101
192.168.1.102
192.168.1.103

But I ran it from 192.168.0.0 to 192.168.255.255. Where then is the wireless router???? If I DID change its IP, I would think I would set it to something like 192.168.0.100 or 192.168.100.1 or some kind of numbers that would be a rememberable base for a subnet. Too bad I dont seem to have written it down. Alas!!!

I must not understand something here. It IS running, 3 of the machines are connected to it.
Click to expand...

Yeah, I tried that too, to find a wireless router configured as an AP, and it didn't seem to find it either, it only found the computers. It didn't find the main router at 192.168.0.1 either.
 
The 169.254.* address is a special "link local" address which is automatically generated when the client is not assigned a static IP and fails to locate a DHCP server. In other words, this is not a "real" IP address, and just shows that your computer is not talking properly to the wireless router.

Assuming that your wireless router is actually working, one potential solution is to manually assign an IP to your computer and then try the last known IP of the router. E.g. set your computer to 192.168.0.10 in the NIC properties and then try connecting to 192.168.0.1.

If that doesn't work, you could try running the scanner from this configuration.

If all that fails, then the next step would be to reset the router to factory defaults. At that point you should reset your computer to automatically obtain an IP from the DHCP server. If you don't get an IP address (i.e. default back to 169.254.*) then your wireless router (or cable, etc.) aren't working properly, and might simply have encountered a hardware failure.

Your usage seems to fall into the "using a wireless router as just an access point", for which Jack has already linked a guide. Look at that to understand what you'd have to do to get the wireless router configured as per your needs once you connect to it.
 
As the King said in Amadeus, "Well, ... there it is."

When I set my own IP to 192.168.0.10, then I could get the login for the wireless, and it showed in the scanner, and I could ping it.

So that's the missing piece that I did not understand? If my own IP is on the 192.168.1.* subnet, the 192.168.0.* hosts are invisible?

I would have thought that in a browser I could have got to 192.168.0.1 if I explicitly enter that as the URL.

Anyway, looks like I'm all set

Thanks all of you. Every piece helped and was good learning!
 
If I'm not mistaken, the reason for that is that 192.168.x.x is a non-routable range so the router won't route from 192.168.1.0 to 192.168.0.0
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top