[arm-allstar] Local DNS Server on Allstar R-Pi not answering 127.0.0.1

[John Huggins]

On Sun, Jul 9, 2017 at 3:23 PM, "Doug Crompton via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> John,
>
>  Also in looking at that closer - what did you do to cause that error? Did
> you try to connect to yourself?


I attempted to connect to W4VA-R (8837691) from KX4O using Echolink on a
Win7 box on the same network as the R-Pi. We are still in a test
environment so this won't be the final solution, but for now both are on
the same internal network.


> The 192.168.1.1 address is strange as that
> address is usually a router base address on a LAN.
>

As it is for me as well. The .1 router has the appropriate port mappings
from the external IP to the internal Echolink and Allstar ports on an
internal 192.168.1.73 static IP.  Both Echolink and Allstar seem to almost
connect, but I am still too much in the newbie stage to enlist connect
volunteers from the outside in a meaningful way, but that is sounding more
and more like something to try.  Echolink throws the RDNS error and Allstar
fails for some permissions thing (but that's still progress).

My guess is the Allstar/Echolink code on the .73 R-Pi sees activity coming
in through my router and wants to know what 192.168.1.1 resolves to in some
sort of effort to authenticate by host perhaps.

Baby steps.  Thanks for your quick replies.

John, kx4o




>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
> On Sun, Jul 9, 2017 at 2:46 PM, "John Huggins via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > All,
> >
> > I have made solid progress setting up the latest Allstar boot image for a
> > R-Pi 2. The unit responds to Echolink connection requests, but the
> > /var/log/asterisk/messages file throws this during the connect attempt...
> >
> >
> >
> >
> > *[Jul  9 14:25:34] ERROR[407] chan_echolink.c: Cannot find DB entry for
> IP
> > addr 192.168.1.1[Jul  9 14:25:34] ERROR[407] chan_echolink.c: Cannot find
> > DB entry for IP addr 192.168.1.1[Jul  9 14:25:40] ERROR[407]
> > chan_echolink.c: Cannot find DB entry for IP addr 192.168.1.1[Jul  9
> > 14:25:40] ERROR[407] chan_echolink.c: Cannot find DB entry for IP addr
> > 192.168.1.1*
> >
> > ...with the Echolink program eventually saying "*Cannot Connect to
> 'call' -
> > UN-AUTHORIZED*."
> >
> > I assume the allstar program suite seeks to perform a reverse lookup on
> my
> > local gateway.
> >
> > I see the boot image sets up the usual BIND server for use as a DNS
> lookup
> > caching server and is setup to also answer reverse lookups for 127.0.0.1
> ->
> > localhost. as well - pretty routine stuff for a caching BIND instance.
> > Resolve.conf is set to point to 127.0.0.1 for lookups. This works fine
> for
> > external hostname resolving, but BIND won't answer for the 127.0.0.1
> > lookup.  I later added a zone for 192.168.1.x (routine stuff) to this
> DNS,
> > but it also doesn't answer requests for local IP address lookups.
> >
> > I do know the local named instance is using this file because I can
> > certainly break it with a typo in /etc/named.conf.
> >
> > Can anyone else successfully resolve 127.0.0.1 on their local copy of the
> > Allstar environment?
> >
> > Taking it back one more step, does echolink really need to know the
> > hostname of my gateway?
> >
> > Thanks for any enlightenment.
> >
> > 73
> > John, kx4o
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> >
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>