public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Paul Simmons <redneckmother@hughes.net>
To: development@lists.ipfire.org
Subject: Re: forgot to say...
Date: Wed, 05 Apr 2017 22:20:11 -0500	[thread overview]
Message-ID: <1491448811.31409.8.camel@hughes.net> (raw)
In-Reply-To: <5cf2b020-a9bb-00b9-c371-ca371af707f3@jwsss.com>

[-- Attachment #1: Type: text/plain, Size: 2346 bytes --]

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

       reply	other threads:[~2017-04-06  3:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5cf2b020-a9bb-00b9-c371-ca371af707f3@jwsss.com>
2017-04-06  3:20 ` Paul Simmons [this message]
     [not found] <1491383399.2643.98.camel@ipfire.org>
2017-04-05 14:53 ` Paul Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1491448811.31409.8.camel@hughes.net \
    --to=redneckmother@hughes.net \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox