IP over Firewire

timk9 · 04-04-2006, 05:05 AM

I recently discovered networking via a Firewire cable and it's pretty nifty. If you don't know, this is natively supported by both WinXP and MacOS. I am using it to connect my WinXP Pro SP2 system and my MacOSX 10.4.5 system at 400Mbps. It works great when I hardcode the IP address and everything, but the catch is this: when I plug in the cable while both machines are on, it works. But if I [re]boot either computer when the cable is already plugged in, I have to unplug it and plug it back in.

Is there any way in software on either end to reinitialize the connection without reaching around to the cable?

Thanks!
Tim

timk9 · 04-04-2006, 09:32 PM

sorry folks, i should have posted in the Networking forum... mod please move or copy. thanks.

timk9 · 04-04-2006, 09:40 PM

Sorry for the triple post...

More information about the problem (rather, inconvenience): If I [re]boot the Windows machine, it maintains its static IP of 192.168.1.8 which I assigned. The Mac's static IP of 192.168.1.1 disappears, and 144.3.8.0 takes its place. Is this like Windows's "autoconfiguration" 169.254.x.x address?

Again when I unplug the cable and reseat it the Mac is the correct IP again. I haven't tried rebooting the Mac yet but I don't think it'll make any difference.

Any ideas? Thanks
Tim

johnwill · 04-06-2006, 03:06 PM

Why not just use Ethernet, it's designed from the ground up to be used for networking?

timk9 · 04-06-2006, 07:59 PM

Of course I could use ethernet, but that's too easy. :-) I like to tinker with unusual things, and there are plenty of reasons I want to use IPFW.

400Mbps FW sounds much better than 100Mbps ethernet (before gigabit devices existed). Second, the Mac is sharing the internet connection to the PC (in via ethernet, out via firewire) and I don't have a router. Third, 802.11g works with these machines but I have difficulty setting up encryption, so it's slower and less safe than a wired connection. Lastly, I have an unused FW port and just want to play with it.

Again I have the connection working just fine but was wondering if this cable inconvenience is common to other users of IPFW. But from reading other threads in this forum it seems like a pretty unpopular (or undiscovered) technology.

Tim

04-04-2006, 05:05 AM	#1 (permalink)
timk9 Registered User Join Date: Feb 2006 Location: Lockport, NY, USA Posts: 58 OS: XPPro, XPPro X64, 98, DOS, MacOSX, various Linuxes	IP over Firewire I recently discovered networking via a Firewire cable and it's pretty nifty. If you don't know, this is natively supported by both WinXP and MacOS. I am using it to connect my WinXP Pro SP2 system and my MacOSX 10.4.5 system at 400Mbps. It works great when I hardcode the IP address and everything, but the catch is this: when I plug in the cable while both machines are on, it works. But if I [re]boot either computer when the cable is already plugged in, I have to unplug it and plug it back in. Is there any way in software on either end to reinitialize the connection without reaching around to the cable? Thanks! Tim

04-06-2006, 03:06 PM	#4 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 32,567 OS: XP-Pro, Vista, Linux Blog Entries: 1	Why not just use Ethernet, it's designed from the ground up to be used for networking? __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

04-04-2006, 09:32 PM	#2 (permalink)
timk9 Registered User Join Date: Feb 2006 Location: Lockport, NY, USA Posts: 58 OS: XPPro, XPPro X64, 98, DOS, MacOSX, various Linuxes	sorry folks, i should have posted in the Networking forum... mod please move or copy. thanks.

04-04-2006, 09:40 PM	#3 (permalink)
timk9 Registered User Join Date: Feb 2006 Location: Lockport, NY, USA Posts: 58 OS: XPPro, XPPro X64, 98, DOS, MacOSX, various Linuxes	Sorry for the triple post... More information about the problem (rather, inconvenience): If I [re]boot the Windows machine, it maintains its static IP of 192.168.1.8 which I assigned. The Mac's static IP of 192.168.1.1 disappears, and 144.3.8.0 takes its place. Is this like Windows's "autoconfiguration" 169.254.x.x address? Again when I unplug the cable and reseat it the Mac is the correct IP again. I haven't tried rebooting the Mac yet but I don't think it'll make any difference. Any ideas? Thanks Tim

04-06-2006, 07:59 PM	#5 (permalink)
timk9 Registered User Join Date: Feb 2006 Location: Lockport, NY, USA Posts: 58 OS: XPPro, XPPro X64, 98, DOS, MacOSX, various Linuxes	Of course I could use ethernet, but that's too easy. :-) I like to tinker with unusual things, and there are plenty of reasons I want to use IPFW. 400Mbps FW sounds much better than 100Mbps ethernet (before gigabit devices existed). Second, the Mac is sharing the internet connection to the PC (in via ethernet, out via firewire) and I don't have a router. Third, 802.11g works with these machines but I have difficulty setting up encryption, so it's slower and less safe than a wired connection. Lastly, I have an unused FW port and just want to play with it. Again I have the connection working just fine but was wondering if this cable inconvenience is common to other users of IPFW. But from reading other threads in this forum it seems like a pretty unpopular (or undiscovered) technology. Tim