Hello friends,

I've encountered a problem while establishing firewire based n/w connection between my target board and my host pc [ linux 2.4.20-8 ].

My target machine is an Intel IOP321 board with 2 firewire interfaces. It has got
montavista's 2.4.19-rmk7-ds1 as it's kernel.

The host machine is redhat 9.0 with 2.4.20-8 kernel.

Host:
I've inserted the module eth1394.o which resulted in this output:

ether1394: $Rev: 601 $ Ben Collins <bcollins@debian.org>
divert: allocating divert_blk for eth1
ether1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (ohci1394)

Later I've done
# ifconfig eth1 192.168.100.1 up
# ifconfig
eth1 Link encap:Ethernet HWaddr FF:C0:00:00:00:00
inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MTU:4088 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Target:
Here the eth1394 driver is inherent in the kernel. So I've directly used ifconfig
to up the device.

# ifconfig eth0 192.168.100.2 up
# ifconfig

Link encap:UNSPEC HWaddr DF-13-00-00-00-00-00-00-00-00-00-00-00-00-0
inet addr:192.168.100.2 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Note: You can find the differences in their Link encap fields. The former has "Ethernet" and the latter has "UNSPEC" .

Now while pinging I get this problem from the target machine:

# ping -c 2 192.168.100.1 &

PING 192.168.100.1 (192.168.100.1) from 192.168.100.2 : 56(84) bytes of data.
From 192.168.100.2 icmp_seq=1 Destination Host Unreachable
From 192.168.100.2 icmp_seq=2 Destination Host Unreachable
WARNING: failed to install socket filter
: Protocol not available

From Host:
# ping 192.168.100.1

PING 192.168.100.2 (192.168.100.2) 56(84) bytes of data.
From 192.168.100.1 icmp_seq=1 Destination Host Unreachable
From 192.168.100.1 icmp_seq=2 Destination Host Unreachable

Can you please determine where the problem is:

Thank You

regards
chaitanya

Same thing here.
And tcpdump on target host shows stuff when pinged:

20:47:00.641057 truncated-arp
0x0000: 0018 0800 1004 0002 8888 8888 8888 900c ................
0x0010: 0a02 ffff f020 0000 0b00 0002 0b00 0001 ................
20:47:01.630764 arp who-has 11.0.0.2 (88:88:88:88:88:88:90:0c) tell 11.0.0.1 hardware #24
20:47:01.630788 truncated-arp
0x0000: 0018 0800 1004 0002 8888 8888 8888 900c ................
0x0010: 0a02 ffff f020 0000 0b00 0002 0b00 0001 ................
20:47:02.624494 arp who-has 11.0.0.2 (88:88:88:88:88:88:90:0c) tell 11.0.0.1 hardware #24
20:47:02.624498 truncated-arp
0x0000: 0018 0800 1004 0002 8888 8888 8888 900c ................
0x0010: 0a02 ffff f020 0000 0b00 0002 0b00 0001 ................
20:47:03.643237 arp who-has 11.0.0.2 (88:88:88:88:88:88:90:0c) tell 11.0.0.1 hardware #24



Dmesg give me that:

ieee1394: ether1394 rx: sender nodeid lookup failure: 0-00:1023
ieee1394: ether1394 rx: sender nodeid lookup failure: 0-00:1023
ieee1394: ether1394 rx: sender nodeid lookup failure: 0-00:1023

It seems to be a 2.6.X kernel problem as firewire network works with two 2.4.33.3 computers.