From owner-freebsd-hackers Sun Aug 27 08:34:33 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id IAA25300 for hackers-outgoing; Sun, 27 Aug 1995 08:34:33 -0700 Received: from virgo.ai.net (virgo.ai.net [198.69.44.2]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id IAA25290 for ; Sun, 27 Aug 1995 08:34:30 -0700 Received: from aries.ai.net (aries.ai.net [198.69.44.1]) by virgo.ai.net (8.6.11/8.6.12) with ESMTP id LAA11195 for ; Sun, 27 Aug 1995 11:50:21 -0400 Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id LAA20180; Sun, 27 Aug 1995 11:34:21 -0400 Date: Sun, 27 Aug 1995 11:34:21 -0400 (EDT) From: Network Coordinator To: hackers@freebsd.org Subject: Networking [not completely FreeBSD related] Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@freebsd.org Precedence: bulk This question isn't completely FreeBSD related, but I have been told its impossible, so I figure I could use FreeBSD to solve it. :-) A standard T-1 connection, long before the internet was popularized, was just a datapipe between two points. No packets, no IP addresses, no nothing. Particularly in the voice-multiplexing area. Nowadays, T-1 connections are used very differently. Can anyone think of a way, or know of an existing solution, that can somehow emulate an old T-1 style datapipe on an IP network. Most likely this would be ether. I would really prefer a solution that didn't involve any heavy digitization for a video or a voice stream, just something like connecting a TSU to a V.35 jack connected to a FreeBSD machine, run something on it, route it across the network, and have a similar machine reconstitute the original input. Its bizarre, I know. If you have any ideas, I would REALLY appreciate anything. Thanks, -Jerry.