RE: Ethernet Questions

RE: Ethernet Questions

[sadunn]

I would like to thank you for helping me get my ethernet configured! I finally 
got everything to work correctly, and I'm currently writing to this list from 
my Linux partition. I know I had no idea what I was doing, and I'm sorry if I 
was too annoying, but once again I'd just like to thank you for helping.


-
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

RE: Ethernet Questions

[Ray Olszewski]

At 01:58 PM 5/4/02 -0500, sadunn wrote:
[...]
>I got some interesting information from doing this. dmesg gave me only one 
>mention of eth0, which went:
>
>eth0: Digital DC21040 Tulip rev 35 at 0x1080, 00:00:C0:1C:0D:C7, IRQ 9
>
>I assume this meant the interface was up, since this is just the information I 
>received from ifconfig -a. However, when I checked var/log, I found this, 
>repeated in three different places, all during an attempt to startup something 
>called inet:
>
>localhost: can't find a dhcpcd client, sbin/pump or sbin/dhcpcd
>localhost network: bringing up device eth0 failed
>
>I then went to /sbin, and there was nothing about pump or dhcpcd there. I 
>searched around, and can't find them anywhere. I looked to see if during my 
>install I didn't install the package(s) they were contained within, but I 
>didn't find anything about them there, either.
[...]

OK. First thing to clarify is terminology. The first eth0 line you found
confirms that the interface *exists*. For it to be "up", though, it needs an
IP address assigned to it. 

Your system is trying to assign an IP address via DHCP -- that's what the
log lines you woute report -- but it can't find a DHCP application to run to
do the work. Apparently you didn't install them when you set up the system.

At this point, someone familiar with the RPM packages can easily help you,
but people like me (people who use non-RPM-based distros like Debian) are
out of the picture. Anyone familiar whth Mandrake should be able to tell you
which *.rpm package(s) you need to load to fix this.



--
------------------------------------"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

RE: Ethernet Questions

[sadunn]

>===== Original Message From Ray Olszewski <ray@comarre.com> =====
>I added the list back in to this exchange, and I left your message to me
>intact below for that reason.

Thank you. I didn't realize until after I had sent the message that I had 
selected to only reply to you, and not to you plus the list.

>The results of "ifconfig -a" indicate that the interface exists but is not
>configured (that is, does not have an IP address). Assuming you are right in
>your guess that your system uses DHCP (that is certainly something we can't
>tell you), then you need to run some DHCP client on the Mandrake system.
>
>In my prior message, I listed the three common ones (see my item #3 from
>before); you need to check if any of them is on your system and if the
>system is set to use it. See if there is an entry for eth0 in
>/etc/network/interfaces that specifies use of DHCP. (I'm not actually sure
>that Mandrake uses this file, but it is the common way these days to set up
>interfaces, so it probably does.)

I don't have a network folder in /etc.

>If DHCP is running and failing for some reason, there should be output from
>it, either in the dmesg ring buffer (access this with the command "dmesg")
>or in your log files (usually in /var/log, though logging details vary a lot
>between distros).

I got some interesting information from doing this. dmesg gave me only one 
mention of eth0, which went:

eth0: Digital DC21040 Tulip rev 35 at 0x1080, 00:00:C0:1C:0D:C7, IRQ 9

I assume this meant the interface was up, since this is just the information I 
received from ifconfig -a. However, when I checked var/log, I found this, 
repeated in three different places, all during an attempt to startup something 
called inet:

localhost: can't find a dhcpcd client, sbin/pump or sbin/dhcpcd
localhost network: bringing up device eth0 failed

I then went to /sbin, and there was nothing about pump or dhcpcd there. I 
searched around, and can't find them anywhere. I looked to see if during my 
install I didn't install the package(s) they were contained within, but I 
didn't find anything about them there, either.

>Once you have a lease, everything else will probably work.

I hope so! If this ever works I think I should become your vassal or the like 
in gratitude!

>At 11:32 PM 5/3/02 -0500, sadunn wrote:
>>>===== Original Message From Ray Olszewski <ray@comarre.com> =====
>>>You are correct; it does not seem to have received a DHCP lease. I was
>>>misled by your comments in your prior message that "but my "real" IP
>>>returned a -1 result". In context, I understood this to mean that you'd
>>>received a DHCP lease; otherwise, what did your reference to "my "real" IP"
>>>mean?
>>
>>Before I begin, I just want to state that I got so frustrated that I
>>reinstalled Mandrake on my system before I began what was asked of me in 
these
>>prior e-mails. Anyways...
>>
>>By my "real" IP, I was referencing the IP that I received from the winipcfg
>>tool available in Win98. It gave me an IP, host name, 3 DNS addresses, a 
node
>>type, and a DHCP server. I assumed that they would carry over to Linux, but 
I
>>pinged the DNS addresses, and got nothing.
>>
>>>New comments:
>>>
>>>1. It is unlikely that your system lacks the command "ifconfig". Were you
>>>root when you ran the command? If not, please try again as root. (Even
>>>though you are clearly not getting an IP address, this test (by using the 
-a
>>>flag) will tell us if the interface itself exists. If not, you have a
>>>problem at some earlier level we have not yet addressed.
>>
>>I ran the command from root, and it returned eth0 and lo. The eth0 said 
this:
>>Link encap: Ethernet
>>HWaddr 00:00:C0:0D:C7
>>Broadcast Multicast
>>MTN: 1500
>>Metric: 1
>>Rx packets: 0 errors: 0 dropped: 0 overruns: 0 frame: 0
>>Tx packets: 0 errors: 0 dropped: 0 overruns: 0 carrier: 0
>>collisions: 0 txqueuelen: 0
>>Interrupt: 9
>>base address: 0x1080
>>
>>>If you were root, and ifconfig is *really* not on your system, then you 
need
>>>to find out what low-level tool Mandrake provides for accessing interfaces.
>>>The only other one I can think of is "ip", and I believe it does not have a
>>>command to display information about unconfigured interfaces.
>>>
>>>2. Since you are not getting an IP address via DHCP, we need to consider
>>>whether you have a working Ethernet interface at all. If (proprely run)
>>>"ifconfig -a" does NOT show an eth0 device, then please tell us what
>>>Ethernet card you are using, what kernel module(s) you are running to 
access
>>>it, and what the kernel reports during boot/init about it. This last part
>>>will be in the kernel's boot messages, visible via the command "dmesg" and
>>>possibly in a logfile somewhere (try grep'ing for it in /var/log).
>>>
>>>3. If you DO have an eth0 interface, then we need to wonder why it is not
>>>being configured during boot/init. Are you sure your setup uses DHCP (how 
do
>>>you know)? What does the Linux DHCP client -- I don't know which one
>>>Mandrake uses, but the common ones are pump, dhcpcd, and dhclient -- report
>>>during the boot/init sequence (look in the logs)?
>>
>>I'm not sure if my setup uses DHCP, but my windows system used it, and I was
>>unaware what to do in Linux.
>>
>>>I should clarify one thing: while Linux is at its core a unified OS across
>>>all its distributions, these days distros try to differentiate themselves 
at
>>>the User Interface level. As a Debian user, I'm not familiar with the UI
>>>utilities Lothar and DrakConfig, the ones you mention using to set up your
>>>interface. Also, the unspecified "quick network setup wizard" you learned
>>>about in unnamed documentation may not be there because it is specific to
>>>some other distro. Here, I am staying with the low-level setup tools that I
>>>believe still to be standard across all full-size Linux distros.
>>>
>>>
>>>At 12:05 PM 5/2/02 -0500, sadunn wrote:
>>>>===== Original Message From Ray Olszewski <ray@comarre.com> =====
>>>>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):
>>>
>>>I don't think it has received its DHCP lease, since the netstat -nr command
>>>returned a destination to 127.0.0.0, and none of the other data seems to
>>make
>>>any sense whatsoever.
>>>
>>>>
>>>>        1. The complete, exact output of "ifconfig -a"
>>>
>>>bash: ifconfig: command not found
>>>
>>>>        2. The complete, exact output of  "netstat -nr"
>>>
>>>Kernel IP routing table
>>>Destination  Gateway   Genmask    Flags   Mss  Window   irtt   Iface
>>>127.0.0.0    0.0.0.0   255.0.0.0    u      0    0         0      lo
>>>
>>>>        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).
>>>
>>>I didn't get an address to ping because the command failed.
>>>
>>>>        4. Try to ping the gateway address reported in step 2 --
>>>>                the routing table (assuming there is one).
>>>
>>>I didn't think 0.0.0.0 was a vaild address to ping, so I didn't. Perhaps I
>>am
>>>mistaken?
>>>
>>>>        5. The contents of the file /etc/resolv.conf .
>>>
>>>search localdomain
>>>
>>>>        6. The results of pinging the first address listed in
>>>>                /etc/resolv.conf .
>>>
>>>I had no address to ping
>>>
>>>>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"
>>>
>>>Linux localhost 2.2.14-15mdk #1 Tue Jan 4 22:24:20 CET 2000 i686 unknown
>>>
>>>[old stuff deleted]
>>>
>>>
>>>--
>>>------------------------------------"Never tell me the odds!"---
>>>Ray Olszewski                                        -- Han Solo
>>>Palo Alto, CA           	 	         ray@comarre.com
>>>----------------------------------------------------------------
>>
>>
>>
>
>--
>------------------------------------"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

RE: Ethernet Questions

[Ray Olszewski]

I added the list back in to this exchange, and I left your message to me
intact below for that reason.

The results of "ifconfig -a" indicate that the interface exists but is not
configured (that is, does not have an IP address). Assuming you are right in
your guess that your system uses DHCP (that is certainly something we can't
tell you), then you need to run some DHCP client on the Mandrake system. 

In my prior message, I listed the three common ones (see my item #3 from
before); you need to check if any of them is on your system and if the
system is set to use it. See if there is an entry for eth0 in
/etc/network/interfaces that specifies use of DHCP. (I'm not actually sure
that Mandrake uses this file, but it is the common way these days to set up
interfaces, so it probably does.)

If DHCP is running and failing for some reason, there should be output from
it, either in the dmesg ring buffer (access this with the command "dmesg")
or in your log files (usually in /var/log, though logging details vary a lot
between distros).

Once you have a lease, everything else will probably work. 

At 11:32 PM 5/3/02 -0500, sadunn wrote:
>>===== Original Message From Ray Olszewski <ray@comarre.com> =====
>>You are correct; it does not seem to have received a DHCP lease. I was
>>misled by your comments in your prior message that "but my "real" IP
>>returned a -1 result". In context, I understood this to mean that you'd
>>received a DHCP lease; otherwise, what did your reference to "my "real" IP"
>>mean?
>
>Before I begin, I just want to state that I got so frustrated that I 
>reinstalled Mandrake on my system before I began what was asked of me in these 
>prior e-mails. Anyways...
>
>By my "real" IP, I was referencing the IP that I received from the winipcfg 
>tool available in Win98. It gave me an IP, host name, 3 DNS addresses, a node 
>type, and a DHCP server. I assumed that they would carry over to Linux, but I 
>pinged the DNS addresses, and got nothing.
>
>>New comments:
>>
>>1. It is unlikely that your system lacks the command "ifconfig". Were you
>>root when you ran the command? If not, please try again as root. (Even
>>though you are clearly not getting an IP address, this test (by using the -a
>>flag) will tell us if the interface itself exists. If not, you have a
>>problem at some earlier level we have not yet addressed.
>
>I ran the command from root, and it returned eth0 and lo. The eth0 said this:
>Link encap: Ethernet
>HWaddr 00:00:C0:0D:C7
>Broadcast Multicast
>MTN: 1500
>Metric: 1
>Rx packets: 0 errors: 0 dropped: 0 overruns: 0 frame: 0
>Tx packets: 0 errors: 0 dropped: 0 overruns: 0 carrier: 0
>collisions: 0 txqueuelen: 0
>Interrupt: 9
>base address: 0x1080
>
>>If you were root, and ifconfig is *really* not on your system, then you need
>>to find out what low-level tool Mandrake provides for accessing interfaces.
>>The only other one I can think of is "ip", and I believe it does not have a
>>command to display information about unconfigured interfaces.
>>
>>2. Since you are not getting an IP address via DHCP, we need to consider
>>whether you have a working Ethernet interface at all. If (proprely run)
>>"ifconfig -a" does NOT show an eth0 device, then please tell us what
>>Ethernet card you are using, what kernel module(s) you are running to access
>>it, and what the kernel reports during boot/init about it. This last part
>>will be in the kernel's boot messages, visible via the command "dmesg" and
>>possibly in a logfile somewhere (try grep'ing for it in /var/log).
>>
>>3. If you DO have an eth0 interface, then we need to wonder why it is not
>>being configured during boot/init. Are you sure your setup uses DHCP (how do
>>you know)? What does the Linux DHCP client -- I don't know which one
>>Mandrake uses, but the common ones are pump, dhcpcd, and dhclient -- report
>>during the boot/init sequence (look in the logs)?
>
>I'm not sure if my setup uses DHCP, but my windows system used it, and I was 
>unaware what to do in Linux.
>
>>I should clarify one thing: while Linux is at its core a unified OS across
>>all its distributions, these days distros try to differentiate themselves at
>>the User Interface level. As a Debian user, I'm not familiar with the UI
>>utilities Lothar and DrakConfig, the ones you mention using to set up your
>>interface. Also, the unspecified "quick network setup wizard" you learned
>>about in unnamed documentation may not be there because it is specific to
>>some other distro. Here, I am staying with the low-level setup tools that I
>>believe still to be standard across all full-size Linux distros.
>>
>>
>>At 12:05 PM 5/2/02 -0500, sadunn wrote:
>>>>===== Original Message From Ray Olszewski <ray@comarre.com> =====
>>>>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):
>>>
>>>I don't think it has received its DHCP lease, since the netstat -nr command
>>>returned a destination to 127.0.0.0, and none of the other data seems to 
>make
>>>any sense whatsoever.
>>>
>>>>
>>>>        1. The complete, exact output of "ifconfig -a"
>>>
>>>bash: ifconfig: command not found
>>>
>>>>        2. The complete, exact output of  "netstat -nr"
>>>
>>>Kernel IP routing table
>>>Destination  Gateway   Genmask    Flags   Mss  Window   irtt   Iface
>>>127.0.0.0    0.0.0.0   255.0.0.0    u      0    0         0      lo
>>>
>>>>        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).
>>>
>>>I didn't get an address to ping because the command failed.
>>>
>>>>        4. Try to ping the gateway address reported in step 2 --
>>>>                the routing table (assuming there is one).
>>>
>>>I didn't think 0.0.0.0 was a vaild address to ping, so I didn't. Perhaps I 
>am
>>>mistaken?
>>>
>>>>        5. The contents of the file /etc/resolv.conf .
>>>
>>>search localdomain
>>>
>>>>        6. The results of pinging the first address listed in
>>>>                /etc/resolv.conf .
>>>
>>>I had no address to ping
>>>
>>>>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"
>>>
>>>Linux localhost 2.2.14-15mdk #1 Tue Jan 4 22:24:20 CET 2000 i686 unknown
>>
>>[old stuff deleted]
>>
>>
>>--
>>------------------------------------"Never tell me the odds!"---
>>Ray Olszewski                                        -- Han Solo
>>Palo Alto, CA           	 	         ray@comarre.com
>>----------------------------------------------------------------
>
>
>

--
------------------------------------"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

RE: Ethernet Questions

[Ray Olszewski]

You are correct; it does not seem to have received a DHCP lease. I was
misled by your comments in your prior message that "but my "real" IP
returned a -1 result". In context, I understood this to mean that you'd
received a DHCP lease; otherwise, what did your reference to "my "real" IP"
mean?

New comments:

1. It is unlikely that your system lacks the command "ifconfig". Were you
root when you ran the command? If not, please try again as root. (Even
though you are clearly not getting an IP address, this test (by using the -a
flag) will tell us if the interface itself exists. If not, you have a
problem at some earlier level we have not yet addressed. 

If you were root, and ifconfig is *really* not on your system, then you need
to find out what low-level tool Mandrake provides for accessing interfaces.
The only other one I can think of is "ip", and I believe it does not have a
command to display information about unconfigured interfaces. 

2. Since you are not getting an IP address via DHCP, we need to consider
whether you have a working Ethernet interface at all. If (proprely run)
"ifconfig -a" does NOT show an eth0 device, then please tell us what
Ethernet card you are using, what kernel module(s) you are running to access
it, and what the kernel reports during boot/init about it. This last part
will be in the kernel's boot messages, visible via the command "dmesg" and
possibly in a logfile somewhere (try grep'ing for it in /var/log).

3. If you DO have an eth0 interface, then we need to wonder why it is not
being configured during boot/init. Are you sure your setup uses DHCP (how do
you know)? What does the Linux DHCP client -- I don't know which one
Mandrake uses, but the common ones are pump, dhcpcd, and dhclient -- report
during the boot/init sequence (look in the logs)?

I should clarify one thing: while Linux is at its core a unified OS across
all its distributions, these days distros try to differentiate themselves at
the User Interface level. As a Debian user, I'm not familiar with the UI
utilities Lothar and DrakConfig, the ones you mention using to set up your
interface. Also, the unspecified "quick network setup wizard" you learned
about in unnamed documentation may not be there because it is specific to
some other distro. Here, I am staying with the low-level setup tools that I
believe still to be standard across all full-size Linux distros.


At 12:05 PM 5/2/02 -0500, sadunn wrote:
>>===== Original Message From Ray Olszewski <ray@comarre.com> =====
>>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):
>
>I don't think it has received its DHCP lease, since the netstat -nr command 
>returned a destination to 127.0.0.0, and none of the other data seems to make 
>any sense whatsoever.
>
>>
>>        1. The complete, exact output of "ifconfig -a"
>
>bash: ifconfig: command not found
>
>>        2. The complete, exact output of  "netstat -nr"
>
>Kernel IP routing table
>Destination  Gateway   Genmask    Flags   Mss  Window   irtt   Iface
>127.0.0.0    0.0.0.0   255.0.0.0    u      0    0         0      lo
>
>>        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).
>
>I didn't get an address to ping because the command failed.
>
>>        4. Try to ping the gateway address reported in step 2 --
>>                the routing table (assuming there is one).
>
>I didn't think 0.0.0.0 was a vaild address to ping, so I didn't. Perhaps I am 
>mistaken?
>
>>        5. The contents of the file /etc/resolv.conf .
>
>search localdomain
>
>>        6. The results of pinging the first address listed in
>>                /etc/resolv.conf .
>
>I had no address to ping
>
>>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"
>
>Linux localhost 2.2.14-15mdk #1 Tue Jan 4 22:24:20 CET 2000 i686 unknown

[old stuff deleted]


--
------------------------------------"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

RE: Ethernet Questions

[sadunn]

>===== Original Message From Ray Olszewski <ray@comarre.com> =====
>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):

I don't think it has received its DHCP lease, since the netstat -nr command 
returned a destination to 127.0.0.0, and none of the other data seems to make 
any sense whatsoever.

>
>        1. The complete, exact output of "ifconfig -a"

bash: ifconfig: command not found

>        2. The complete, exact output of  "netstat -nr"

Kernel IP routing table
Destination  Gateway   Genmask    Flags   Mss  Window   irtt   Iface
127.0.0.0    0.0.0.0   255.0.0.0    u      0    0         0      lo

>        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).

I didn't get an address to ping because the command failed.

>        4. Try to ping the gateway address reported in step 2 --
>                the routing table (assuming there is one).

I didn't think 0.0.0.0 was a vaild address to ping, so I didn't. Perhaps I am 
mistaken?

>        5. The contents of the file /etc/resolv.conf .

search localdomain

>        6. The results of pinging the first address listed in
>                /etc/resolv.conf .

I had no address to ping

>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"

Linux localhost 2.2.14-15mdk #1 Tue Jan 4 22:24:20 CET 2000 i686 unknown

>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

Re: Ethernet Questions

[Ray Olszewski]

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

Re: Ethernet Questions

[Paul Furness]

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

Ethernet Questions

[sadunn]

(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!


-
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