IP Over 1394/Firewire?

Chanc_Gorkon asks: "Just like to ask the Slashdot community if anyone has a set of step-by-step instructions for connecting two computers via IP over Firewire. Mac OS X Panther supports IP over Firewire, as does Windows XP. I would like to hook my PowerBook to a Windows XP machine, and be able to access the Internet and share files over the link. I am shooting for near full functionality, but the closest I came in my initial trials was being able to set static IP's per Firewire port, and do a FTP between the machines. If I can get this working, I figure this will be a good way of getting my PowerBook on the office network, without having to have a drop put in."

Comments

you'll need this..

[danalien]

what you need for this is recipt:

*eth1394 (depends on ieee1394 - and both are in the latest kernels - I know it's in the 2.4.20+ for a fact *use it myself..not eth1394, but ieee1394...*)

• but Read this site carefully, check your kernel,
• download a patch & patch it if necessary... the 'usual common sense'-principle...

  so grab a supported/the patched kernel...,and don't don't forget to configure & compile it with these options:

  • 'OHCI-1394 support'
  • 
    'Ethernet over 1394
    'Raw IEEE1394 I/O support'
    ...ps, and maybe while you're at it, add 'SBP-2 support (Harddisks etc.)' too ...
    

  (btw, in 2.4.20+ - you'll need to enable "Code maturity level options --> [*] Prompt for development and/or incomplete code/drivers" , or else you won't see the "IEEE 1394 (FireWire) support (EXPERIMENTAL)" all this is under..)

  if you compiled 'all of these things' as 'Modules', don't forget to load up these modules(and try to do them in that order....):

  • ieee1394
  • 
    raw1394
    ohci1394
    eth1394

  elsewise, load only those that are modules .... - and if you compiled all of them into your kernel, just skip all of the above...

  !PS - on some hardware it's also required that you first unload 'ohci1394' before you remove your the Firewire Controller (ONLY for PCMCIA users ...)

  !PS - if you are a really 'unfamiliar with loading & unloading drivers' & 'don't know how to automate these things'.... don't bother, stick with your windows/OS X box... }:-)

* and you might also want to check these out:

• DVTS - for some furthur info if you don't manage on your own ( they are implementing a "..DV streams from IEEE1394 over IP.", sorta related, I guess)
• FIREHOSE - "FIREHOSE gives you a basic data transfer over multiple network devices supporting TCP/IP layers. Stripe multiple 100Mbit, Gigabit, 10 Gigabit, or firewire to give one humungous pipe for firehosing your gigabytes and gigabytes of data." (I guess, also related...)

OP: A better way.

[Glonoinha]

I am guessing that the Windows machine is connected to the network via Ethernet, and there is a single Ethernet port in your work area that a little Ethernet cable plugs into on one side, the other side going into the Ethernet jack on your Windows machine.

Go to Best Buy, or Circuit City, or Frys and buy a small Linksys 4 port 10/100 switch for about $40. Buy an extra Ethernet cable or two. Get a crossover Ethernet cable just in case, save yourself a trip in you need it - buy a red one so you don't have to figure out why it doesn't work in places that regular Ethernet cables go.

Unplug the Ethernet cable from the Windows machine. Plug it into the switch in the one socket that is set apart from the other four (this is the uplink.) Plug the two new cables (not the crossover) into any two holes in the switch they will fit. Plug the other end of one into your Windows machine, and the other end of the other into the Apple.

Turn everything on. Voila! Everything pretty much works and you didn't need an extra drop. You can even hide the little Linksys switch under your desk so the IT department doesn't know that you have tampered with the network.

Last suggestion, network admins can peruse the names of all the machines on their network. I suggest you name the Apple laptop something that looks like it fits in with all the other corporate network machines. I do not know how to do this on an Apple, or even if it applys, but it is worth noting.
-
As for making computers communicate over firewire or USB as a way to emulate or replace regular network components ... why, when doing it the straightforward way is so much simpler?