Andrew,
Your kernel of 2.2.4 raises my suspicions. Did you upgrade to all
the requisite levels of software required by the 2.2 kernels? If not, you
could have unpredictable failures, and this could be one of them.
Look at the file /usr/src/linux/Documentation/Changes in the
section 'Current Minimal Requirements' for more details about the
requisite levels.
One other thing which I had suggested you try in a previous note :
ping by ip address instead of hostname. I take it you tried this and
failed?
Kenneth
There is no such thing as luck. 'Luck' is nothing but an absence of bad luck.
On Sat, 10 Apr 1999, Andrew R. Brink wrote:
> Ray Olszewski wrote:
> >
> > Hard to pinpoint a problem from what you've said. But here are a few basics
> > to check out.
> >
> > 1. Do you have an IRQ conflict. (This can cause packets to be sent but not
> > received.) Check /proc/interrupts and make sure the NIC is where you think
> > it should be.
> >
> eth0= irq 10, pretty sure nothing else is using 10.
>
> > 2. Does ifconfig succeed? (Probably, if you see the hub lights flashing when
> > you try to ping.) To be sure, run ifconfig in probe mode (that is, whthout
> > any arguments) and see if the results look right. Does each eth0 have the
> > right broadcast address (I can't remember the default if you don't specify
> > it, and the arp request needs a working broadcast address).
>
> yes it does
> >
> > 3. Might you have a routing problem? (Again, probably not, if the lights
> > flash.) To be sure, check the output of "route -n".
>
>
> >
> > 4. Might you have a kernel problem? Can each machine successfully ping
> > localhost?
> >
> yes they can
>
> > 5. After you try to ping, what does /proc/net/arp show about the destination
> > machine? Does its IP address have an associated MAC (Ethernet) address, or
> > is the entry all 0s?
>
> The interesting one,
> IP address HW type Flags HW address Mask
> Device
> 192.168.1.2 0x1 0x2 00:20:AE:E0:47:70 *
> eth0
>
>
>
> >
> > Hope this gives you some helpful ideas. BTW, if you post again, mention the
> > basics of your setup - hardware, Linux distribution and version, and kernel
> > version. For now, good luck.
>
> Slack 3.2 (old i know)
> kernel 2.2.4
> p 133 48 ram,
> 3c509b ethernet cards
>
>
> >
> > At 06:12 PM 4/10/99 -0500, Andrew R. Brink wrote:
> > >Hi,
> > >I've got my network cards (3c509b) setup on 2 machines. But they cant
> > >ping each other?
> > >
> > >Here's the setup.
> > >
> > >machine 1 ---- 3com hub ----- machine 2
> > >
> > >machine 1 : ifconfig eth0 192.168.1.1 up
> > > route add -net 192.168.1.0 netmask 255.255.255.0 eth0
> > >
> > >machine 2 : ifconfig eth0 192.168.1.2 up
> > > route add -net 192.168.1.0 netmask 255.255.255.0 eth0
> > >
> > >What have I missed in my configuration? Why can't they ping each other?
> > >
> > >I'm pretty sure that the cables are working because when the machines
> > >try to ping each other, the packet light on my hub flashes.
> >
> > ------------------------------------"Never tell me the odds!"---
> > Ray Olszewski -- Han Solo
> > 762 Garland Drive
> > Palo Alto, CA 94303-3603
> > 650.328.4219 voice [EMAIL PROTECTED]
> > ----------------------------------------------------------------
>
-====---====---====---====---====---====---====---====---====---====---====-
to unsubscribe email "unsubscribe linux-admin" to [EMAIL PROTECTED]
See the linux-admin FAQ: http://www.kalug.lug.net/linux-admin-FAQ/
