From owner-freebsd-current Wed Mar 5 6:27:15 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2575F37B401 for ; Wed, 5 Mar 2003 06:27:13 -0800 (PST) Received: from www.outpostsentinel.com (66-23-198-138.clients.speedfactory.net [66.23.198.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19DC343FBD for ; Wed, 5 Mar 2003 06:27:12 -0800 (PST) (envelope-from cfowler@outpostsentinel.com) Received: from [192.168.2.8] ([192.168.2.8]) by www.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id h25ER1F08195; Wed, 5 Mar 2003 09:27:01 -0500 Subject: Re: IP over IEEE1394? From: Christopher Fowler To: David Leimbach Cc: freebsd-current@freebsd.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 05 Mar 2003 09:30:58 -0500 Message-Id: <1046874658.5666.27.camel@cfowler.outpostsentinel.com> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The beauty of ppp is that you have support in the kernel to do it. Else, you are stuck to writing some type of interface driver for the kernel. In the short term, this may not be a workable solution. On a side note, I read an article on /. about using firewire + MinDV for backup. I guess I can get some use out of my camera after all. Chris On Wed, 2003-03-05 at 09:21, David Leimbach wrote: > Yeah... point to point connections are interesting and powerful but IP > would > be better if we could get it. > > I wish I knew more about how to implement it. :) > > Dave > On Wednesday, March 5, 2003, at 08:23 AM, Christopher Fowler wrote: > > > This may not be a workable solution, but if you can get 2 programs to > > send data across the firewire to one another, you could use pppd > > through > > that tunnel. > > > > > > On Wed, 2003-03-05 at 08:25, David Leimbach wrote: > >> Interesting... I didn't even know we had Ethernet over firewire :). > >> > >> Mac OS X and Windows XP both have IP over firewire either working or > >> in the works and somewhat usable. The only one I can claim any > >> experience > >> with is Mac OS X. It's somewhat flaky though and you get unreliable > >> spikes > >> in some basic performance tests I have done with it. > >> > >> It would be a really interesting value added feature for FreeBSD 5.x > >> and could potentially open FBSD up even more to the "cluster" market > >> which is somewhere its not as proliferated as linux. > >> > >> With the advent of firewire2 on the horizon it may be even more > >> impressive. > >> > >> I believe there is even an Oracle product for linux which can cluster > >> databases > >> over firewire now. [I don't know if its IP though] > >> > >> > >> Dave > >> On Wednesday, March 5, 2003, at 01:43 AM, Rossam Souza Silva wrote: > >> > >>> > >>> Hi, there is some plan to port NetBSD's implementation of IP over > >>> Firewire? I know, we have "Ethernet over Firewire", but like the > >>> Linux > >>> one, isn't a standard... > >>> > >>> Just curious. > >>> > >>> --------------------------------------------------------------------- > >>> -- > >>> ------- > >>> (_ ) "Contrary to popular belief, UNIX is user friendly. It > >>> just > >>> happens > >>> \\\'',) ^ to be very selective about who it decides to make friends > >>> with." > >>> \/ \( > >>> .\._/_) Rossam Souza Silva (rss@cin.ufpe.br) > >>> --------------------------------------------------------------------- > >>> -- > >>> ------ > >>> > >>> > >>> To Unsubscribe: send mail to majordomo@FreeBSD.org > >>> with "unsubscribe freebsd-current" in the body of the message > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-current" in the body of the message > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message