Hiya Kevin,
I assume that after the route command finishes you are still not on the network. But i am not 100% clear on that from you letter. I know of a temporary fix for this that may(??) work for you. I also have a Linksys Cable/DSL router. Hopefully someone will respond with a real fix. Also, maybe someone(a network guru to me) can explain a little better to me what the -pointopoint option is in ifconfig with more detail than the man page. I worked pretty hard to figure this out when I had trouble getting online and needed to do it manually. I cracked open several man pages and did much reading. The numbers used here are examples only. Here it is.... P3V4X:~# ifconfig eth0 down P3V4X:~# ifconfig eth0 inet netmask 255.255.255.0 -pointopoint 192.168.1.100 address 192.168.1.100 P3V4X:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 P3V4X:~# route add default gw 192.168.1.1 P3V4X:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 Hope that helps somehow, and good luck, Jimmy Richards On Saturday 31 March 2001 17:07, Kevin C. Smith wrote: > I installed Debian 2.2_R2 today on my second computer. It was running > Redhat then Progeny RC1 just fine. After installing Debian I am unable to > reach (ping) my gateway. > > #ifconfig (results are fine). > #route (takes a long time to finish, taking time with default gateway, > but when it does finish, 15 minutes later, results are fine). > > The correct module is loaded (tulip), the NIC is recognized during boot. > Use the same NIC on the other computer running Debian unstable, without > trouble. > > What am I missing. Progeny autoconfigured fine, so know I am missing > something. > > PS. The lights on my Linksys Etherfast Cable router show the connection > to this computer is failing every 10-15 seconds. > > Thanks,
