Hi!

I hope somebody can help me.

I tried to connect an windows PC (Win XP) and a linux machine (Suse Linux 2.4.20) with IP over Firewire. (1394b)!!!

I tried to ping, but that doesn't work.

To view the traffic on the 1394 bus, I recorded the ping operation each between two linux PCs and two XP PCs with FireSpy.

Both packed the IP frame in their data block. So far, so good, here comes my problem:

Linux seems to use the split transaction mode resp. concatenated transaction mode. That means, after a WriteBlockRequest comes a WriteResponse.

XP seems to use the unified transaction mode. Means there is no response subaction. The acknowledge packet informs the requester that the subaction is complete. (I hope I am right so far).

Why do XP and Linux use different transaction modes? Where is this defined? How can I influence this?

I think it must be possible to connect XP and Linux, because Linux is able to transfer data with IP over Firewire to anothe Linux machine.



I would be glad, if somebody could help me!!

I'm having the exact same problem. Linux to linux via firewire, pinging is no problem; WinXP to WinXp, complete network capabilities. Linux to WinXP and I get nothing. My windows box does; however, show up in gscanbus, but that's all.

If you get it solved, I'd like to know how you did it.

Hi!
I can not say that I have solved the problem completely, but i can ping a XP machine from a linux PC and the other way round. I can also do a file transfer.

I found a problem in the ohci1394.c driver module for ieee1394.
The module is not RFC 2734 compliant. The configuration ROM entry of the Linux 1394 card is not complete. The Linux card and the windows card swap their Config ROM entries.
The Linux driver does not write the IP capability to its config ROM as described in RFC 2734. For XP than the linux PC is not IP capable.

If you add this entry to the driver module ohci1394.c as described on page 13/14 in RFC2734, the connection works.

But it is very unstable. I suggest, because of that, the driver developers removed this entry out of the driver module to avoid the crash of the Linux system (that is sometimes the result of the connection).

I will work on that problem.

Wow, fantastic work in figuring that out... let the guys at www.linux1394.org know about your findings... if you think it's stable, I'd really appreciate specific instructions on how to achieve the connection, and there are plenty more..

Please keep us posted with your progress...

*goes to see ohci1394.c for himself *

Keep up the good work!

On a similar issue, I'm trying to connect WinXP to win2k. I know this would be much easier using a Mac, but I haven't gotten one just yet *lucky ol' me*. Anyway, I managed to set the IP addresses on the two boxes, I just can't seem to connect to on or the other through the other. Would I use Remote Desktop Connection or SSH? I've seen some people use SCP, but I pretty much want to move some files over. Also, I'm only using one Firewire cable, someone mentioned that I have to use a crossover firewire for this to work.