Slashdot Mirror
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."
You need to set up Windows Internet Connection Sharing on the firewire port to allow for that connection to use your LAN drop.
http://www.homenethelp.com/ics/index.asp can help you
I've connected my Late 2001 iBook 600MHz to a friends Shuttle PC running Windows XP Pro, without issue. I turned on XP's Internet connection sharing (which includes a DHCP server), told the iBook to dynamically find an IP, and it worked.
It's all just basic troubleshooting from the point you're at.
Gimme a break. File this under "More Stupid Ask Slashdot Tricks".
I recently networked two iBooks together using IP over FireWire and was surprised to discover i was only getting about 20k a second, it was quite strange. Anyway, as for HOW to do it, it's simply an network interface option under the Network system pref panel. Anyone else get it working, but not get the speed the were expecting?
Cloud City Digital: DVD Production at its cheapest/finest
If you want to get your PowerBook on line at the office don't waste your time with firewire, just buy a cheap hub.
Use the right tool for the job. Firewire probably can be coersed into working, but it was not designed as a netwroking tool. Thus it will definately will be a lot bigger pain in the butt than simply using standard network tools.
I speak for e experience of trying to get an SLIP connection going between my desktop and my HP 200LX back in the day. I also wasted time with an old notebook and laplink parrellel cables, because I did not want to spend $200 at the time for a PCMCIA network card.
The times have changed, take advantage of it.
MS2k
Are you running the latest version of OS X. OS X 10.3 (Panther) has the IP over Firewire built-in. Before that it was available as an extension. If you are not running 10.3 then update and try again.
Also just saw this nice tutorial about this. Have a look and make sure you have done all the required steps. Also have a look though the comments.
(\(\
(^.^)
(")")
*This is the cute bunny virus, please copy this into your sig so it can spread
in windows xp you just turn on internet connection sharing and bridge the 1394 and ethernet addresses. set up the IP of your windows machine as your gateway on your mac.
done.
I don't understand how is running a firewire line between two computers easier than running an RJ45 line? I'm guessing your RJ45 is already used up though receiving your internet connection? So get a simple hub. Case closed.
Try this
If nothing else works, try joining the Apple Developer connection. The link can be found here
A lot of posts have been of the form:
"Why are you using Firewire for networking? Buy a hub!"
A couple of points.
1. A lot of us have Firewire cables lying around but not hubs. Therefore, Firewire: $0. Switch: $25.
2. Firewire has the potential to be really fast. I know some of the third-party Firewire networking solutions for Mac used to sell well simply because they were 4x the speed of Ethernet -- which makes a big difference if you're transferring, say, massive TIFF proofs. (I personally have not gotten this working, see below.)
However:
1. It's a Mac. If you've got a free Ethernet port on another machine, you don't need a hub/switch. Macs detect crossover-vs.-normal UTP cables automatically.
2. Last I checked, the Firewire IP implementation in Panther wasn't terribly standard -- or, at least, I couldn't get any of my Linux or BSD boxes to recognize it. Might work with XP; should work with another Mac.
Now you just need to set up the internet sharing. Try using a proxy server ( analogx.com has a good free once for windows) on the machine that's directly into the ethernet drop, binding the proxy to the address you assigned to the Firewire connection (You did use a private IP, right?)
You've got IP over Firewire, you just need routing/proxying services. This seems to have mislead some people's responses.
I recognize people by their sigs. Is that a bad thing?
*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...
- 'OHCI-1394 support'
...ps, and maybe while you're at it, add 'SBP-2 support (Harddisks etc.)' too ...
- ieee1394
* and you might also want to check these out:so grab a supported/the patched kernel...,and don't don't forget to configure & compile it with these options:
'Ethernet over 1394
'Raw IEEE1394 I/O support'
(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....):
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... }:-)
I don't claim I know more than I know, and if you know you know more than I know, then by all means, let me know.
Point to point, yes. Using one of the machines as a router to the internet, the internet won't get any faster than that 10bT/100bT drop. Unless the original poster is dealing with enormous files (say video) the hassle involved in getting this to work is worth way more than the $25 or so to buy a blinkin switch.
7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
Firewire is far faster than 100 base T ethernet.
Photos.
I've had a setup similar to what the poster's looking for for quite some time now
The basics (under Panther, similar under Jaguar):
- XP *loves* to bridge all of your networking connections, and it treats firewire as one. Don't let it. Delete the bridging node if it's in your Net Connections panel.
- Use the Internet Connection Sharing wizard, and set it to share your ethernet over the 1394 connection (firewire in the civilized world).
- On the Mac, go to your network control panel (prefpane, whatever), Show --> Network Port Configurations
- Add a New --> Built-in Firewire connection
- Set it up for DHCP and you should be good to go. You might also disable your built in ethernet, airport and dialup ports for this configuration if you want an easier time debugging the connection.
The connection works great between my Shuttle box and my Powerbooks. Close to gigabit speeds for local filesharing, speeds you'd expect for 'Net sharing.
Once the price of gigabit hubs comes down, however, I'll probably never use this connection type again. If my rendering farm gets big enough to require that type of constant bandwidth, I'll probably go gigE or fiber.
First, make sure that both computers are linked by firewire, then, reboot the powerbook, holding down 'T' as it is starting up. It should give you the firewire logo on the screen, meaning that it is in FW disk mode. Then, simply use the powerbook as a firewire hard disk (SBP2).
I wrote my own experience with IP over 1394 some time ago, you can read it here. It's working just fine on my case, slightly better than FastEthernet with ~150Mbits/s practical transfer rates, but not quite as good as GigabitEthernet. If you have a couple of Macs with built-in GigabitEthernet, then you'll be better off plugging a crossover Ethernet cable (Cat6 for Gigabit) between them, configure IP, and enjoy even greater speed.
If you could ftp from one machine to the next over firewire, then IP is working. Sounds like you need to figure out how to setup a NAT or HTTP Proxy. You're barking up the wrong tree.
-molo
Using your sig line to advertise for friends is lame.
I figured I'd save everyone the trouble of writing their own question, and just post my template.
I was wondering, has anyone here done $COMMON TASK$ with $INAPPROPRIATE DEVICE$ ? If so, how well did it work ? What problems did you encounter ? I am aware of $APPROPRIATE DEVICE$ for $COMMON TASK$, but I really want to try $INAPPROPRIATE DEVICE$, because of $UNLIKELY TO BE REALIZED BENEFITS$. Thanks.
In Soviet America the banks rob you!
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.
... why, when doing it the straightforward way is so much simpler?
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
Glonoinha the MebiByte Slayer
This is great, but how can I put my linux box in firewire target mode?
No, really... how? This would be a *huge* benefit to us!
how do i set up a dial in acct on win98? i have dsl and want to dial in while out and access the web too