On Wednesday 25 December 2002 09:38 pm, Lyvim Xaphir wrote: > On Wed, 2002-12-25 at 20:35, Barry Premeaux wrote: > > I gave that a shot, but it didn't make a difference. > > > > Although, it seems to be a mute point for now. In tinkering with LILO (I > > also boot RH8.0 and SuSE8.0 from this machine), I hosed the boot loader. > > Had difficulty getting CD1's rescue mode to see the reiserfs of my 9.0 > > load, so I simply went back to a fresh install. (No, I didn't make a > > boot floppy the first time, but I did this time. Lesson learned.) > > > > Everything is back up and running again for now. I'll have to watch it > > as I begin retracing my steps with the firewall and updates again. > > > > Thanks for responding. > > > > Barry > > Sometimes Kppp will not route like it is supposed to. I had this > problem some ages ago when I was on a dialup, but it's been quite a > while. > > Try the following. When kppp connects, note the ip address. Then from > a root command prompt do > > route add default gw your.isp.dynamic.ip ppp0 > > > In my case (in case you're interested) the final qualifier on my > workstation here is eth0 instead of ppp0. If you were on a local lan > attempting to connect to a gateway, you'd use the same route command > line as above but just changing the device. > > This is a manual fix, a way to test. You should be able to ping out > after you do this. > > --LX
Thank you for the info. I had just completed some KDE updates prior to the routing problem. It may be that one of the packages didn't set well with Kppp. Barry
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
