Linux-Networking Digest #831, Volume #9 Sat, 9 Jan 99 18:13:44 EST
Contents:
LAN at home (campin)
Re: Need help with diagnosing a network problem (Joerg Ammon)
Re: Netscape 4.5=DUD !? (Yaye)
Re: Need help with diagnosing a network problem (Joerg Ammon)
Re: Need help with diagnosing a network problem (Joerg Ammon)
Re: Need help with diagnosing a network problem (Joerg Ammon)
Re: Need help with diagnosing a network problem (Joerg Ammon)
use CDE remotely ("Raymond")
Trouble with networ-card ne2000 PCI (Yves Schlegel)
----------------------------------------------------------------------------
From: campin <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.questions
Subject: LAN at home
Date: Sat, 09 Jan 1999 15:02:11 GMT
Sorry people,
I havw two boxes at home, the Pentium is named "bipolar" and the i486 is
"skitzo." PPP has not been enabled at any point during the
diagnostics/lan installation.
I have a dual boot Micronics/EDS Pentium 90 with 16 megs RAM, a 4 gig
hard drive. I was just given an i486 DX4
100mz without a hard drive or CDROM and 24megs of RAM on the board.
What's the first thing a Linux junkie thinks
of when he/she is given another box? LAN AT HOME!
I got my hands on two unused NICS, same make and model, (SMC EtherEZ,
ISA) from work that have the 10base2
coax connectors and bought the thinnet cable, T connectors and
terminators at Comp USA. I plugged in an extra HDD
with Red Hat 5.1 already installed, plugged in the NIC and booted her
up. The new HDD already had a SMC NIC driver
compiled into the kernel, so it saw the NIC at boot-up.
I didn't change the IP address for the 486 from 199.208.118.159 since
it's what I already configured on the LAN at
work, and I just wanted to test my new network before assigning new
addresses. The pentium is also a "real" IP
address that can't be connected the internet - 199.208.118.10
I can't get the two machines to ping each other...
dmesg shows the following bootup messages:
486 (skitzo):
smc-ultra.c:v2.02 2/3/98 Donald Becker ([EMAIL PROTECTED])
eth0: SMC EtherEZ at 0x240, 00 00 C0 4B B4 C7,EEPROM IRQ 11
programmed-I/O mode.eth0
pentium (bipolar):
smc-ultra.c:v2.02 2/3/98 Donald Becker ([EMAIL PROTECTED])
eth0: SMC EtherEZ at 0x240, 00 00 C0 09 94 C7,EEPROM IRQ 11
programmed-I/O mode.
Here's ifconfig on eth0:
[root@skitzo /]# ifconfig eth0
Link encap:Ethernet HWaddr 00:00:C0:4B:B4:C7
inet addr:199.208.118.159 Bcast:199.208.118.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:245 errors:0 dropped:0 overruns:0
TX packets:1087 errors:0 dropped:0 overruns:0
Interrupt:11 Base address:0x250 Memory:c0000-c2000
[root@bipolar floppy]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:00:C0:09:94:C7
inet addr:199.208.118.10 Bcast:199.208.118.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:0 dropped:0 overruns:0 carrier:0
collisions:0
Interrupt:11 Base address:0x250 Memory:c0000-c2000
[root@skitzo init.d]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
199.208.118.0 * 255.255.255.0 U 0
0 13 eth0
127.0.0.0 * 255.0.0.0
U 0 0 4 lo
default * 0.0.0.0
U 0 0 0 eth0
[root@bipolar floppy]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
199.208.118.0 * 255.255.255.0 U
0 0 0 eth0
127.0.0.0 * 255.0.0.0 U
0 0 0 lo
[root@skitzo /root]# netstat -r -n
Kernel IP routing table
Destination Gateway Genmask Flags MSS
Window irtt Iface
199.208.118.0 0.0.0.0 255.255.255.0 U
1500 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0
U 3584 0 0 lo
0.0.0.0 199.208.118.159 0.0.0.0 UG
1500 0 0 eth0
[root@bipolar floppy]# netstat -r -n
Kernel IP routing table
Destination Gateway Genmask Flags MSS
Window irtt Iface
199.208.118.0 0.0.0.0 255.255.255.0 U
1500 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0
U 3584 0 0 lo
[root@skitzo init.d]# cat /proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-009f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : npu
01f0-01f7 : ide0
0240-025f : SMC EtherEZ
03c0-03df : vga+
03f0-03f5 : floppy
03f6-03f6 : ide0
03f7-03f7 : floppy DIR
03f8-03ff : serial(auto)
[root@bipolar floppy]# cat /proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-009f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : npu
01f0-01f7 : ide0
0240-025f : SMC EtherEZ
02f8-02ff : serial(auto)
03c0-03df : vga+
03f0-03f5 : floppy
03f6-03f6 : ide0
03f7-03f7 : floppy DIR
03f8-03ff : serial(auto)
fbf0-fbf7 : IDE DMA
[root@skitzo init.d]# cat /proc/interrupts
0: 2792335 timer
1: 7713 keyboard
2: 0 cascade
4: 79965 + serial
8: 1 + rtc
11: 1350 SMC EtherEZ
13: 1 math error
14: 361097 + ide0
[root@bipolar net]# cat /proc/interrupts
0: 283524 timer
1: 4544 keyboard
2: 0 cascade
6: 10 + floppy
8: 1 + rtc
11: 0 SMC EtherEZ
12: 141004 PS/2 Mouse
13: 1 math error
14: 21054 + ide0
It isn't conflicts, it isn't routing tables (or is it?), and it
definitely isn't a failure of eth0 to be recognized by the kernel.
I edited /etc/hosts on both machines and added the name and IP address
of the other machine.
I remembered how I didn't ever get even a ping returned at work until I
put in the address of the DNS server, even
though I was pinging machines in my /etc/hosts file, so I made the 486
the nameserver and started up named on it. I set
the other box to use the 486 as the default nameserver but it still
didn't work. I suspect that I didn't set up DNS right,
and the books didn't seem to help any.
[root@skitzo /]# cd /proc/net
[root@skitzo net]# cat dev
Inter-| Receive | Transmit
face |packets errs drop fifo frame|packets errs drop fifo colls
carrier
lo: 932 0 0 0 0 932 0
0 0 0 0
eth0: 465 0 0 0 0 1407 0
0 0 0 0
[root@bipolar floppy]# cd /proc/net
[root@bipolar net]# cat dev
Inter-| Receive | Transmit
face |packets errs drop fifo frame|packets errs drop fifo colls carrier
lo: 0 0 0 0 0 0
0 0 0 0 0
eth0: 0 0 0 0 0 0
0 0 0 0 0
I realize that the packets under "receive" came from me pinging my own
machine.
My pentium has one partition with dual boot win95/NT4 so I booted up NT
and it recognized the card and installed it
properly. I added the Linux box to it's LMHOSTS file and tried to ping
it... no luck.
I also installed a network monitor which gives reports on all the
packets, so I set the NT box and skitzo pinging
each other continuously, and watched. The packets on the NT box
(bipolar) were going to the right broadcast address,
199.208.118.255 but nothing seemed to be going down the wire. The
sniffer also showed nothing from skitzo.
I guess I need to rule out the thinnet wiring itself but it's brand new,
and so are the connectors (with the proper 50 ohm
terminators). I bought 50 ohm RGU58A/U cabling, is it the right kind?
One interesting thing is that my NIC's lights on both machines blink
when I give ping commands. I'm guessing that the
lights indicate packet activity, so where am I going wrong?
I've even totally redone /etc/smb.conf to try and talk to the NT box
using Samba but no luck.
Anyone have any ideas?
I tried to include every troubleshooting command I could come up with.
If I left out anything, just reply and request it.
Thanks
Nate
------------------------------
Date: Sat, 09 Jan 1999 17:23:02 +0100
From: Joerg Ammon <[EMAIL PROTECTED]>
Subject: Re: Need help with diagnosing a network problem
Hi Jay,
in case you're planning to replace your hub by a switch - do that quick!
Since a switch writes packet statistics on every port it's really no big deal to
identify a bad NIC (in case you have one!).
>From what I can see in your loggings it might as well be just a busy
shared media ethernet!!!
What applications have you got running?
How many user accessing this segment?
etc...
Do a quick calculation AND change to a switch soon!
The only proper way of identifying a bad hub port is shuffling the links to free
ports ;-(
In case you've got some sort of packet sniffer (there is e.g. tcpdump) you might
as
well get a hint of your problem on actual looking at the packets themselves. If
you see
a large number of error frames you can then identify the host.
Jay D Ribak wrote:
> Hi,
> I am having a bit of a network problem on my small network. I am not
> sure where to go from here to troubleshoot the problem further. Background:
> 5 Linux PCs on a mini-hub, all running 10mbs ethernet. The hub is uplinked
> to a 10mbs switch, which is in turn connected to a Cisco router and a T1. I
> have noticed huge numbers of collisions lately on each system. When
> looking at the hub, the collision LED is blinking at least once every two
> seconds. Here are some stats from ifconfig on one of the boxes:
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:62419179 errors:1984 dropped:1984 overruns:627
> frame:1984
> TX packets:63294738 errors:2 dropped:0 overruns:0 carrier:256644
> coll:436889
> Interrupt:10 Base address:0x300
>
> As you can see the number of collisions is quite large. This is now slowing
> down performance between the systems, and from the T1 into the servers from
> the outside world. I am not sure if I have a bad NIC somewhere, a bad port
> on the hub, or what. I also don't know how to figure that out from here.
> I have another 10mbs switch on order, and I plan on replacing the hub with
> the switch. From what I understand of switching technology this should
> significantly lower or eliminate the collisions. I don't really like the
> idea of glossing over a potential problem with a NIC though. The systems
> are also high availability servers and so I can't just bring them down to
> swap out NICs unless I have proof that one is indeed bad.
>
> What tools are there in Linux to allow me to analyze network traffic to
> figure out which system is causing all of the collisions?
>
> Thanks
> Jay R.
------------------------------
From: [EMAIL PROTECTED] (Yaye)
Subject: Re: Netscape 4.5=DUD !?
Date: 09 Jan 1999 16:22:30 GMT
Hello,
I'd like to know how to do the same things with Communicator 4.06 for Linux.
Although the help file states go to File then Go Offline, there is no such
option under File. Thanks in advance.
Ian
------------------------------
Date: Sat, 09 Jan 1999 17:23:35 +0100
From: Joerg Ammon <[EMAIL PROTECTED]>
Subject: Re: Need help with diagnosing a network problem
Hi Jay,
in case you're planning to replace your hub by a switch - do that quick!
Since a switch writes packet statistics on every port it's really no big deal to
identify a bad NIC (in case you have one!).
>From what I can see in your loggings it might as well be just a busy
shared media ethernet!!!
What applications have you got running?
How many user accessing this segment?
etc...
Do a quick calculation AND change to a switch soon!
The only proper way of identifying a bad hub port is shuffling the links to free
ports ;-(
In case you've got some sort of packet sniffer (there is e.g. tcpdump) you might
as
well get a hint of your problem on actual looking at the packets themselves. If
you see
a large number of error frames you can then identify the host.
Jay D Ribak wrote:
> Hi,
> I am having a bit of a network problem on my small network. I am not
> sure where to go from here to troubleshoot the problem further. Background:
> 5 Linux PCs on a mini-hub, all running 10mbs ethernet. The hub is uplinked
> to a 10mbs switch, which is in turn connected to a Cisco router and a T1. I
> have noticed huge numbers of collisions lately on each system. When
> looking at the hub, the collision LED is blinking at least once every two
> seconds. Here are some stats from ifconfig on one of the boxes:
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:62419179 errors:1984 dropped:1984 overruns:627
> frame:1984
> TX packets:63294738 errors:2 dropped:0 overruns:0 carrier:256644
> coll:436889
> Interrupt:10 Base address:0x300
>
> As you can see the number of collisions is quite large. This is now slowing
> down performance between the systems, and from the T1 into the servers from
> the outside world. I am not sure if I have a bad NIC somewhere, a bad port
> on the hub, or what. I also don't know how to figure that out from here.
> I have another 10mbs switch on order, and I plan on replacing the hub with
> the switch. From what I understand of switching technology this should
> significantly lower or eliminate the collisions. I don't really like the
> idea of glossing over a potential problem with a NIC though. The systems
> are also high availability servers and so I can't just bring them down to
> swap out NICs unless I have proof that one is indeed bad.
>
> What tools are there in Linux to allow me to analyze network traffic to
> figure out which system is causing all of the collisions?
>
> Thanks
> Jay R.
------------------------------
Date: Sat, 09 Jan 1999 17:24:45 +0100
From: Joerg Ammon <[EMAIL PROTECTED]>
Subject: Re: Need help with diagnosing a network problem
Hi Jay,
in case you're planning to replace your hub by a switch - do that quick!
Since a switch writes packet statistics on every port it's really no big deal to
identify a bad NIC (in case you have one!).
>From what I can see in your loggings it might as well be just a busy
shared media ethernet!!!
What applications have you got running?
How many user accessing this segment?
etc...
Do a quick calculation AND change to a switch soon!
The only proper way of identifying a bad hub port is shuffling the links to free
ports ;-(
In case you've got some sort of packet sniffer (there is e.g. tcpdump) you might
as
well get a hint of your problem on actual looking at the packets themselves. If
you see
a large number of error frames you can then identify the host.
Jay D Ribak wrote:
> Hi,
> I am having a bit of a network problem on my small network. I am not
> sure where to go from here to troubleshoot the problem further. Background:
> 5 Linux PCs on a mini-hub, all running 10mbs ethernet. The hub is uplinked
> to a 10mbs switch, which is in turn connected to a Cisco router and a T1. I
> have noticed huge numbers of collisions lately on each system. When
> looking at the hub, the collision LED is blinking at least once every two
> seconds. Here are some stats from ifconfig on one of the boxes:
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:62419179 errors:1984 dropped:1984 overruns:627
> frame:1984
> TX packets:63294738 errors:2 dropped:0 overruns:0 carrier:256644
> coll:436889
> Interrupt:10 Base address:0x300
>
> As you can see the number of collisions is quite large. This is now slowing
> down performance between the systems, and from the T1 into the servers from
> the outside world. I am not sure if I have a bad NIC somewhere, a bad port
> on the hub, or what. I also don't know how to figure that out from here.
> I have another 10mbs switch on order, and I plan on replacing the hub with
> the switch. From what I understand of switching technology this should
> significantly lower or eliminate the collisions. I don't really like the
> idea of glossing over a potential problem with a NIC though. The systems
> are also high availability servers and so I can't just bring them down to
> swap out NICs unless I have proof that one is indeed bad.
>
> What tools are there in Linux to allow me to analyze network traffic to
> figure out which system is causing all of the collisions?
>
> Thanks
> Jay R.
------------------------------
Date: Sat, 09 Jan 1999 17:25:49 +0100
From: Joerg Ammon <[EMAIL PROTECTED]>
Subject: Re: Need help with diagnosing a network problem
Hi Jay,
in case you're planning to replace your hub by a switch - do that quick!
Since a switch writes packet statistics on every port it's really no big deal to
identify a bad NIC (in case you have one!).
>From what I can see in your loggings it might as well be just a busy
shared media ethernet!!!
What applications have you got running?
How many user accessing this segment?
etc...
Do a quick calculation AND change to a switch soon!
The only proper way of identifying a bad hub port is shuffling the links to free
ports ;-(
In case you've got some sort of packet sniffer (there is e.g. tcpdump) you might
as
well get a hint of your problem on actual looking at the packets themselves. If
you see
a large number of error frames you can then identify the host.
Jay D Ribak schrieb:
> Hi,
> I am having a bit of a network problem on my small network. I am not
> sure where to go from here to troubleshoot the problem further. Background:
> 5 Linux PCs on a mini-hub, all running 10mbs ethernet. The hub is uplinked
> to a 10mbs switch, which is in turn connected to a Cisco router and a T1. I
> have noticed huge numbers of collisions lately on each system. When
> looking at the hub, the collision LED is blinking at least once every two
> seconds. Here are some stats from ifconfig on one of the boxes:
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:62419179 errors:1984 dropped:1984 overruns:627
> frame:1984
> TX packets:63294738 errors:2 dropped:0 overruns:0 carrier:256644
> coll:436889
> Interrupt:10 Base address:0x300
>
> As you can see the number of collisions is quite large. This is now slowing
> down performance between the systems, and from the T1 into the servers from
> the outside world. I am not sure if I have a bad NIC somewhere, a bad port
> on the hub, or what. I also don't know how to figure that out from here.
> I have another 10mbs switch on order, and I plan on replacing the hub with
> the switch. From what I understand of switching technology this should
> significantly lower or eliminate the collisions. I don't really like the
> idea of glossing over a potential problem with a NIC though. The systems
> are also high availability servers and so I can't just bring them down to
> swap out NICs unless I have proof that one is indeed bad.
>
> What tools are there in Linux to allow me to analyze network traffic to
> figure out which system is causing all of the collisions?
>
> Thanks
> Jay R.
------------------------------
Date: Sat, 09 Jan 1999 17:26:11 +0100
From: Joerg Ammon <[EMAIL PROTECTED]>
Subject: Re: Need help with diagnosing a network problem
Hi Jay,
in case you're planning to replace your hub by a switch - do that quick!
Since a switch writes packet statistics on every port it's really no big deal to
identify a bad NIC (in case you have one!).
>From what I can see in your loggings it might as well be just a busy
shared media ethernet!!!
What applications have you got running?
How many user accessing this segment?
etc...
Do a quick calculation AND change to a switch soon!
The only proper way of identifying a bad hub port is shuffling the links to free
ports ;-(
In case you've got some sort of packet sniffer (there is e.g. tcpdump) you might
as
well get a hint of your problem on actual looking at the packets themselves. If
you see
a large number of error frames you can then identify the host.
Jay D Ribak schrieb:
> Hi,
> I am having a bit of a network problem on my small network. I am not
> sure where to go from here to troubleshoot the problem further. Background:
> 5 Linux PCs on a mini-hub, all running 10mbs ethernet. The hub is uplinked
> to a 10mbs switch, which is in turn connected to a Cisco router and a T1. I
> have noticed huge numbers of collisions lately on each system. When
> looking at the hub, the collision LED is blinking at least once every two
> seconds. Here are some stats from ifconfig on one of the boxes:
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:62419179 errors:1984 dropped:1984 overruns:627
> frame:1984
> TX packets:63294738 errors:2 dropped:0 overruns:0 carrier:256644
> coll:436889
> Interrupt:10 Base address:0x300
>
> As you can see the number of collisions is quite large. This is now slowing
> down performance between the systems, and from the T1 into the servers from
> the outside world. I am not sure if I have a bad NIC somewhere, a bad port
> on the hub, or what. I also don't know how to figure that out from here.
> I have another 10mbs switch on order, and I plan on replacing the hub with
> the switch. From what I understand of switching technology this should
> significantly lower or eliminate the collisions. I don't really like the
> idea of glossing over a potential problem with a NIC though. The systems
> are also high availability servers and so I can't just bring them down to
> swap out NICs unless I have proof that one is indeed bad.
>
> What tools are there in Linux to allow me to analyze network traffic to
> figure out which system is causing all of the collisions?
>
> Thanks
> Jay R.
------------------------------
From: "Raymond" <[EMAIL PROTECTED]>
Subject: use CDE remotely
Date: Sat, 9 Jan 1999 10:30:52 -0600
At the office I've got a Sun workstation running Solaris 2.5 and CDE gui.
At home I'm running Suse 5.3. There's no problem dialing in to the
office network from home with PPP, telneting to my workstation and
getting a shell prompt.
My question is: Is it possible to make the CDE desktop appear on
my home box and what additional software would it take?
Thanks.
Ray
------------------------------
From: Yves Schlegel <[EMAIL PROTECTED]>
Subject: Trouble with networ-card ne2000 PCI
Date: Sat, 09 Jan 1999 17:09:30 +0100
Hello everyone out there!
I'm new to linux and I faced some problems configuring the network. I'm
using SuSE 5.3 with kernel 2.0.35.
The loopback network is working very well, but not eth0. I'm using a
NE2000-compatible PCI card with realtek8029-chip, it is correctly
detected, but I can't ping on 192.168.1.1. When I ping the server on
192.168.1.1 from a client, I just receive Host unreachable, when I ping
127.0.0.1 it is reachable!
I saw that in startup there was an error-message, netmask not correct
defined. But it should be correct becuase it is set to 255.255.255.0,
broadcast 192.168.1.255, subnet 192.168.1.0.
Does anyonecould help solving my problem?
Sincerely, Yves
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.networking) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Networking Digest
******************************
