1 |
Jack wrote: |
2 |
> On 2019.12.30 15:04, Dale wrote: |
3 |
>> Howdy, |
4 |
>> |
5 |
>> I ran up on a used DSL modem that supports IPv6. It was cheap so |
6 |
>> figured why not. Ironically, it is also a router. It's a Netgear |
7 |
>> Frontier B90-755044-15 sometimes referred to as the 7550. Anyway, I |
8 |
>> tried all the usual IPs to access the thing, no luck. I tried resetting |
9 |
>> it, holding the reset button for 7 seconds. That didn't help either. |
10 |
>> I've googled and tried all the IPs I can find that way too. None of |
11 |
>> this is working. The lights and all come up like it should. It seems |
12 |
>> to be working fine, just can't access it to set it up. |
13 |
>> |
14 |
>> Is there a way to find the IP for this thing? I'm out of ideas here. |
15 |
>> Anyone own one of these and can share their defaults? Why don't they |
16 |
>> put the default IP on the bottom anyway??? |
17 |
>> |
18 |
>> Thanks. |
19 |
>> |
20 |
>> Dale |
21 |
> I think I probably had one of those years ago, before switching to |
22 |
> cable. If your PC uses DHCP, then you should be able to do "ip a" and |
23 |
> find the subnet (perhaps 192.168.1) You might then try 254 as the |
24 |
> last octet. Using traceroute might also show you the address. If you |
25 |
> want/need to dig out the big guns, wireshark should also provide some |
26 |
> useful info. |
27 |
> |
28 |
> Jack |
29 |
> |
30 |
|
31 |
I've never noticed the ip command before, not that I remember anyway. I |
32 |
did try ipconfig before tho. While I tried to use ip, I may not be |
33 |
using it correctly. Actually, most likely I'm not. The help page was |
34 |
little help either. |
35 |
|
36 |
This is the IPs I've tried so far: |
37 |
|
38 |
http://192.168.0.1/ |
39 |
http://192.168.0.5 |
40 |
http://192.168.0.254/ |
41 |
http://192.168.0.255/ |
42 |
http://192.168.1.1/ |
43 |
http://192.168.1.5 |
44 |
http://192.168.1.254 |
45 |
http://192.168.1.255 |
46 |
http://192.168.2.1 |
47 |
http://192.168.2.5 |
48 |
http://192.168.2.254 |
49 |
http://192.168.2.255 |
50 |
http://192.168.254.254/ |
51 |
|
52 |
I think I tried 128 on the end at one point as well. |
53 |
|
54 |
Even tho I have dhcp set up and the ethernet light shows it is |
55 |
connected, I still restart eth1 just to be sure. Then I run ifconfig |
56 |
and take the info from there to start trying addresses. I figure the |
57 |
3rd part might narrow it down a bit. Then I try some others even if |
58 |
they don't make a lot of sense to try. This is what ipconfig usually |
59 |
shows for eth1: |
60 |
|
61 |
|
62 |
|
63 |
root@fireball / # ifconfig |
64 |
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 |
65 |
inet 192.168.2.5 netmask 255.255.255.0 broadcast 192.168.0.255 |
66 |
inet6 fe80::201:53ff:fe80:dc35 prefixlen 64 scopeid 0x20<link> |
67 |
ether 00:01:53:80:dc:35 txqueuelen 1000 (Ethernet) |
68 |
RX packets 43311747 bytes 60136286625 (56.0 GiB) |
69 |
RX errors 0 dropped 0 overruns 0 frame 0 |
70 |
TX packets 33539185 bytes 2574220465 (2.3 GiB) |
71 |
TX errors 2 dropped 0 overruns 0 carrier 0 collisions 0 |
72 |
|
73 |
|
74 |
|
75 |
To be honest, it doesn't seem to change from when I'm hooked to the |
76 |
older hardware. I dunno. |
77 |
|
78 |
Open to ideas if anyone has some. |
79 |
|
80 |
Dale |
81 |
|
82 |
:-) :-) |