Gentoo Archives: gentoo-user

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

Replies

Subject Author
Re: [gentoo-user] Frontier ADSL modem and IP address Dale <rdalek1967@×××××.com>
Re: [gentoo-user] Frontier ADSL modem and IP address Peter Humphrey <peter@××××××××××××.uk>