[App_rpt-users] Can you connect to a node just on the lan? (multihome? how?)

[Steve Gladden]

Thanks Paul!

Very helpful! I'd like to add this to the standard documentation
exactly as you put it if possible..
Unless nobody else really does this :-)..
This is great.. I can continue testing now without annoying anyone
else's live nodes with my rigorous testing now. :-)

+ I might link two nodes over a wireless LAN in Dayton this weekend!


Steve









> Yes this is how my hub and node are configured.
>
> #1:  Ensure that both nodes see their internal address in the node stanza
> as indicated below.
>
> Radio 1: 27084 = radio at 10.15.0.249/27084,NONE
> Radio 2: 2598 = radio at 10.15.0.250/2598,NONE
>
> #2:  For good measure so you can connect with each other, insure that you
> have a peer entry in the iax.conf file for both nodes' internal addresses.
>
> Radio 1:
> [WINSLink-HI]
> type=peer
> host=10.15.0.250
> secret=xxxxx
> auth=md5
> disallow=all
> allow=ulaw
> allow=alaw
> transfer=no
>
> Radio 2:
> [vmAsterisk]
> type=peer
> host=10.15.0.249
> secret=xxxxxx
> auth=md5
> disallow=all
> allow=ulaw
> allow=alaw
> transfer=no
>
> The entry into each node stanza on the 'rpt.conf' file will override the
> public database that is being updated from the allstar server while, still
> allowing outside connections based on your public IP address if you are
> connected to the internet.
>
> _______________________________
> Paul J. Agamata
> Sysman at Xceptions.COM
> Hilo, Hawaii
>
> [cid:3356425690_4952136]
>
>
> ________________________________
> From: Steve Gladden <steve at michiganbroadband.com>
> Date: Tue, 11 May 2010 11:57:59 -1000
> To: Steve Gladden <stevegladden at michiganbroadband.com>
> Cc: <app_rpt-users at qrvc.com>
> Subject: Re: [App_rpt-users] Can you connect to a node just on the lan?
> (multihome? how?)
>
>
>
>> On Sat, 8 May 2010, Steve Gladden wrote:
>>
>>> I've got two nodes:
>>>
>>> 2586 and 27036
>>>
>>> Both sit on the same LAN.
>>>
>>> Is it possible to connect one to the other (link) them
>>> over the LAN while they are still reachable from the
>>> Internet via ALLSTAR public node list
>>>
>>> You can see my attempt below that is failing across the LAN.
>>> I don't know if it is failing because the same node number
>>> is also in the public IP/ public nodelist.
>>>
>>> Is there a way to 'locally' override the public node list
>>> so it's number is reachable 'locally' via lan or VPN?
>>>
>>> Or do local type nodes need to not also register with ALLSTAR LINK?
>>>
>>> In this example I'm trying to make outbound link to node
>>> 2586 which is at 10.73.73.9 internally..
>>>
>>> Back on node 27036 in it's config I of course am pointing
>>> back to 2586 at it's internal IP (not shown here).
>>> Thanks! -Steve
>>>
>>>
>>> 27036 = radio at 127.0.0.1/27036,NONE      ; This must be changed to your
>>> node number
>>>
>>> 2586 = radio at 10.73.73.9/2586,NONE
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Michigan Broadband Systems Inc.
>>> "Always Connected"
>>>
>>> (734)527-7150
>>>
>>> Steve's cellphone: (734)904-1811
>>>
>>>
>>>
>> BUMP: Please & Thank You..
>>
>> I'd like to link my two nodes over the local network and have almost
>> got it but not quite...
>> Am I missing a step or concept here?
>>
>> Can I multihome an Internet registered node locally? as you see me
>> attempting above?
>>
>> Or can a node have two simultaneous identities? one for the LAN
>> and another for registering with Allstar Link?
>>
>> -Steve
>
> Anyone ever done this?
> I'm trying to get it working for Dayton if possible.
> -Steve
>
>
>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>


Michigan Broadband Systems Inc.
"Always Connected"

(734)527-7150

Steve's cellphone: (734)904-1811


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.