1 |
On 2019.12.30 17:43, Dale wrote: |
2 |
> Jack wrote: |
3 |
> > On 2019.12.30 15:04, Dale wrote: |
4 |
> >> Howdy, |
5 |
> >> |
6 |
> >> I ran up on a used DSL modem that supports IPv6. It was cheap so |
7 |
> >> figured why not. Ironically, it is also a router. It's a Netgear |
8 |
> >> Frontier B90-755044-15 sometimes referred to as the 7550. |
9 |
> 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 |
15 |
> of |
16 |
> >> this is working. The lights and all come up like it should. It |
17 |
> seems |
18 |
> >> to be working fine, just can't access it to set it up. |
19 |
> >> |
20 |
> >> Is there a way to find the IP for this thing? I'm out of ideas |
21 |
> here. |
22 |
> >> Anyone own one of these and can share their defaults? Why don't |
23 |
> they |
24 |
> >> put the default IP on the bottom anyway??? |
25 |
> >> |
26 |
> >> Thanks. |
27 |
> >> |
28 |
> >> Dale |
29 |
> > I think I probably had one of those years ago, before switching to |
30 |
> > cable. If your PC uses DHCP, then you should be able to do "ip a" |
31 |
> and |
32 |
> > find the subnet (perhaps 192.168.1) You might then try 254 as the |
33 |
> > last octet. Using traceroute might also show you the address. If |
34 |
> you |
35 |
> > want/need to dig out the big guns, wireshark should also provide |
36 |
> some |
37 |
> > useful info. |
38 |
> > |
39 |
> > Jack |
40 |
> > |
41 |
> |
42 |
> I've never noticed the ip command before, not that I remember |
43 |
> anyway. I |
44 |
> did try ipconfig before tho. While I tried to use ip, I may not be |
45 |
> using it correctly. Actually, most likely I'm not. The help page was |
46 |
> little help either. |
47 |
At some point ifconfig disappeared for me, and I finally found ip as |
48 |
the closest for getting the same data. (I now do have ifconfig back.) |
49 |
I think those differences depend on specific versions of various |
50 |
network utilities. |
51 |
> |
52 |
> This is the IPs I've tried so far: |
53 |
> |
54 |
> http://192.168.0.1/ |
55 |
> http://192.168.0.5 |
56 |
> http://192.168.0.254/ |
57 |
> http://192.168.0.255/ |
58 |
> http://192.168.1.1/ |
59 |
> http://192.168.1.5 |
60 |
> http://192.168.1.254 |
61 |
> http://192.168.1.255 |
62 |
> http://192.168.2.1 |
63 |
> http://192.168.2.5 |
64 |
> http://192.168.2.254 |
65 |
> http://192.168.2.255 |
66 |
> http://192.168.254.254/ |
67 |
That last one matches something I just found on the Frontier site for |
68 |
that router. Have you tried a hard reset to factory settings on the |
69 |
router? Is there anything useful actually printed on the bottom of the |
70 |
router? You might need a bright light and a magnifying glass :-) |
71 |
> |
72 |
> I think I tried 128 on the end at one point as well. |
73 |
> |
74 |
> Even tho I have dhcp set up and the ethernet light shows it is |
75 |
> connected, I still restart eth1 just to be sure. Then I run ifconfig |
76 |
> and take the info from there to start trying addresses. I figure the |
77 |
> 3rd part might narrow it down a bit. Then I try some others even if |
78 |
> they don't make a lot of sense to try. This is what ipconfig usually |
79 |
> shows for eth1: |
80 |
> |
81 |
> |
82 |
> |
83 |
> root@fireball / # ifconfig |
84 |
> eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 |
85 |
> inet 192.168.2.5 netmask 255.255.255.0 broadcast |
86 |
> 192.168.0.255 |
87 |
Something smells fishy here. Why are inet and broadcast not on the |
88 |
same network? They should differ only in the last octet, given the |
89 |
netmask. I'm also very surprised the router is at .5 and not either .1 |
90 |
or .254. |
91 |
> inet6 fe80::201:53ff:fe80:dc35 prefixlen 64 scopeid |
92 |
> 0x20<link> |
93 |
> ether 00:01:53:80:dc:35 txqueuelen 1000 (Ethernet) |
94 |
> RX packets 43311747 bytes 60136286625 (56.0 GiB) |
95 |
> RX errors 0 dropped 0 overruns 0 frame 0 |
96 |
> TX packets 33539185 bytes 2574220465 (2.3 GiB) |
97 |
> TX errors 2 dropped 0 overruns 0 carrier 0 collisions 0 |
98 |
> |
99 |
> To be honest, it doesn't seem to change from when I'm hooked to the |
100 |
> older hardware. I dunno. |
101 |
> |
102 |
> Open to ideas if anyone has some. |
103 |
Can you get to the internet? If so, then a traceroute might show where |
104 |
the packets think they are going. If not, then you may not have a |
105 |
proper connection between the router and PC. Those mismatched network |
106 |
numbers could be the issue. (I don't know if you are sending these |
107 |
messages using that connection, or sending from another device.) |
108 |
> |
109 |
> Dale |
110 |
Jack |