[arm-allstar] lots of log entries

[David McGough]

Hi John,

Interesting. Yes, turning IPv6 "off" entirely is probably a good idea; we
might want to add that to the network setup scripts since IPv6 does
nothing for us at this point except add confusion.

In this case, there would still be errors, however--both nodes2 and nodes4
were off-line. I see that nodes2 is still off-line now. And, note that
"dig"  doesn't report that any of these URL's have AAAA records
advertised.


Thanks for the feedback-

73, David KB4FXC




On Mon, 17 Jul 2017, John Hoser-Smith wrote:

> Dave - I "solved the problem" a different way...
> On all my Allstar Nodes - I have disabled any/all reference to IPv6 
being used - for both the Ethernet (Eth0) and Wireless (Wan0) Interfaces 
on the RPi3.So for my nodes now (only) IPv4 is used and I don't have to 
worry about what gets registered at Allstar Servers nor what (IPv6) gets 
entered into the local log file.I can pass back the instructions to 
disable IPv6 if you're interested.  Yes my Comcast Business Class (cable 
modem - DOCSIS v3.0) hands out IPv6 addresses as a default.
> 73s  N0ECT
>  
> 
>     On Monday, July 17, 2017 12:02 AM, David McGough via arm-allstar <arm-allstar at hamvoip.org> wrote:
>  
> 
>  
> Hi Dave,
> 
> If you're running a completely private system, you can eliminate these log 
> messages by commenting out the rc.updatenodelist script. This script is 
> launched from the /usr/local/etc/rc.allstar script, at startup, on (or 
> about) line 68.
> 
> Change:
> 
> # get node to IP database
> /usr/local/etc/rc.updatenodelist &
> 
> To:
> 
> # get node to IP database
> #/usr/local/etc/rc.updatenodelist &
> 
> 
> ...Then save the file and restart the RPi3, or simply kill the
> rc.updatenodelist script from the root shell prompt (menu option #9) like:
> 
> killall rc.updatenodelist
> 
> 
> 73, David KB4FXC
> 
> 
> On Sun, 16 Jul 2017, "mail via arm-allstar" wrote:
> 
> > I have two private nodes on an RPi3 server running V1.5.  One of the 
> > nodes is a pseudo node with Echolink enabled, the other has a repeater 
> > connected.  When I use Supermon to look at the Linux log I see large 
> > volumes (several per second) of things like:
> > 
> > network unreachable resolving 'nodes4.allstarlink.org/A/IN': 2604:a880:cad:d0::137:b001#53
> > 
> > network unreachable resolving 'nodes4.allstarlink.org/AAAA/IN': 
> > 2604:a880:cad:d0::137:b001#53
> > 
> > network unreachable resolving 'nodes2.allstarlink.org/AAAA/IN': 2604:a880:800:10::47e:8001#53
> > 
> > I thought I had commented out the lines in rpt.conf and iax.conf that 
> > were reporting to allstarlink.org but apparently not.  I would like to 
> > fix the problem or stop the log entries.
> > -Dave k6dvd
> > 
> > _______________________________________________
> > 
> > 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
> 
> 
>