Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
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.
Click Here to receive this Complete Guide absolutely free.
Hello! Today is the first day I've ever used Linux. I finished installing Debian 6.0 GNU/Linux at 4:00 this morning. I have a friend who is quite good with Debian Linux (he's been using it for years), but he was unable to help me. Over four hours of searching-around on the internet, typing gibberish into the terminal, etc. has done nothing but frustrate me. Even more frustrating: it worked at 5:00 this morning, before I went to sleep. Does anyone have any advice for me on how to fix this crippling issue?
My NIC is integrated, having come with the computer, and is the RealTek Family Fast Ethernet.
My Ethernet-cord is plugged-in.
Nothing happens when I type "dhclient" or "sudo dhclient" into the terminal. :\
The ethernet-cable's plugged firmly into both the router and the back of the computer. As it was just working this morning, I probably don't need a new ethernet-cord (and I don't have any others that are anywhere near long enough to reach my computer, so we have to just assume that the ethernet-cord is in good shape).
I'm not sure what you mean by "Bounce". Do you mean type "192.168.1.1" into a browser, or do you mean to ping the router? If it's the latter, I don't know how on Linux.
Running the command cat /etc/network/interfaces in a terminal will allow you to see how your networking is currently configured by displaying the contents /etc/network/interfaces in the terminal.
Thanks. I believe you've just identified the source of the problem. There are obvious errors in the files specified in the guide you linked to, but my computer refuses to let me edit them; they're read-only. How do I change this?
Originally Posted by anomie
Power-cycle the router/NAT device. (I see you're on private IP space, so I am assuming you have one.) Afterward, either restart your networking service, or restart your workstation.
That's one of the first things I did.
Last edited by Sweyn78; 07-08-2011 at 01:20 AM.
Reason: To acknowledge and respond to the other bit of advice.
I've made the changes to the files in the guide, I've tried to follow the advice of the comments on the guide, and, still, it's just not working.
Things I've noticed:
Nothing but headers appear when I type "netstat -nr".
Resolv.config keeps rewriting itself
resolv.conf being re-written is quite normal; various things (dhcp, ppp, and probably network manager/wicd) do this when they are active. Usually, there is a comment included in resolv.conf about which service has written its settings there, so posting the file in its overwritten state may be helpful (if you can, please paste directly into your reply, using code tags to surround the pasted portion - it improves readability).
Can you ping your router? You'll have to know the ip address of your router It will almost inevitably be on a private/non-routable ip address; probably 192.168.0.0 or 192.168.0.1.
To try ping, type the following into a terminal
(which will try to ping for ever control-C to terminate...or
ping 192.168.0.1 -c 1
for a single ping; this will still stall, if the target is unavailable, but control-C will bring it to an end).
If you cannot ping the router, you'll find it difficult to make much progress. Any one of the things listed by anomie in post 4 are enough to stop you, but being unable to ping is pretty fundamental and low level, so start there.
Our Linksys' IP is 192.168.1.1. I know because I've done port-forwarding and other such things before from this OS and my XP (which I formatted yesterday for Debian).
Whenever it changes that file, it leaves only one line of code, and it's always the same nameserver, which is some combination of 10's and 1's.
I'm about to reboot into Debian to try to ping my router and to try OpenDSN to see if it'll work.
I'll be watching this thread from my Blackberry and I'll post what happens (if anything).