Re: strange problem connecting 2 linux boxes
From: Clifford Kite (kite_at_see.signature.id)
Date: 05/16/04
- Next message: Eugenio Milas: "ettcp output"
- Previous message: Gaétan Martineau: "I want to setup a mail server in a DMZ."
- In reply to: P Gentry: "Re: strange problem connecting 2 linux boxes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 16 May 2004 13:50:04 -0500
P Gentry <rdgentry1@cablelynx.com> wrote:
> Seems you're covering the bases, but ...
> No ifconfig or route output from 192.168.0.1 ...
If you assume that the second connection is meaningful and the 192.168.0.1
host's interface and routing didn't change before that connection then
that would seem to be irrelevant:
I took the 192.168.0.1 and connected it to a different
machine with the same non-corss cable - I could ping it!!
> However, note the ifconfig output from 192.168.0.2 :
> [quote]
> ifconfig of 192.168.0.2 gives:
> ifconfig
> eth0 Link encap:Ethernet HWaddr 00:0D:61:10:B8:AC
> inet addr:192.168.0.2 Bcast:192.168.0.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3109 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2820 errors:0 dropped:0 overruns:0 carrier:0
> collisions:661 txqueuelen:100
> RX bytes:912643 (891.2 Kb) TX bytes:2277008 (2.1 Mb)
> Interrupt:11 Base address:0x9000
> [end quote]
> You have some sort of hardware related problem with so many collisions
> -- ie., someone or something else is interferring with clean
> transmissions from this interface by trying to transmit before this
> eth0 has properly finished.
I think that may be true - or traffic from the second subnet and routing
on the eth0 interface is causing the collisions. (I did notice the
collisions, and they also seemed excessive to me, but my experience with
such things is limited so I passed on remarking about it.)
> You may want to double check link status/speed on all hosts with :
> # mii-tool -v
> You can monitor the route cache for dynamic changes (on this or other
> Linux hosts) with:
> $ /bin/netstat -rncC
> Sometimes it provides clues if connectivity is flakey or intermittent.
> You may have to test/decide if this nic is on the down-and-outs :-(
And yet he said pings from a second host to this one succeeded, albeit
with the "same non-corss cable." So unless that reference to the cable
is simply a mistake, something very strange seems to be going on.
-- Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13" PPP-Q&A links, downloads: http://ckite.no-ip.net/ /* I hear and I forget. I see and I remember. I do and I understand. --Confucius, 551-479 BC */
- Next message: Eugenio Milas: "ettcp output"
- Previous message: Gaétan Martineau: "I want to setup a mail server in a DMZ."
- In reply to: P Gentry: "Re: strange problem connecting 2 linux boxes"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
