| 1 |
Neil Bothwick wrote: |
| 2 |
> On Mon, 30 Dec 2019 14:04:46 -0600, Dale wrote: |
| 3 |
> |
| 4 |
>> I ran up on a used DSL modem that supports IPv6. It was cheap so |
| 5 |
>> figured why not. Ironically, it is also a router. It's a Netgear |
| 6 |
>> Frontier B90-755044-15 sometimes referred to as the 7550. Anyway, I |
| 7 |
>> tried all the usual IPs to access the thing, no luck. I tried resetting |
| 8 |
>> it, holding the reset button for 7 seconds. That didn't help either. |
| 9 |
>> I've googled and tried all the IPs I can find that way too. None of |
| 10 |
>> this is working. The lights and all come up like it should. It seems |
| 11 |
>> to be working fine, just can't access it to set it up. |
| 12 |
> Isn't the IP address n the manual? |
| 13 |
> |
| 14 |
> Anyway, if you're using DHCP to set up your PC, run "route -n" and look |
| 15 |
> at the gateway for 0.0.0.0 - that should be the IP address of your router. |
| 16 |
> |
| 17 |
> |
| 18 |
|
| 19 |
This is what I get when hooked to the new modem directly. |
| 20 |
|
| 21 |
|
| 22 |
|
| 23 |
root@fireball / # route -n |
| 24 |
Kernel IP routing table |
| 25 |
Destination Gateway Genmask Flags Metric Ref Use |
| 26 |
Iface |
| 27 |
0.0.0.0 192.168.2.1 0.0.0.0 UG 2 0 0 eth1 |
| 28 |
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo |
| 29 |
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 |
| 30 |
root@fireball / # |
| 31 |
|
| 32 |
|
| 33 |
If I read your reply correctly, 192.168.2.1 should be the address. It |
| 34 |
didn't work. Just for giggles, in case I was reading it wrong, I also |
| 35 |
tried 192.168.2.0 which also didn't work. |
| 36 |
|
| 37 |
So, modem broke or something else weird going on? BTW, I did do a full |
| 38 |
reset. I pressed and held the button for a good 20 seconds. It says 7 |
| 39 |
seconds, I wanted to be sure. It should be using the defaults from the |
| 40 |
factory. Key word, should. |
| 41 |
|
| 42 |
Ideas? |
| 43 |
|
| 44 |
Dale |
| 45 |
|
| 46 |
:-) :-) |
| 47 |
|
| 48 |
P. S. Your sig was funny. lol |
Archives