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

[Denys Vlasenko]

On Tuesday 21 April 2009 19:20, Chris Plasun wrote:
> 
> > > Is tshark for the console? I'm going to try it.
> > 
> > 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:

> > "ip a"
> 1: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
                                ^^ it's up
>     link/ether 00:e0:0c:00:95:01 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.100/24 brd 192.168.1.255 scope global eth0
           ^^^^^^^^^^^^^^^^ it has address
> 2: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
>     link/ether 00:e0:0c:00:95:02 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.207/24 brd 192.168.1.255 scope global eth1
> 3: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
> 
> > "ip r" 
> 192.168.1.0/24 dev eth0  src 192.168.1.100
  ^^^^^^^^^^^^^^^^^^^^^^^^ the packets can be routed through it
> 192.168.1.0/24 dev eth1  src 192.168.1.207
> 127.0.0.0/8 dev lo
> default via 192.168.1.1 dev eth1

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?
--
vda