mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question on HDLC and raw access to T1/E1 serial streams.
Date: Sat, 30 Sep 2006 19:34:33 +0200	[thread overview]
Message-ID: <m3mz8hntqu.fsf@defiant.localdomain> (raw)
In-Reply-To: <451DC75E.4070403@candelatech.com> (Ben Greear's message of "Fri, 29 Sep 2006 18:24:46 -0700")

Ben Greear <greearb@candelatech.com> writes:

> I am looking for a way to bridge a T1/E1 network by reading a raw
> bitstream from one T1 interface and writing it out to the other.  The
> application is adding delay and/or bit corruptions for impairment
> testing.
>
> I have been using Sangoma's drivers and NICs, but I'm having no luck
> getting their latest stuff to work so I was hoping to use in-kernel
> drivers (even if that means writing or hiring someone to write new ones.)
>
> Is there currently a way to read/write the raw bitstream for a full T1
> or E1 or a subset of channels?

Well, my generic HDLC works with HDLC framing only, T1/E1 is
a layer lower than that... I think Cyclades have (had?) a version
of PC300 card with T1/E1 interface. It at least doesn't require
any "binary blobs", though I think the driver would need some work.

Which line interface do you need? G.703?
Do you need to bridge multiple streams (not slots) over one
interface (internal (de)multiplexer - I mean "more than one
subset of channels")?
-- 
Krzysztof Halasa

  reply	other threads:[~2006-09-30 17:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30  1:24 Ben Greear
2006-09-30 17:34 ` Krzysztof Halasa [this message]
2006-09-30 22:02   ` Ben Greear
2006-10-01 11:54     ` Krzysztof Halasa
2006-10-01 18:41       ` Ben Greear
2006-10-01 20:46         ` Alan Cox
2006-10-04  4:27           ` Ben Greear
2006-10-04 14:20             ` Lennart Sorensen
2006-10-04 18:03               ` Ben Greear
2006-10-01 22:09         ` Krzysztof Halasa
2006-10-02 16:29           ` Ben Greear
2006-10-03 16:08             ` Krzysztof Halasa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3mz8hntqu.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®