Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Jan 2012 14:21:55 +1100
From:      Jan Mikkelsen <janm-freebsd-hackers@transactionware.com>
To:        Julian Elischer <julian@freebsd.org>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Hardware supported by ng_frame_relay?
Message-ID:  <351D0C9B-AD02-4B1E-BA94-B3EBF2562C65@transactionware.com>
In-Reply-To: <4F139ABD.8070801@freebsd.org>
References:  <FC3D394D-46D6-4183-B9D1-BC975D40362C@transactionware.com> <4F139ABD.8070801@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help


On 16/01/2012, at 2:34 PM, Julian Elischer wrote:

> On 1/13/12 11:00 PM, Jan Mikkelsen wrote:
>> Hi,
>> 
>> I'm looking to upgrade a system running frame relay over a Sangoma A101 card and WANPIPE.
>> 
>> Sangoma do not support FreeBSD anymore, so I'm looking for alternatives.
>> 
>> What hardware does ng_frame_relay support now that ar(4) and sr(4) are not in FreeBSD 9?
>> 
>> Specifically, will ng_frame_relay work with a Digium TE121 and ports/dahdi-kmod?
>> 
>> Any suggestions welcome, G.703, X.21 or V.35 interfaces OK.
> 
> Unfortunately, with the advent of Ethernet connected internet feeds (e.g. dsl, cable etc),
> plain synchronous interfaces have become almost irrelevant for most of the developers.
> If you can find a card that "would have" been usable with  the ar or sr
> drivers and you have one for testing, we could possibly resurrect it with your help,
> but none of the current developers have such a card.. (that I know of).

Thanks. For now I'm going with a standalone router. This is a single link for a communicating with a legacy application at a government body, so I'm not looking to invest significant amounts of time.

I was curious about about what was involved in hooking ng_frame_relay up to one of the E1 based telephone cards to do frame relay. Perhaps if I get one of the cards for another purpose I'll have a look.

Regards,

Jan.


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?351D0C9B-AD02-4B1E-BA94-B3EBF2562C65>