Re: [microblaze-uclinux] ping

[John Williams <jwilliams@itee.uq.edu.au>]

Hi Rahul,

Rahul Sarvadevabhatla wrote:
> We are trying to get TCP/IP going with mbvanilla_net on Insight/Memec 
> V2MB1000 board. After bootup we ran the following comands
> 
> ifconfig lo 127.0.0.1
> ifconfig eth0 192.168.1.189
> 
> When we did ping 192.168.1.189, it was able to send and receive packets. 

Yes - pings to the same ip address get automatically routed through the 
loopback (lo) device, so never actually hit the wire.

> But when we tried to ping another ip it could not do it. What are the 
> options which we have to set while buiding the kernel to be able to ping 
> other computers in the network.

There could be a couple of reasons - firstly you should specify a 
netmask and broadcast address - for your internal network (192.168....) 
you would probably use 255.255.255.0 as the netmask, and 192.168.1.255 
as the broadcast address - or check with your local network admin.

You will find it very very help[ful to put a linux box on the same 
network, and run tcpdump.  Do man tcpdump for more command line options, 
but basically you can sniff all traffic to or from a particular IP or 
MAC address, examine the contents, etc etc.  Very useful for getting 
this sort of thing up and running.

Regards,

John

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/