[arm-allstar] registration woes

[R Dahl]

Thanks for the suggestions Roger and Doug. All good

The confusion is because my lan has access to 3 gateways with public ip's
which are managed by 2 mikrotik routers, one of which is at one of the
(rtcm)repeater sites 30 miles away via wifi.  The multiple gateways(natted)
are handy for providing alternate methods to access the lan externally as
well as allowing different devices to use whichever as defined with routing
marks.  And yes, there is only one dhcp server.  The whole arrangement
works very well until asterisk is in the mix.

Curiously, I can do a traceroute from either server(2 rpi's) to the
registration server, and the proper gw's and ip's are used,  however
monitoring a friends node log shows connection requests as coming from one
of the others.  A year or two back, Tim Sawyer had suggested a mikrotik
specific fix for all this and it worked gloriously until recently when I
must have changed something I cant find.

I dont mean to belabour the list with mikrotik quirks so I am going to turn
off the redundant gateways and live with just one until I figure it out.
Might be arp related??



On Thu, Feb 9, 2017 at 11:52 AM, R Dahl <ve6ars at gmail.com> wrote:

> I have two V1.5 servers on my lan
> In iax.conf's they have:
>
>
> for node 44203
>
> [general]
> bindport=4571
>
> and for node 40526
>
> [general]
> bindport=4569
>
> per lsnodes, they are both registered per below:
>
> 67.215.233.178:4569 44203 Registered
>
> 67.215.233.178:4569 40526 Registered
>
> They both appear as port 4569 even though the allstarlink server has been
> adjusted for ve6dok to port 4571.  Server network configs per:
>
> ve6dok
> 4571
> DHCP
>
> ve6aah
> 4569
> DHCP
>
> Yet 44203, which is a node of ve6dok, comes back as 4569
> 44203 can not make connections outside of the lan while 40526 can
>
> Thanks de Ross ve6ars
>
>
>
>
>
>