Originally posted by Gon
When I tried using firewire to share a connection for a week or so, it was a real pain in the ass, I had to restart network sharing all the time to get it to work.
Sure it's nice to have the feature, but seems it needs a little further work.
Like I said... tunneling TCP/IP over FireWire sucks... both protocols have connection monitoring built into them, and it winds up that they fight a lot when anything goes wrong. Then there is the fact that FireWire is optimized for large chunks of data, and TCP/IP is best at sending streams of small chiunks. This problem is not limited at all to Apple's implementation, but is a general thing. It is just a bad idea.
To fix the problem you would really have to bridge/tunnel the data across FireWire (probably with some sort of trick-cache system like satellite network providers use), and this would require something proprietary (as there is no standard for this), and it would have to be at both ends. But this is really not worth anyone doing as current FireWire (over anything but fiber) tops out at 800Mbits/sec but Gigbit ethernet (theoretically) tops out at 1000Mbits/sec, and that is bi-directional (the FireWire number is aggregate), and the price difference is not usually worth talking about.
Now don't confuse this with saying there is no place for FireWire, those same protocols that make TCP/IP suck over FireWire also make it the best protocol out there for working with disk drives and other large-data-streaming systems. It just has no real place as a network carrier. I like that Apple has provided a basic setup, as it is nice for emergencies, but any more money spent in this area would just be a waste of resources that could better be used elsewhere.