This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Date: Sun, 09 May 2004 08:54:58 -0700
To: balug-talk@balug.org
From: Andrew Wheeler <awheeler@pacbell.net>
Subject: [Balug-talk] Newbie Networking problems
I am very new to linux. I bought an old Dell Optiplex on which to install
Linux. (Linux 8 had been installed on another machine but there was not
enough disk space to do anything.)
Fedora is on the Optiplex but I am not able to see my home network The book
I have is not detailed enough for me to begin to troubleshoot the problem.
I have looked at various boards and am frustrated.
My network consists of a Linksys router connected to a DSL modem. There are
three windows machines that are able to connect to the Web and to each
other. What I done on the Fedora machins is:
1. I can ping localhost successfully.
2. Someone suggested I confirm the network module was loaded by running
/sbin/lsmod and the output from that command was
Module Size Used by Not tainted
soundcore 6468 0 (autoclean)
ide-cd 35776 0 (autoclean)
cdrom 33728 0 (autoclean) [ide-cd
parport_pc 19076 1 (autoclean)
lp 9060 0 (autoclean)
parport 35076 1 (autoclean) [parport_pc lp]
autofs 13364 0 (autoclean) (unused)
3c59x 31280 1
floppy 58012 1 (autoclean)
sg 36492 0 (autoclean) (unused)
scsi_mod 108168 1 (autoclean) [sg]
microcode 4700 0 (autoclean)
keydev 2976 0 (unused)
hid 24708 0 (unused)
usb-uhci 26380 0 (unused)
usbcore 79168 1 [hid usb-uhci]
mousedev 5556 1 (autoclean)
input 5888 1 (autoclean) [keyboard hid mousedev]
ext3 71300 2
jbd 52084 2 [ext3
I have no idea what the output means.
According to the GUI "net configuration" tool the hardware tab displays
the nic card as 3c905 100BaseTx [Boomerang]
It was also suggested that I run ifconfig and the output from that follows.
eth0 Linkencap: Ethernet HWaddr: 00:CO:4F:785:E5
inetaddr:192.168.1.40 Bcast:192.168.1.255 Mask 255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:137 dropped:0 overruns:138 carrier:138
collisions:0 txqueuelen:1000
Rx bytes:32036 (31.2 kb) Tx bytes 0 (0.0 b)
interupt:11 base addressxdc80
lo Linkencap:local loopback
inetaddr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:1436 Metric:1
RX packets:3237 errors:0 dropped:0 overruns:0 frame:0
TX packets:3237 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Rx bytes:2538848 (2.4 Mb) Tx bytes:2538848 (2.4 Mb)
Suggestions and or help would be greatly appreciated.
===
Date: Sun, 09 May 2004 10:26:46 -0700
To: "sziisoft" <szii@sziisoft.com>, <balug-talk@balug.org>
From: Andrew Wheeler <awheeler@pacbell.net>
Subject: Re: [Balug-talk] Newbie Networking problems
sziisoft wrote:
>post your routing table via "route -n"
>
>Also, what are the addresses of your other machines?
The output from route -n is
Kernal IP routing table
Destination Gtewy GnMask flags metric ref use iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 eth0
192.254.0.0 0.0.0.0 255.255.0.0 U 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 eth0
The addresses of my other machines are
192.168.1.1 linksys router
192.168.1.100 XP Home edition
192.168.1.101 XP Professional
192.168.1.20 NT
===
Date: Sun, 9 May 2004 16:10:21 -0700
From: "Karsten M. Self" <kmself@ix.netcom.com>
To: balug-talk@balug.org
Subject: Re: [Balug-talk] Newbie Networking problems
Andrew Wheeler (awheeler@pacbell.net) wrote:
A few general tips:
- Don't post HTML to list. It's unfriendly for archives and a lot of
mailers. Your route and IP tables were also skewed for those of us
with monspace fonts (the One True Mail font). You can disable HTML
posts in Eudora.
- Post your response *after* the post you're quoting and trim quotes
(particularly sigs, headers, etc.).
- Mike would do well to get a patch to fix his MS OutHouse quoting
format.
> sziisoft wrote:
> > Andrew Wheeler wrote:
> > > My network consists of a Linksys router connected to a DSL modem.
> > > There are three windows machines that are able to connect to the
> > > Web and to each other. What I done on the Fedora machins is:
> > > 1. I can ping localhost successfully.
> > > 2. Someone suggested I confirm the network module was loaded by running
> > > /sbin/lsmod and the output from that command was
> > >
> > > Module Size Used by Not tainted
> > > soundcore 6468 0 (autoclean)
> > > ide-cd 35776 0 (autoclean)
> > > cdrom 33728 0 (autoclean) [ide-cd
> > > parport_pc 19076 1 (autoclean)
> > > lp 9060 0 (autoclean)
> > > parport 35076 1 (autoclean) [parport_pc lp]
> > > autofs 13364 0 (autoclean) (unused)
> > > 3c59x 31280 1
> > > floppy 58012 1 (autoclean)
> > > sg 36492 0 (autoclean) (unused)
> > > scsi_mod 108168 1 (autoclean) [sg]
> > > microcode 4700 0 (autoclean)
> > > keydev 2976 0 (unused)
> > > hid 24708 0 (unused)
> > > usb-uhci 26380 0 (unused)
> > > usbcore 79168 1 [hid usb-uhci]
> > > mousedev 5556 1 (autoclean)
> > > input 5888 1 (autoclean) [keyboard hid mousedev]
> > > ext3 71300 2
> > > jbd 52084 2 [ext3
> > > I have no idea what the output means.
That's a list of modules loaded (first column), space used, and other
modules referencing same.
What you're looking for specifically is a module for your NIC card(s)
being loaded. 'grep -i eth /var/log/dmesg' will provide similar
information in somewhat greater detail. 'lspci | grep -i eth' will show
what NICs are on your PCI bus.
> > > According to the GUI "net configuration" tool the hardware tab
> > > displays the nic card as 3c905 100BaseTx [Boomerang]
Loaded as 3c59x, above. That's not your problem.
> > > It was also suggested that I run ifconfig and the output from that
> > > follows.
> > > eth0 Linkencap: Ethernet HWaddr: 00:CO:4F:785:E5
> > > inetaddr:192.168.1.40 Bcast:192.168.1.255 Mask 255.255.255.0
You've got eth0 configured at address 192.168.1.40, on the 192.168.0/24
network. This corresponds appropriately to your other hosts' addresses
given later.
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:0 errors:137 dropped:0 overruns:138 carrier:138 collisions:0 txqueuelen:1000
That's a high error rate. I'd say you've got a NIC configuration or HW
problem, possibly.
> The output from route -n is
> Kernal IP routing table
> Destination Gtewy GnMask flags metric ref use iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 eth0
> 192.254.0.0 0.0.0.0 255.255.0.0 U 0 0 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 eth0
That looks _mostly_ good, though there's one probable problem:
Why do you have a 192.254/16 network configured on eth0 *in addition* to
the 192.168.1.0/24 net?
If you do want to IP alias, you should specify eth0, eth0:0, eth0:1,
etc., for the various aliases.
This could well be the source of your errors.
Find out where that route is coming from, and remove/comment it, then
try again.
> The addresses of my other machines are
> 192.168.1.1 linksys router
> 192.168.1.100 XP Home edition
> 192.168.1.101 XP Professional
> 192.168.1.20 NT
Looks good.
===
Date: Sun, 09 May 2004 17:55:08 -0700
To: "Karsten M. Self" <kmself@ix.netcom.com>, balug-talk@balug.org
From: Andrew Wheeler <awheeler@pacbell.net>
Subject: Re: [Balug-talk] Newbie Networking problems
Cc:
At 04:10 PM 5/9/04 -0700, Karsten M. Self wrote:
>on Sun, May 09, 2004 at 10:26:46AM -0700, Andrew Wheeler
>(awheeler@pacbell.net) wrote:
>
>A few general tips:
>
> - Don't post HTML to list. It's unfriendly for archives and a lot of
> mailers. Your route and IP tables were also skewed for those of us
> with monspace fonts (the One True Mail font). You can disable HTML
> posts in Eudora.
I believe I have turned HTML formating off.
> - Post your response *after* the post you're quoting and trim quotes
> (particularly sigs, headers, etc.).
Like this? Not sure what you meant by sigs and headers.
> - Mike would do well to get a patch to fix his MS OutHouse quoting
> format.
>
> > sziisoft wrote:
> > > Andrew Wheeler wrote:
> > > > My network consists of a Linksys router connected to a DSL modem.
> > > > There are three windows machines that are able to connect to the
> > > > Web and to each other. What I done on the Fedora machins is:
> > > >
> > > > 1. I can ping localhost successfully.
> > > > 2. Someone suggested I confirm the network module was loaded by running
> > > > /sbin/lsmod and the output from that command was
> > > > I have no idea what the output means.
>That's a list of modules loaded (first column), space used, and other
>modules referencing same.
>
>What you're looking for specifically is a module for your NIC card(s)
>being loaded. 'grep -i eth /var/log/dmesg' will provide similar
>information in somewhat greater detail. 'lspci | grep -i eth' will show
>what NICs are on your PCI bus.
Thanks that is helpful. Will try the other commands.
> > > > According to the GUI "net configuration" tool the hardware tab
> > > > displays the nic card as 3c905 100BaseTx [Boomerang]
>
>Loaded as 3c59x, above. That's not your problem.
>
> > > > It was also suggested that I run ifconfig and the output from that
> > > > follows.
> > > >
> > > > eth0 Linkencap: Ethernet HWaddr: 00:CO:4F:785:E5
> > > > inetaddr:192.168.1.40 Bcast:192.168.1.255 Mask 255.255.255.0
>
>You've got eth0 configured at address 192.168.1.40, on the 192.168.0/24
>network. This corresponds appropriately to your other hosts' addresses
>given later.
I don't understand the "on the 192.168.0/24 network." What is the 0/24
referring to?
> > The output from route -n is
> >
> > Kernal IP routing table
> >
> > Destination Gtewy GnMask flags metric ref use iface
> >
> > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 eth0
> > 192.254.0.0 0.0.0.0 255.255.0.0 U 0 0 eth0
> > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo
> > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 eth0
>
>That looks _mostly_ good, though there's one probable problem:
>
>Why do you have a 192.254/16 network configured on eth0 *in addition* to
>the 192.168.1.0/24 net?
>
>If you do want to IP alias, you should specify eth0, eth0:0, eth0:1,
>etc., for the various aliases.
>
>This could well be the source of your errors.
>
>Find out where that route is coming from, and remove/comment it, then
>try again.
You say "why do you have a 192.254/16 network configured on eth0 to the
192.168.1.0/24 net.
I don't know why I would want an alias and didn't set one up to my
knowledge (although I must have inadvertently)
How do I find out where the route is coming from and how do I remove it?
===
Date: Sun, 9 May 2004 19:15:32 -0700
From: "Karsten M. Self" <kmself@ix.netcom.com>
To: balug-talk@balug.org
Subject: Re: [Balug-talk] Newbie Networking problems
Andrew Wheeler (awheeler@pacbell.net) wrote:
> Karsten M. Self wrote:
> >Andrew Wheeler (awheeler@pacbell.net) wrote:
> I believe I have turned HTML formating off.
Much better, thanks.
> > - Post your response *after* the post you're quoting and trim quotes
> > (particularly sigs, headers, etc.).
> Like this? Not sure what you meant by sigs and headers.
Yes. Again, thanks.
Note that I'll gripe about your CCing me on list posts. I filter mail
based on list-inserted headers -- where I _got_ the mail from, rather
than where it was _sent_ to -- *and* drop dupe mails based on
Message-ID. As do a lot of folks.
So your CC usually beats the list mail to my inbox, ends up as personal
mail, and the list post is dumped as a duplicate delivery. Which makes
me grumpy. But not quite so much as Mr. Moffitt.
> >> At 10:02 AM 5/9/04 -0700, sziisoft wrote:
> >> > On: Sunday, May 09, 2004 <mailto:awheeler@pacbell.net>Andrew Wheeler=
=20
> >wrote:
> >
> >> > > My network consists of a Linksys router connected to a DSL modem.
> >> > > There are three windows machines that are able to connect to the
> >> > > Web and to each other. What I done on the Fedora machins is:
> >> > >
> >> > > 1. I can ping localhost successfully.
> >> > > 2. Someone suggested I confirm the network module was loaded by=20
> >running
> >> > > /sbin/lsmod and the output from that command was
> >> > >
> >> > > Module Size Used by Not tainted
> >> > > soundcore 6468 0 (autoclean)
> >> > > ide-cd 35776 0 (autoclean)
> >> > > cdrom 33728 0 (autoclean) [ide-cd
<...>
> >> > > It was also suggested that I run ifconfig and the output from that
> >> > > follows.
> >> > >
> >> > > eth0 Linkencap: Ethernet HWaddr: 00:CO:4F:785:E5
> >> > > inetaddr:192.168.1.40 Bcast:192.168.1.255 Mask 255.255.255.0
> >
> >You've got eth0 configured at address 192.168.1.40, on the 192.168.0/24
> >network. This corresponds appropriately to your other hosts' addresses
> >given later.
> I don't understand the "on the 192.168.0/24 network." What is the 0/24 referring to?
CIDR: classless Internet domain routing.
The first bit is the network specification: where the network starts.
The "/#" bit indicates the size of the network mask. A larger netmask
means a smaller defined network. /32 =3D 1 host. /24 =3D 254 hosts (plus
network and broadcast addresses =3D=3D 256 addresses). A 16 is 65,534
addresses (plus network/b'cast), an 8 is 16,777,214 addresses (plus
network/b'cast).
The /netmask can also be specified in dotted quad format:
/24 =3D /255.255.255.0
/16 =3D /255.255.0.0
/8 =3D /255.0.0.0
I'd recommend reading the Linux Networking HOWTOs for a general
background on these concepts.
http://www.tldp.org/HOWTO/Networking-Overview-HOWTO.html
http://www.tldp.org/HOWTO/Net-HOWTO/index.html
http://www.tldp.org/HOWTO/IP-Subnetworking.html
> >> The output from route -n is
> >>
> >> Kernal IP routing table
> >>
> >> Destination Gtewy GnMask flags metric ref use iface
> >>
> >> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 eth0
> >> 192.254.0.0 0.0.0.0 255.255.0.0 U 0 0 eth0
> >> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 lo
> >> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 eth0
> >
> >That looks _mostly_ good, though there's one probable problem:
> >
> >Why do you have a 192.254/16 network configured on eth0 *in addition* to
> >the 192.168.1.0/24 net?
> >If you do want to IP alias, you should specify eth0, eth0:0, eth0:1,
> >etc., for the various aliases.
> >
> >This could well be the source of your errors.
> >
> >Find out where that route is coming from, and remove/comment it, then
> >try again.
> You say "why do you have a 192.254/16 network configured on eth0 to the
> 192.168.1.0/24 net.
These two lines:
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 eth0
192.254.0.0 0.0.0.0 255.255.0.0 U 0 0 eth0
..indicate that device "eth0" has two routes defined on it.
One is 192.168.1.0/255.255.255.0 (aka 192.168.1.0/24). This is what you
want.
One is 192.254.0.0/255.255.255.0 (aka 192.254.0.0/16). This probably
shouldn't be there.
> I don't know why I would want an alias and didn't set one up to my=20
> knowledge (although I must have inadvertently)
Aliases can be useful. You can set up a single NIC with a primary IP
and a secondary role-based IP. You can then transfer this role to a
different box simply by disabling the *alias* on the first box and
enabling it on another (or you can use failover tools to do this
automatically). This increases flexibility (and complexity ;-) on a
network.
> How do I find out where the route is coming from and how do I remove it?
In reverse order:
route del 192.254.0.0
...should, I think, get rid of it.
You can see if it shows up again on reboot (or restarting of network
configuration).
Hunting it down is more interesting. I'd start with:
find /etc -type f -print0 | xargs -0 grep -l '192\.254\.0\.0'
...which may run for a while. I'd try a network restart first just to
be sure I didn't fumble-finger the route from the command line.
Otherwise, you'll want to walk through your startup scripts
individually, run these, and see which sets that route. And if *that*
doesn't turn up the culprit, dig further.
Startup scripts should live in:
Most modern distros: /etc/rcS.d/
Older RH/RPM distros: /etc/rc.d/rcS.d/
I think Fedora falls under the first class.
===
Date: Sun, 9 May 2004 21:47:19 -0700
To: balug-talk@balug.org
Subject: Re: [Balug-talk] Newbie Networking problems
From: Rick Moen <rick@linuxmafia.com>
[Further comments to assist Andrew.]
Quoting Karsten Self (kmself@ix.netcom.com):
> - Don't post HTML to list. It's unfriendly for archives and a lot of
> mailers. Your route and IP tables were also skewed for those of us
> with monspace fonts (the One True Mail font). You can disable HTML
> posts in Eudora.
Here's how:
http://expita.com/nomime.html#eudora5
> - Post your response *after* the post you're quoting and trim quotes
> (particularly sigs, headers, etc.).
For Andrew's benefit: By "sigs", Karsten means the "signature blocks"
at the bottom of people's messages -- the blocks of text following the
main message body, in which people put witty sayings, contact
information, etc. When you respond to people's messages, there is NO
reason to quote their signature blocks except in the very, very rare
case of your having reason to comment on the content of those blocks.
Andrew, you still need to fix that. Quote _only_ the text you're
specifically responding to. Eliminate (trim, snip) everything else
from quoted text.
> - Mike would do well to get a patch to fix his MS OutHouse quoting
> format.
There is an add-on utility for MS-Outlook, and a matching one for
MS-Outlook Express, to take care of that detail automatically. See:
"MS-Outlook Quoting" on http://linuxmafia.com/kb/Legacy_Microsoft
===
Date: Tue, 11 May 2004 12:10:55 -0700
To: balug-talk@balug.org
From: Andrew Wheeler <awheeler@pacbell.net>
Subject: Re: [Balug-talk] Newbie Networking problems
Karsten M. Self wrote:
> Andrew Wheeler wrote:
> > Karsten M. Self wrote:
> > >Andrew Wheeler wrote:
>So your CC usually beats the list mail to my inbox, ends up as personal
>mail, and the list post is dumped as a duplicate delivery. Which makes
>me grumpy. But not quite so much as Mr. Moffitt.
OK this is just being sent to the List.
> > >> sziisoft wrote:
> > >> > Andrew Wheeler wrote:
> > I don't understand the "on the 192.168.0/24 network." What is the 0/24
> > referring to?
>
>CIDR: classless Internet domain routing.
>
>The first bit is the network specification: where the network starts.
>The "/#" bit indicates the size of the network mask. A larger netmask
>means a smaller defined network. /32 = 1 host. /24 = 254 hosts (plus
>network and broadcast addresses == 256 addresses). A 16 is 65,534
>addresses (plus network/b'cast), an 8 is 16,777,214 addresses (plus
>network/b'cast).
>
>The /netmask can also be specified in dotted quad format:
>
> /24 = /255.255.255.0
> /16 = /255.255.0.0
> /8 = /255.0.0.0
Thanks this was an excellent explanation.
>I'd recommend reading the Linux Networking HOWTOs for a general
>background on these concepts.
>
> http://www.tldp.org/HOWTO/Networking-Overview-HOWTO.html
> http://www.tldp.org/HOWTO/Net-HOWTO/index.html
> http://www.tldp.org/HOWTO/IP-Subnetworking.html
I have started to read this. I have read quite a bit about TCP/IP but since
I don't work with the concepts much they get lost in the morass of details
in my brain.
> > How do I find out where the route is coming from and how do I remove it?
>
>In reverse order:
>
> route del 192.254.0.0
>
>...should, I think, get rid of it.
>
>You can see if it shows up again on reboot (or restarting of network
>configuration).
I was able to remove 192.254.0.0 but still not able to ping linksys router
or anything else but localhost.
I have continued to pursue this problem via Google and various bulletin
boards and see many posts and no answers similar problems with the 3Com