[Bulk] Re: Wonky Ping (ping don't work)

[Chris Plasun]

> > > Tshark is the text-based version of wireshark.  It's included in the
> > > wireshark package (wireshark is the full-fledged GUI version).  Tcpdump is
> > > a simpler text-based protocol analyzer.  Tcpdump is easier and quicker
> > > to build than tshark, and probably uses signficantly less resources at
> > > runtime (I'm guessing at the latter; I haven't actually checked), so
> > > you should probably just put tcpdump on target.  You can save captures
> > > using tcpdump on-target and analyze them later on a host with wireshark
> > > installed, or you can have tcpdump print a line of text on-the-fly for
> > > each packet.  The latter should be fine for your current needs.
> > > 
> > > --Doug
> > 
> > Thanks Doug. I'm hoping the issue is with the setup.
> > Now need to find PPC versions of these programs. 
> 
> The configured address on eth0 is definitely a configuration error:
> If you use eth1 for connection, eth0 is better be deconfigured and
> downed. You need to find out why on every boot up it gets configured
> in the first place - is some script uses hardcoded "eth0" somewhere?

Yes, eth0 is down now and everything works. I noticed there's nothing in the routing table.

I figure I should look in /etc/rc.d/rcS ?

I think I'm converting over to Linux, the OS Jesus would use :P

Now on to NFS!