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. 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/ 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 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. Dale :-) :-)
