Jack wrote: > On 2019.12.30 17:43, Dale wrote: >> Jack wrote: >> > On 2019.12.30 15:04, Dale wrote: >> >> Howdy, >> >> >> >> I ran up on a used DSL modem that supports IPv6. It was cheap so >> >> figured why not. Ironically, it is also a router. It's a Netgear >> >> Frontier B90-755044-15 sometimes referred to as the 7550. Anyway, I >> >> tried all the usual IPs to access the thing, no luck. I tried >> resetting >> >> it, holding the reset button for 7 seconds. That didn't help >> either. >> >> I've googled and tried all the IPs I can find that way too. None of >> >> this is working. The lights and all come up like it should. It >> seems >> >> to be working fine, just can't access it to set it up. >> >> >> >> Is there a way to find the IP for this thing? I'm out of ideas >> here. >> >> Anyone own one of these and can share their defaults? Why don't they >> >> put the default IP on the bottom anyway??? >> >> >> >> Thanks. >> >> >> >> Dale >> > I think I probably had one of those years ago, before switching to >> > cable. If your PC uses DHCP, then you should be able to do "ip a" and >> > find the subnet (perhaps 192.168.1) You might then try 254 as the >> > last octet. Using traceroute might also show you the address. If you >> > want/need to dig out the big guns, wireshark should also provide some >> > useful info. >> > >> > Jack >> > >> >> I've never noticed the ip command before, not that I remember anyway. I >> did try ipconfig before tho. While I tried to use ip, I may not be >> using it correctly. Actually, most likely I'm not. The help page was >> little help either. > At some point ifconfig disappeared for me, and I finally found ip as > the closest for getting the same data. (I now do have ifconfig > back.) I think those differences depend on specific versions of > various network utilities.
Somehow I have both. >> >> This is the IPs I've tried so far: >> >> http://192.168.0.1/ >> http://192.168.0.5 >> http://192.168.0.254/ >> http://192.168.0.255/ >> http://192.168.1.1/ >> http://192.168.1.5 >> http://192.168.1.254 >> http://192.168.1.255 >> http://192.168.2.1 >> http://192.168.2.5 >> http://192.168.2.254 >> http://192.168.2.255 >> http://192.168.254.254/ > That last one matches something I just found on the Frontier site for > that router. Have you tried a hard reset to factory settings on the > router? Is there anything useful actually printed on the bottom of > the router? You might need a bright light and a magnifying glass :-) Nope. Usually, they stick the default IP and way back in the stone age of puters, a default password. If worse comes to worse, reset and start fresh with known info. This one has nothing about a IP address or anything like it. It has some info for the wireless part but that's it. It has a Mac address but I don't think that works in my browser. >> >> I think I tried 128 on the end at one point as well. >> >> Even tho I have dhcp set up and the ethernet light shows it is >> connected, I still restart eth1 just to be sure. Then I run ifconfig >> and take the info from there to start trying addresses. I figure the >> 3rd part might narrow it down a bit. Then I try some others even if >> they don't make a lot of sense to try. This is what ipconfig usually >> shows for eth1: >> >> >> >> root@fireball / # ifconfig >> eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >> inet 192.168.2.5 netmask 255.255.255.0 broadcast 192.168.0.255 > Something smells fishy here. Why are inet and broadcast not on the > same network? They should differ only in the last octet, given the > netmask. I'm also very surprised the router is at .5 and not either > .1 or .254. I noticed that too. I don't recall ever seeing it set up that way and it makes me curious. That said, I tried all the usual options with the first two parts for both addresses. No joy. >> inet6 fe80::201:53ff:fe80:dc35 prefixlen 64 scopeid 0x20<link> >> ether 00:01:53:80:dc:35 txqueuelen 1000 (Ethernet) >> RX packets 43311747 bytes 60136286625 (56.0 GiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 33539185 bytes 2574220465 (2.3 GiB) >> TX errors 2 dropped 0 overruns 0 carrier 0 collisions 0 >> >> To be honest, it doesn't seem to change from when I'm hooked to the >> older hardware. I dunno. >> >> Open to ideas if anyone has some. > Can you get to the internet? If so, then a traceroute might show > where the packets think they are going. If not, then you may not have > a proper connection between the router and PC. Those mismatched > network numbers could be the issue. (I don't know if you are sending > these messages using that connection, or sending from another device.) >> >> Dale > Jack > Right now, I'm on my old hardware. When I hook up the new, to me, hardware, I have to disconnect the old hardware. If nothing else, I was concerned both might have the same address, both being modems basically, and would result in a conflict. When I connect to the new hardware, I can't get anywhere, yet. The DSL signal is there since the light is on but it can't connect since I can't access it to give it the user/password info. I've never ran into this before. Usually when I buy a modem or a router, I can eventually find it without even googling for the IP. Generally the ones listed above will get me to the new device. This one, has me stumped. Either it is broke somehow or it has one strange ip address. Thanks for the help. Maybe I'll find gold at some point. ;-) Dale :-) :-)
