On Wed, 2017-04-05 at 10:07 -0700, jim stephens wrote:

Use teamviewer on a system at each end.  There are other services  possibly as well.

Teamviewer is a desktop share utility.  It has a central server in the  concept of how it works rendering the only needed thing to be a working system to  connect in any way at each end.

If you can post email, and SSH from that system to the system with the  problem by IP address, perhaps that would work.

This jumps the NAT problem.

Thanks Jim

On 4/5/2017 7:53 AM, Paul Simmons wrote:

...

On Wed, 2017-04-05 at 10:09 +0100, Michael Tremer wrote:

...

Hi,

thank you.

Can we maybe arrange a session where I log in from remote to your system and see what I can find?

So far I don't have many ideas.

Would this be possible? Where in the world are you even?

Best, -Michael

On Mon, 2017-04-03 at 15:35 -0500, Paul Simmons wrote:

...

Michael, I forgot to tell you that I'm willing and able to test script changes (such as the unbound init) or substitute executables on the test system.

Thnks, Paul

Hello, Michael.

Oh, how I wish!  Unfortunately, I'm NATed and the ISP doesn't allow "local servers".  Also, without working DNS, I'm unsure of how to connect.  I'm in a rural area of West Texas, with "challenging" terrain.  I'm hoping a nearby (~10km distant) fiber provider will build a NLOS WISP in a year or two; they are interested, but not ready to commit.

Perhaps we should take this discussion out of the devel list for now?

I appreciate your attention, and realize you have a lot of others to support.  I notice core110 is in testing.  I'll try some changes locally, based on that release.  I'll poke around in the unbound init.d and get some better info.

I'll report any findings in another thread.

Best, Paul

Thank you for your reply, Jim.

I think it'll be less effort to work through this myself.

I already have enough complications with my so-called ISP without adding proprietary software into the mix.

Thank you for the suggestion, though.

Paul