[App_rpt-users] App_rpt-users Digest, Vol 84, Issue 17
Jim Aspinwall
no1pc at yahoo.com
Mon Feb 15 20:52:50 UTC 2016
Excellent - thanks. BW and hardware won't be an issue where I think this would go.
Today's Topics:
1. Hub vs Node? (Jim Aspinwall)
2. Re: Hub vs Node? (Steve Zingman)
3. Re: Hub vs Node? (Kevin Custer)
----------------------------------------------------------------------
Message: 1
Date: Sun, 14 Feb 2016 22:24:49 +0000 (UTC)
From: Jim Aspinwall <no1pc at yahoo.com>
To: "app_rpt-users at ohnosec.org" <app_rpt-users at ohnosec.org>
Subject: [App_rpt-users] Hub vs Node?
Message-ID:
<1373181799.4087456.1455488689812.JavaMail.yahoo at mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"
What if anything are the specific differences between a single node (tied to simplex, repeater, Pi box and headset...) that can presumably only accept one in-bound call/connect, and a hub, to which many can connect and bridge through/over?
Given a certain amount of specialization or purpose/interest-built hubs I am interested in having a purpose-built hub for a few systems and users not exclusive but so as not to impose on others' hubs and traffic.
What does it take to do this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20160214/3423844a/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 15 Feb 2016 09:54:44 -0500
From: Steve Zingman <szingman at msgstor.com>
To: app_rpt-users at ohnosec.org
Subject: Re: [App_rpt-users] Hub vs Node?
Message-ID: <56C1E6B4.1010300 at msgstor.com>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Jim,
Any node can be a "HUB" A node is not limited to one connection. There
may be hardware limitation about the number of connections a given piece
of hardware and internet connection can support. Typically, a HUB is
located on a higher bandwidth internet connection and is running a more
"stout" piece of hardware. A HUB usually does not have a node radio
connected to it, but there is no reason it can't. A HUB usually runs
DAHDI/pseudo for it's rxchannel.
As a example HUB 2100 is running on a decent internet connection and
decent hardware. We are running the beta test of the DMR <---> AllStar
gateway on it so it has a NW Digital DV3000 connected and is using
chan_usrp instead of pseudo for it's rxchannel.
Hope this helps.
73, Steve N4IRS
On 2/14/2016 5:24 PM, Jim Aspinwall wrote:
> What if anything are the specific differences between a single node
> (tied to simplex, repeater, Pi box and headset...) that can presumably
> only accept one in-bound call/connect, and a hub, to which many can
> connect and bridge through/over?
>
> Given a certain amount of specialization or purpose/interest-built
> hubs I am interested in having a purpose-built hub for a few systems
> and users not exclusive but so as not to impose on others' hubs and
> traffic.
>
> What does it take to do this?
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20160215/13f59dc5/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 15 Feb 2016 11:04:26 -0500
From: Kevin Custer <kuggie at kuggie.com>
To: app_rpt-users at ohnosec.org, arm-app_rpt at yahoogroups.com
Subject: Re: [App_rpt-users] Hub vs Node?
Message-ID: <56C1F70A.4070805 at kuggie.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
This is now answered in the DIAL FAQ:
http://docs.allstarlink.org/drupal/node/170
Kevin
On 2/15/2016 9:54 AM, Steve Zingman wrote:
> Jim,
> Any node can be a "HUB" A node is not limited to one connection. There
> may be hardware limitation about the number of connections a given
> piece of hardware and internet connection can support. Typically, a
> HUB is located on a higher bandwidth internet connection and is
> running a more "stout" piece of hardware. A HUB usually does not have
> a node radio connected to it, but there is no reason it can't. A HUB
> usually runs DAHDI/pseudo for it's rxchannel.
>
> As a example HUB 2100 is running on a decent internet connection and
> decent hardware. We are running the beta test of the DMR <---> AllStar
> gateway on it so it has a NW Digital DV3000 connected and is using
> chan_usrp instead of pseudo for it's rxchannel.
>
> Hope this helps.
>
> 73, Steve N4IRS
>
> On 2/14/2016 5:24 PM, Jim Aspinwall wrote:
>> What if anything are the specific differences between a single node
>> (tied to simplex, repeater, Pi box and headset...) that can
>> presumably only accept one in-bound call/connect, and a hub, to which
>> many can connect and bridge through/over?
>>
>> Given a certain amount of specialization or purpose/interest-built
>> hubs I am interested in having a purpose-built hub for a few systems
>> and users not exclusive but so as not to impose on others' hubs and
>> traffic.
>>
>> What does it take to do this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20160215/c10bff2a/attachment-0001.html>
------------------------------
_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
End of App_rpt-users Digest, Vol 84, Issue 17
*********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20160215/a4c84644/attachment.html>
More information about the App_rpt-users
mailing list