[App_rpt-users] BIG registration problem this morning

[Tim Sawyer]

I'm partially responsible for this change. I want to make the AllStar
portal as simple to use as possible. It seemed to me that not having to put
the IAX port in the portal would make life easier. I forget to do that when
I move or setup new servers as have many others. When I discovered Asterisk
is reporting the actual source port to the portal database I thought it
would make sense to use that port for the nodes list.

On Mon, Aug 13, 2018 at 3:48 AM Paul - KN2R <paulkn2r at gmail.com> wrote:

> Tim,
>
>
>
> I am for putting the previous Registration server back in operation!
>
>
>
> All my nodes are having problems registering with different port numbers I
> do not have configured anywhere.
>
> I use a commercial grade SonicWall TZ-205N firewall/router which has been
> working fine for years!
>
> No changes have been made to that server or the router in over a year or
> two.  Now all of a sudden, since the change, all is *not* working.
>
>
>
> Paul / KN2R
>
>
>
>
>
> *From:* App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org]
> *On Behalf Of *Tim Sawyer
> *Sent:* Monday, August 13, 2018 1:15 AM
> *To:* Users of Asterisk app_rpt
> *Subject:* Re: [App_rpt-users] BIG registration problem this morning
>
>
>
> Why do some nodes not have this problem? Is NAT somehow different from
> different routers? I'd really like to understand so I can take it back to
> the technical folks and explain why it needs to be put back the way it was.
>
>
>
> On Sun, Aug 12, 2018 at 8:06 PM Danny K5CG <k5cg at hamoperator.org> wrote:
>
> I'm running pfSense and I "could" setup a static port for the outbound NAT
> but since when does the source port ever match the destination port, for
> any protocol? I'm not touching it.
>
> 46679*CLI> iax2 show registry
> Host                  dnsmgr  Username        Perceived
>  Refresh  State
> 44.98.254.145:4569    Y       46679           47.187.195.172:29961
>  60  Auth. Sent
>
> 4569 is what's set on the portal for my node. 29961 appears to be what is
> recorded on the server from my registration.
>
> The portal port needs to be used or there has to be a way to set the port
> in rpt.conf to have that communicated to the registration server. Relying
> on the source port (which can be anything) is not a good idea.
>
> Next steps?
>
> Danny
> K5CG
> _______________________________________________
> 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.
>
>
>
>
> --
>
> Tim WD6AWP
> _______________________________________________
> 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.
>


-- 
Tim WD6AWP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20180813/60108991/attachment.html>