[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] Problems with networking
Hi John,
I have futher investigated into this topic.
> Can you post the output of "ifconfig -a"
> On the lo interface? What about the eth0 interface?
here it is:
/bin> ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:00:C0:A3:E5:44
inet addr:192.168.0.242 Bcast:192.168.0.255
Mask:255.255.255.0
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:3629 errors:0 dropped:0 overruns:0 frame:0
TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:3
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:682 errors:0 dropped:0 overruns:0 frame:0
TX packets:682 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
That seems to be quite promising. After a several tests with different
options I started tcpdump on my microblaze, with quite an interesing
result:
This is what pin says:
PING 192.168.0.1 (192.168.0.1): 56 data bytes
Ans the interesting line from tcpdump:
01:14:30.350000 arp who-has 192.168.0.1 tell 229.68.192.168
As you might already have noticed in the output from ifconfig above,
the IP address of my microblaze system is supposed to be 192.168.0.242.
Not 229.68.192.168. Somehow the address is mixed up. At least the
last 2 bytes seem recognizable, althoug I would expect them at the
beginning of the IP address. I think I will have to dig deeper into
that topic. Any useful hints will be greatly appreciated.
Thanks
Erik
--
Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte untersucht
und ist - aktuelle Virenscanner vorausgesetzt - sauber.
___________________________
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/