Wonky Ping (ping don't work)

[Steve Iribarne (GMail)]

Chris..

No worries.. you just need to learn to redirect your questions to the
right place.  Basically your question would have been ignored.  I'm
going to keep this on the list just for fun, but guys on the list, if
it gets annoying, let me know and I'll take it offline.

I have a few minutes while my compile is happening so I'll try to help
you out here.

First off, "SIOCDELRT", just looking at it what do you think it means?
 We generally try to make error strings like that make some sort of
sense.

SIOC usually means the System or driver 'ioctl' (short for i/o control)
DEL usually short for something like "delete"
RT in this case I would guess to mean route.

So what that tells me is that the udhcpc is trying to delete a route
that doesn't exists.  So you are ok there.  I could be wrong, but I'm
pretty sure that's it.


The rest I'll answer in line.

>> >
>> > I have another issue now with ping. I figure it doesn't make sense to
>> > make the MPC8313 board work as a NFS client until there are no problems
>> > with ping.
>> >

Yes good assumption.


>> > DHCP appears to work fine:
>> >
>> > ~ # udhcpc -i eth1
>> > udhcpc (v0.9.9-pre) started
>> > udhcpc[796]: udhcpc (v0.9.9-pre) started
>> > Sending discover...
>> > udhcpc[796]: Sending discover...
>> > Sending select for 192.168.1.207...
>> > udhcpc[796]: Sending select for 192.168.1.207...
>> > Lease of 192.168.1.207 obtained, lease time 86400
>> > udhcpc[796]: Lease of 192.168.1.207 obtained, lease time 86400
>> > deleting routers
>> > S

Yes again.. DHCP is now working.


>> > adding dns 64.59.144.18
>> > adding dns 64.59.144.19
>> >
>> > BTW Does 'SIOCDELRT: No such process' mean anything ominous?
>> >

So I answer the SIOCDELRT thing above.  Also I didn't try this but did
you try to google it and see if anyone had any true insight on this?

Also you'll note that the DHCP Response from your DHCP server told us
to add 64.59.144.18 and 19 as our dns servers.  So we did it.  Whether
they are up or not is not our problem, it's the network admins
problem.

>> > The problem is that I can't ping anything on the local network, either
>> > at home or at work.
>> >

Ok, so you gave me nothing to work with here.  All I know from what
you have told me is that the MPC board has an ip address of
192.168.1.207.  I would assume the subnet mask is 255.255.255.0.

What is the ip address of your PC's??

>> > And I can't ping the board with my PC.
>> >
>> > I tried another board that hasn't been worked on before and same issue
>> > again.
>> >
>> > Last week the board, PC and the virtual Suse machine were pinging each
>> > other back and forth.
>> >
>> > I can however ping outside the network. I've tried www.asp.net,
>> > yahoo.com, spiegel.de and google.com and those work fine.
>> >
>> > msn.com and microsoft.com fail, though the IP address is resolved.

Whoa there tiger.  So what this tells me is a not alot.  First off,
how are you getting from your board to the outside internet?  Is there
a NAT server somewhere?  Because the 192 address most certainly is NOT
on the internet.

So why you can resolve IP addresses and not get pings back from some
sites is very strange.

And this also tells me that ping IS indeed working and it's your local
network that's busted.

Again, wireshark is your friend here.

>> >
>> > I can't ping one of the DNS servers.
>> >

Not a big deal.  This is why you usually get two DNS servers.  They go
up and down all the time.  At least mine do.. but then again, our IT
dept. here is not what I would call stellar.

>> > I've been read and asking various people but I can't figure out what's
>> > wrong.
>> >
>> > How do I diagnose this?
>> >

Wireshark, wireshark, wireshark.  Put it everywhere in your network
and find out where the packets are going...

Hope this helps.  Let me know if you need more help and I'll do my
best time if I have time.

-stv