| 1 |
On Mon, 30 Dec 2019 17:36:45 -0600, Dale wrote: |
| 2 |
|
| 3 |
> > Isn't the IP address in the manual? |
| 4 |
> > |
| 5 |
> > Anyway, if you're using DHCP to set up your PC, run "route -n" and |
| 6 |
> > look at the gateway for 0.0.0.0 - that should be the IP address of |
| 7 |
> > your router. |
| 8 |
> > |
| 9 |
> > |
| 10 |
> |
| 11 |
> This is what I get when hooked to the new modem directly. |
| 12 |
> |
| 13 |
> |
| 14 |
> |
| 15 |
> root@fireball / # route -n |
| 16 |
> Kernel IP routing table |
| 17 |
> Destination Gateway Genmask Flags Metric Ref Use |
| 18 |
> Iface |
| 19 |
> 0.0.0.0 192.168.2.1 0.0.0.0 UG 2 0 0 |
| 20 |
> eth1 127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 |
| 21 |
> 0 lo 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 |
| 22 |
> 0 eth1 root@fireball / # |
| 23 |
> |
| 24 |
> |
| 25 |
> If I read your reply correctly, 192.168.2.1 should be the address. It |
| 26 |
> didn't work. Just for giggles, in case I was reading it wrong, I also |
| 27 |
> tried 192.168.2.0 which also didn't work. |
| 28 |
|
| 29 |
No, 192.168.2.0 wouldn't work, but 192.168.2.1 should. |
| 30 |
|
| 31 |
> So, modem broke or something else weird going on? BTW, I did do a full |
| 32 |
> reset. I pressed and held the button for a good 20 seconds. It says 7 |
| 33 |
> seconds, I wanted to be sure. It should be using the defaults from the |
| 34 |
> factory. Key word, should. |
| 35 |
|
| 36 |
It could well be, but first I'd try Jack's suggestion and power both |
| 37 |
modem and computer off, then restart the modem followed by the computer, |
| 38 |
just to make sure no remnants of your old config are confusing things. |
| 39 |
|
| 40 |
"Turn it off and on again" is probably one of Microsoft's greatest gifts |
| 41 |
to the World ;-) |
| 42 |
|
| 43 |
|
| 44 |
-- |
| 45 |
Neil Bothwick |
| 46 |
|
| 47 |
Yes, I've heard of "decaf." What's your point? |
Archives