From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Furness Subject: Re: Ethernet Questions Date: 03 May 2002 17:45:27 +0100 Sender: linux-newbie-owner@vger.kernel.org Message-ID: <1020444328.5720.7.camel@Zebra> References: <2.2.32.20020502154917.010ab6fc@[192.168.1.23]> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2.2.32.20020502154917.010ab6fc@[192.168.1.23]> List-Id: Content-Type: text/plain; charset="us-ascii" To: Ray Olszewski Cc: linux-newbie I'd just add to all the info you have been given that you generally need to be root to run most of these commands - not because you need root privelages, but they are usually not in the defined command path for normal users. ifconfig is usually in /sbin or sometimes /usr/sbin, so if you are a regular user other than root and you type "ifconfig -a" at the prompt your system is likely to complain that ifconfig is a "command not found". If you do it as root, it should work fine. I only played with mandrake a couple of times, and that was over a year ago, but it definitely had ifconfig installed. If you are really missing this and possibly other essential system tools, it is possible that your install didn't work right or you accidentally told it not to install some stuff which you (at the time) didn't recognize as important. Worst comes to worst, it could possibly involve a rebuild of the system, selecting different install options, but hopefully you can avoid that for now! Paul. On Thu, 2002-05-02 at 16:49, Ray Olszewski wrote: > OK. Networking 101. Your system needs a valid IP address, a routing table > that includes a route to a working gateway to the Internet, and access to > DNS servers that can resolve names for you. (It may need other things too, > but this is the base.) To let us help you figure out what it wrong, report > the following (from your machine, AFTER it has received its DHCP lease): > > 1. The complete, exact output of "ifconfig -a" > 2. The complete, exact output of "netstat -nr" > 3. Try to ping the IP address reported in step 1. > Tell us either that the ping works or EXACTLY > how it fails ("-1" isn't enough; we need to see > the text that precedes the -1). > 4. Try to ping the gateway address reported in step 2 -- > the routing table (assuming there is one). > 5. The contents of the file /etc/resolv.conf . > 6. The results of pinging the first address listed in > /etc/resolv.conf . > > You may also have a hardware problem. I don't want to take the time to write > out those tests right now; if the results of this first set suggest a > hardware problem, I'll return to it. Oh, one more thing ... > > 7. The output of "uname -a" > > In responding, please don't paraphrase or summarize the results. From what > you have written,I'd say you don't know enough to decide what is and isn't > important in the output. Provide the details, though, and I (or someone else > here) can probably help you. > > At 10:22 AM 5/2/02 -0500, sadunn wrote: > >(I initially posted this to comp.os.linux.help, but none of the advice I > >received was that helpful. Regardles, I am going to post the replies I > >received, as well as my replies to them after this message) > > > >Hello. I am new to Linux, although I purchased Mandrake 7.0 quite a > >while ago. I recently began to desire to know how to operate Linux > >because I began to legitimately want to know about computers, as > >opposed to being a beginning programmer that liked to play around a > >little on them. However, I am unable to connect to the Internet on my > >terminal. I used to Lothar utility to detect my ethernet card, and I > >inputed all the values(Adapter Address, IP, Subnet mask, and Default > >Gateway) into the Network configuration available through DrakConfig. > >I got this data from the Winipcfg program in Win98. These were not > >enough. I went to the Linux ethernet HOW-TO, but none of the > >information there was on software setup, but it directed me to the > >networking HOW-TO. That, as well, failed to provide me with the > >information that I needed. So then I went to my university Information > >Technology Services(ITS) office, but they told me that they couldn't > >give me any technical support on Linux directly(they appear to have > >some sort of deal with Gateway, Macintosh, and Windows, but not > >Linux-oriented companies), but they did have a small webpage they > >directed me to. I went there, and it was a meager collection of links. > >Through these links I found this newsgroup. Please, I really want to > >get my ethernet running as soon as possible so I can update my kernel > >and OS and begin to learn how Linux really works. Whatever other > >information you need I will try my very best to provide. Thanks! > > > >Response one(by "John"): > > > >You also need your DNS servers' IP addresses, I didn't see that you > >mentioned this. Without them you can access remote servers only by > >number, not name. Without DNS, you cannot resolve anything and any > >attempts to connect to a web site will fail (unless you use the IP > >address, which is unlikely) > > > >Can you ping "localhost" or "127.0.0.1"? How about your "real" IP? For > >example (at a command prompt): > > > >ping localhost > >ping 127.0.0.1 > >ping 12.34.56.78 <--- your real IP here > > > >Response by "Alex" to response one: > > > >Try to see if your ISP (or wherever you get your Net feed from) uses > >DHCP. This means Dynamic Host Configuration Protocol, and if properly > >set up will automatically assign you your own IP adress and DNS server > >addresses. The software that does this undex Linux is either dhcpcd or > >pump (I think there are perhaps others I have seen). If you use this, > >you do not need to manually configure your internet connection. > > > >My two responses(One to each person that tried to help me): > > > >My net feed does use dynamic IP's. In my settings, I can select DHCP, > >which was unknown to me before this message. So, after reading this, I > >selected it. I'm not sure if it helped. It didn't do anything with my > >DNS that I can see, and my error message when I try to access a > >webpage still says that it is unable to resolve a name server. > > > >I can ping localhost and 127.0.0.1, but my "real" IP returned a -1 > >result. I am almost certain now, after some searching around, that it > >is my DNS that is to blame. The error message I get when I try to > >access a webpage tells me that it cannot resolve the name server, > >which seems to be in line with the DNS advice you gave me. I think > >that my IP is dynamic, not static, so I'm unable to ping the same one > >twice. Also, reading through some more help documentation, I've > >discovered that there is supposed to be a quick network setup wizard, > >but it isn't there. > > > >If anyone on this list can help me, I'd be very happy, indeed. Thanks! > > > > -- > ------------------------------------"Never tell me the odds!"--- > Ray Olszewski -- Han Solo > Palo Alto, CA ray@comarre.com > ---------------------------------------------------------------- > > - > To unsubscribe from this list: send the line "unsubscribe linux-newbie" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.linux-learn.org/faqs > - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs