Slashdot Mirror


Apple Releases Preview of IP over FireWire

A user writes, "Apple has finally released IP over FireWire drivers for Mac OS X. It is now possible to connect two or more Macs together with FireWire cables and if needed, FireWire hubs."

8 of 116 comments (clear)

  1. IP over FireWire by tps12 · · Score: 5, Funny

    Jeez, the MPAA was already upset about IP over Ethernet. This'll drive them up the wall.

    --

    Karma: Good (despite my invention of the Karma: sig)
  2. It's at least another option by Spencerian · · Score: 5, Interesting

    Currently you can connect most Macs together by a crossover Ethernet cable for networking. Alternatively, if you just need to move something between two boxes, you can use a FireWire cable and mount another hard drive with Target Disk Mode (which someone noted earlier).

    So IP over FireWire adds to the diversity. Today, you don't even need a crossover cable with the Gigabit Ethernet ports on most Macs. Just use a regular CAT5 to connect them.

    Having this option, from my techie POV, allows me to connect to another Mac should the user's Ethernet port go cranky. I'd have to think a little more for additional applications, but perhaps a cheap, high speed FireWire LAN for gaming or small home networks would be useful. I would think you can share a cable modem connection in this manner, too. I better RTFdocs.

    --
    Vos teneo officium eram periculosus ut vos recipero is.
  3. On XP it works nicely. by kmellis · · Score: 4, Informative

    I've been using IP on 1394 from my desktop box to my Sony laptop. I just bridge my ethernet and firewire NICs on my desktop PC, and the Sony has an Internet connection over Firewire (which they call "i.Link"). It works great. Theoretically, I should be seeing four times the bandwidth on the 1394 link than I see with 100 Ethernet, but in reality it's not that big of a difference. As people are saying about gig-ethernet, other things, like the PCI bus, start to be limiting factors.

  4. Re:cluster me crazy by kuwan · · Score: 5, Interesting
    Well, a Firewire network would be a lot cheaper. For a gigabit ethernet network you'd have to get a gigabit switch which are pretty expensive (at least $800-$900). For a Firewire netword you wouldn't even need a hub as computers can be daisy-chained together (assuming they have at least two Firewire ports). But if you do need a Firewire hub, they're pretty cheap compared to a gigabit hub/switch.

    Also, many Macs can't be upgraded to gigabit ethernet. iMacs, iBooks, older PowerBooks, and older PowerMac don't have gigabit ethernet, but many of them do have Firewire. So depending on what you have, building a Firewire network is much more attractive than trying to build a gigabit ethernet network.

  5. Any iPod-based Applications? by kalidasa · · Score: 4, Insightful

    I know this is for OS X, and the OS on the iPod is different, but what about using IP-over-Firewire for IP synching of iPods?

  6. Repeat after me: by Genady · · Score: 4, Funny

    IP Over Firewire is not the new localtalk. IP Over Firewire is not the new localtalk. IP Over Firewire is not... oh the hell with it.

    Why do I see the little daisy chain boxes showing up in schools again?

    (But you see Mr. School administrator with shrinking funds, you don't need to buy a hub or switch, we've got that covered.)

    --


    What if it is just turtles all the way down?
  7. Re:FireWire Target Disk Mode by tim1724 · · Score: 4, Insightful

    Why would you want and/or need AppleTalk?

    AFP (Apple Filing Protocol, what the marketing people call "AppleShare") works great over TCP.

    Given Jaguar's support for Rendevous and AFP over TCP, what does AppleTalk get you? AppleTalk's only place in today's world is for compatibility with legacy machines, but that doesn't apply here, as Apple only supplies this software for Jaguar.

    --
    -- Tim Buchheim
  8. Re:It deleted my network settings by tim1724 · · Score: 4, Informative

    aha.. macfixit.com has the solution. It turns out that for some reason /var/db/SystemConfiguration/preferences.xml is renamed to preferences.xml-old .. so just move it back:

    cd /var/db/SystemConfiguration/
    mv preferences.xml-old preferences.xml

    --
    -- Tim Buchheim