From owner-freebsd-hackers Wed Oct 7 08:37:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13040 for freebsd-hackers-outgoing; Wed, 7 Oct 1998 08:37:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13025 for ; Wed, 7 Oct 1998 08:37:37 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00429; Wed, 7 Oct 1998 08:41:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810071541.IAA00429@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andre Albsmeier cc: hackers@FreeBSD.ORG Subject: Re: How to send data between two network cards directly? In-reply-to: Your message of "Wed, 07 Oct 1998 16:58:06 +0200." <199810071458.QAA01398@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 08:41:08 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have two machines connected with two network cards directly > together via 10Base2. I would like to send data from one > machine two the other without doing IP or any other > protocol. You have to have some protocol, or you can't tell what any given item of data is. > What functions in FreeBSD could be used for that without > hacking around in the kernel or the network drivers? > > Is there something like a low-level-open or some ioctl > or anything similar? >From the opposite direction - why do you want to do this? There's a perfectly functional solution already available that doesn't involve reinventing the wheel. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message