1 |
Jack wrote: |
2 |
> On 2019.12.30 17:43, Dale wrote: |
3 |
>> Jack wrote: |
4 |
>> > On 2019.12.30 15:04, Dale wrote: |
5 |
>> >> Howdy, |
6 |
>> >> |
7 |
>> >> I ran up on a used DSL modem that supports IPv6. It was cheap so |
8 |
>> >> figured why not. Ironically, it is also a router. It's a Netgear |
9 |
>> >> Frontier B90-755044-15 sometimes referred to as the 7550. Anyway, I |
10 |
>> >> tried all the usual IPs to access the thing, no luck. I tried |
11 |
>> resetting |
12 |
>> >> it, holding the reset button for 7 seconds. That didn't help |
13 |
>> either. |
14 |
>> >> I've googled and tried all the IPs I can find that way too. None of |
15 |
>> >> this is working. The lights and all come up like it should. It |
16 |
>> seems |
17 |
>> >> to be working fine, just can't access it to set it up. |
18 |
>> >> |
19 |
>> >> Is there a way to find the IP for this thing? I'm out of ideas |
20 |
>> here. |
21 |
>> >> Anyone own one of these and can share their defaults? Why don't they |
22 |
>> >> put the default IP on the bottom anyway??? |
23 |
>> >> |
24 |
>> >> Thanks. |
25 |
>> >> |
26 |
>> >> Dale |
27 |
>> > I think I probably had one of those years ago, before switching to |
28 |
>> > cable. If your PC uses DHCP, then you should be able to do "ip a" and |
29 |
>> > find the subnet (perhaps 192.168.1) You might then try 254 as the |
30 |
>> > last octet. Using traceroute might also show you the address. If you |
31 |
>> > want/need to dig out the big guns, wireshark should also provide some |
32 |
>> > useful info. |
33 |
>> > |
34 |
>> > Jack |
35 |
>> > |
36 |
>> |
37 |
>> I've never noticed the ip command before, not that I remember anyway. I |
38 |
>> did try ipconfig before tho. While I tried to use ip, I may not be |
39 |
>> using it correctly. Actually, most likely I'm not. The help page was |
40 |
>> little help either. |
41 |
> At some point ifconfig disappeared for me, and I finally found ip as |
42 |
> the closest for getting the same data. (I now do have ifconfig |
43 |
> back.) I think those differences depend on specific versions of |
44 |
> various network utilities. |
45 |
|
46 |
Somehow I have both. |
47 |
|
48 |
>> |
49 |
>> This is the IPs I've tried so far: |
50 |
>> |
51 |
>> http://192.168.0.1/ |
52 |
>> http://192.168.0.5 |
53 |
>> http://192.168.0.254/ |
54 |
>> http://192.168.0.255/ |
55 |
>> http://192.168.1.1/ |
56 |
>> http://192.168.1.5 |
57 |
>> http://192.168.1.254 |
58 |
>> http://192.168.1.255 |
59 |
>> http://192.168.2.1 |
60 |
>> http://192.168.2.5 |
61 |
>> http://192.168.2.254 |
62 |
>> http://192.168.2.255 |
63 |
>> http://192.168.254.254/ |
64 |
> That last one matches something I just found on the Frontier site for |
65 |
> that router. Have you tried a hard reset to factory settings on the |
66 |
> router? Is there anything useful actually printed on the bottom of |
67 |
> the router? You might need a bright light and a magnifying glass :-) |
68 |
|
69 |
Nope. Usually, they stick the default IP and way back in the stone age |
70 |
of puters, a default password. If worse comes to worse, reset and start |
71 |
fresh with known info. This one has nothing about a IP address or |
72 |
anything like it. It has some info for the wireless part but that's |
73 |
it. It has a Mac address but I don't think that works in my browser. |
74 |
|
75 |
|
76 |
>> |
77 |
>> I think I tried 128 on the end at one point as well. |
78 |
>> |
79 |
>> Even tho I have dhcp set up and the ethernet light shows it is |
80 |
>> connected, I still restart eth1 just to be sure. Then I run ifconfig |
81 |
>> and take the info from there to start trying addresses. I figure the |
82 |
>> 3rd part might narrow it down a bit. Then I try some others even if |
83 |
>> they don't make a lot of sense to try. This is what ipconfig usually |
84 |
>> shows for eth1: |
85 |
>> |
86 |
>> |
87 |
>> |
88 |
>> root@fireball / # ifconfig |
89 |
>> eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 |
90 |
>> inet 192.168.2.5 netmask 255.255.255.0 broadcast 192.168.0.255 |
91 |
> Something smells fishy here. Why are inet and broadcast not on the |
92 |
> same network? They should differ only in the last octet, given the |
93 |
> netmask. I'm also very surprised the router is at .5 and not either |
94 |
> .1 or .254. |
95 |
|
96 |
I noticed that too. I don't recall ever seeing it set up that way and |
97 |
it makes me curious. That said, I tried all the usual options with the |
98 |
first two parts for both addresses. No joy. |
99 |
|
100 |
>> inet6 fe80::201:53ff:fe80:dc35 prefixlen 64 scopeid 0x20<link> |
101 |
>> ether 00:01:53:80:dc:35 txqueuelen 1000 (Ethernet) |
102 |
>> RX packets 43311747 bytes 60136286625 (56.0 GiB) |
103 |
>> RX errors 0 dropped 0 overruns 0 frame 0 |
104 |
>> TX packets 33539185 bytes 2574220465 (2.3 GiB) |
105 |
>> TX errors 2 dropped 0 overruns 0 carrier 0 collisions 0 |
106 |
>> |
107 |
>> To be honest, it doesn't seem to change from when I'm hooked to the |
108 |
>> older hardware. I dunno. |
109 |
>> |
110 |
>> Open to ideas if anyone has some. |
111 |
> Can you get to the internet? If so, then a traceroute might show |
112 |
> where the packets think they are going. If not, then you may not have |
113 |
> a proper connection between the router and PC. Those mismatched |
114 |
> network numbers could be the issue. (I don't know if you are sending |
115 |
> these messages using that connection, or sending from another device.) |
116 |
>> |
117 |
>> Dale |
118 |
> Jack |
119 |
> |
120 |
|
121 |
|
122 |
Right now, I'm on my old hardware. When I hook up the new, to me, |
123 |
hardware, I have to disconnect the old hardware. If nothing else, I was |
124 |
concerned both might have the same address, both being modems basically, |
125 |
and would result in a conflict. When I connect to the new hardware, I |
126 |
can't get anywhere, yet. The DSL signal is there since the light is on |
127 |
but it can't connect since I can't access it to give it the |
128 |
user/password info. |
129 |
|
130 |
I've never ran into this before. Usually when I buy a modem or a |
131 |
router, I can eventually find it without even googling for the IP. |
132 |
Generally the ones listed above will get me to the new device. This |
133 |
one, has me stumped. Either it is broke somehow or it has one strange |
134 |
ip address. |
135 |
|
136 |
Thanks for the help. Maybe I'll find gold at some point. ;-) |
137 |
|
138 |
Dale |
139 |
|
140 |
:-) :-) |