'ping' is hurting my feelings

[Christopher Reid Palmer <reid@pconline.com>]

Hello all,

I am having some network problems. My home netbroke (I can't call it a
net*work*, since it doesn't yet) is the simplest possible: one Mac, one
Linux box, one crossover cable+AUI-TP transceiver (the Mac has only an
AUI jack, no 10BaseT).

The Mac is 192.168.0.2, the Linux box is 192.168.0.1.

I can ping the Mac from the Linux box:

===
[reid@dusk ~ ] ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: icmp_seq=0 ttl=255 time=3.6 ms
64 bytes from 192.168.0.2: icmp_seq=1 ttl=255 time=1.5 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=255 time=1.5 ms
64 bytes from 192.168.0.2: icmp_seq=3 ttl=255 time=1.5 ms
64 bytes from 192.168.0.2: icmp_seq=4 ttl=255 time=1.5 ms
64 bytes from 192.168.0.2: icmp_seq=5 ttl=255 time=1.7 ms
64 bytes from 192.168.0.2: icmp_seq=6 ttl=255 time=1.5 ms
64 bytes from 192.168.0.2: icmp_seq=7 ttl=255 time=1.5 ms
64 bytes from 192.168.0.2: icmp_seq=8 ttl=255 time=1.5 ms
64 bytes from 192.168.0.2: icmp_seq=9 ttl=255 time=1.5 ms
64 bytes from 192.168.0.2: icmp_seq=10 ttl=255 time=1.5 ms

--- 192.168.0.2 ping statistics ---
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 1.5/1.7/3.6 ms
===

The blinky lights on the transceiver do their thing. Good.


But the Linux box can't ping itself:

===
[reid@dusk ~ ] ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
ping: sendto: No buffer space available
ping: wrote 192.168.0.1 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 192.168.0.1 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 192.168.0.1 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 192.168.0.1 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 192.168.0.1 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 192.168.0.1 64 chars, ret=-1

--- 192.168.0.1 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss
===

When I try to BetterTelnet from the Mac to the Linux box, I get the
message 'Host or gateway not responding: 192.168.0.1'. Fetch (a Mac FTP
client) tells me 'The connection was refused' when I try to ftp to the
Linux box.

My /etc/inetd.conf does not have the ftp or telnet lines commented out
(which would explain the 'connection refused' message).

I'm running Red Hat 5.2, stock except for one big thing: kernel 2.2.6. I
did the questionable thing of upgrading only the kernel and none of the
other stuff. Could that be the problem? If so, what software do I need
to upgrade?

I'm going to compile and boot 2.0.36 now, and see what I get. But even
if that succeeds, I'd still like to know what userland stuff needs to be
upgraded, since I like 2.2.6 (it's faster!).


Thanks in advance,
-- Chris :)

_____________________________________________________________________________
Christopher Reid Palmer : reid@pconline.com : http://innerfire.visi.com/