You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

YAST configures the internal modem settings & driver, but the modem doesn't make DHCP requests to get an IP address (YES, I HAVE THE MODEM SET TO USE DHCP!). KInternet shows the plug icon with the lightning bolt, so I have to manually execute #ifconfig eth0 and #ifup eth0 to get the connection to show that it is on-line, but still nothing.

#IP still shows the local host IP addr of 127.x.x.x, so my conclusion is that the IP stack code never got the DHCP request sent to the router. I cannot ping the router, nor can I ping URL's because there is no DNS translation. YAST sees the modem, configures it with everything I/it thinks it needs, yet the Rx & Tx packet counts from the NIC card are 0 (nothing is being sent or received obviously. Status light on the LAN NIC card shows green (OK).

I am a Linux Newbie after many years on WinDoze, so I'm applying my Networking experience there to what I think should be happening in SUSE Linux. Comments? Been there, fixed this before? Thanks.

Having received no obvious answers (there were none), I solved the problem by updating the default kernel from 2.6.8 (out of the SUSE 9.2 distro box) to the latest 2.6.8-24.11 downloaded from one of the Internet distro mirrors all over the world. YAST installed it, I rebooted it, and Konqueror worked the first time I connected to a SUSE website; it asked if I would accept a cookie. Eureka!