[App_rpt-users] Connection issues with new ASL hub

[Russell Thomas]

per the instructions, I did not create this node on a separate server on
Allstar Link. can it be moved or have it deleted and start over?


On Wed, Nov 7, 2018 at 6:45 PM Russell Thomas <russell at kv4s.com> wrote:

> Thanks all!
> I think NAT is the problem as well. I'll work on it next time I'm by the
> computer!
>
> Many thanks!
>
> On Wed, Nov 7, 2018, 5:17 PM David Shaw <shawpbx at gmail.com wrote:
>
>> Check out of document
>>
>>
>> https://docs.google.com/document/d/1Dz0zD12RJKeFkmfuDM9fhQj88C84JeygfLygR8VniFI/edit?usp=sharing
>>
>>
>> --
>> Thanks, David
>>
>> "Laws that forbid the carrying of arms...disarm only those who are
>> neither inclined nor determined to commit crimes. Such laws make things
>> worse for the assaulted and better for the assailants; they serve rather to
>> encourage than prevent homicides, for an unarmed man may be attacked with
>> greater confidence than an armed one."
>> Thomas Jefferson
>>
>>
>> On Wed, Nov 7, 2018 at 1:24 PM Bryan Fields <Bryan at bryanfields.net>
>> wrote:
>>
>>> On 11/7/18 4:09 PM, Bryan Fields wrote:
>>> > Ok, how is your node connected?  Is there a NAT device in the way
>>> between your
>>> > node and 174.85.220.36?
>>>
>>> eureka! NAT bs is present :(
>>>
>>> root at Itchy:~# grep 174.85.220.36 /var/lib/asterisk/rpt_extnodes
>>> 47923=radio at 174.85.220.36:4569/47923,174.85.220.36
>>> 49308=radio at 174.85.220.36:4569/49308,174.85.220.36
>>>
>>> They a passing from different ports for IAX on the registration servers
>>> as well.
>>>
>>> You have two nodes behind the same IP, and they are identifying on the
>>> same
>>> port, so the NAT device at 174.85.220.36 won't be able to direct them to
>>> the
>>> proper internal address if they are not on different ports.
>>>
>>> What I would do is configure a nat rule to forward udp
>>> 174.85.220.36:4570 to
>>> <Internal-IP-49308>:4569 and configure the port for the server 49308 is
>>> on to
>>> 4570 in the portal.
>>>
>>> This way when people connect to 47923, it goes to 174.85.220.36:4569
>>> and 49308
>>> will go to 174.85.220.36:4570.
>>>
>>> If you want 47923 and 49308 you'll need to configure them in rpt.conf,
>>> since
>>> they will be behind your NAT device, and using direct connections.
>>>
>>> [nodes]
>>> 49308 = radio@<Internal-IP-49308>:4569/49308,NONE
>>>
>>> Give this a try and report back.
>>>
>>> --
>>> Bryan Fields
>>>
>>> 727-409-1194 - Voice
>>> http://bryanfields.net
>>> _______________________________________________
>>> App_rpt-users mailing list
>>> App_rpt-users at lists.allstarlink.org
>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>>>
>>> To unsubscribe from this list please visit
>>> http://lists.allstarlink.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.
>>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at lists.allstarlink.org
>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
>> To unsubscribe from this list please visit
>> http://lists.allstarlink.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://lists.keekles.org/pipermail/app_rpt-users/attachments/20181108/b8f309db/attachment.html>