On Mon, 30 Dec 2019 17:36:45 -0600, Dale wrote: > > Isn't the IP address in the manual? > > > > Anyway, if you're using DHCP to set up your PC, run "route -n" and > > look at the gateway for 0.0.0.0 - that should be the IP address of > > your router. > > > > > > This is what I get when hooked to the new modem directly. > > > > root@fireball / # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 0.0.0.0 192.168.2.1 0.0.0.0 UG 2 0 0 > eth1 127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 > 0 lo 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 > 0 eth1 root@fireball / # > > > If I read your reply correctly, 192.168.2.1 should be the address. It > didn't work. Just for giggles, in case I was reading it wrong, I also > tried 192.168.2.0 which also didn't work.
No, 192.168.2.0 wouldn't work, but 192.168.2.1 should. > So, modem broke or something else weird going on? BTW, I did do a full > reset. I pressed and held the button for a good 20 seconds. It says 7 > seconds, I wanted to be sure. It should be using the defaults from the > factory. Key word, should. It could well be, but first I'd try Jack's suggestion and power both modem and computer off, then restart the modem followed by the computer, just to make sure no remnants of your old config are confusing things. "Turn it off and on again" is probably one of Microsoft's greatest gifts to the World ;-) -- Neil Bothwick Yes, I've heard of "decaf." What's your point?
pgp1LffOtx845.pgp
Description: OpenPGP digital signature
