public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] VPN vs LAN address hostname resolution
Date: Wed, 22 May 2013 15:44:17 -0400	[thread overview]
Message-ID: <519D2011.1000402@orlitzky.com> (raw)
In-Reply-To: <519D1E02.1080001@gmail.com>

On 05/22/13 15:35, Samuraiii wrote:
>  The only result I got was a script which every 5 minutes checked all
> possible addresses of given machine (my "network" is not big at all -
> only eight machines and one network printer). So checking around 20
> addreses is not big deal - but this approach feels clumsy and not
> scalable to bigger networks (as have other users from list to deal with).
> 
> Script was just checking (by sftp with public ssh keys for unprivileged
> account) if LAN (eth or wifi) address is up and if not it just assigned
> address to hostname from vpn range (it did not accounted if machine is
> up or down). And the just write new /etc/hosts.
> Central dns is possible only in one part of network - only one machine
> runs 24/7.

Can't this be changed? If you're running a script to update 20 hosts
files regularly, you're reinventing what DNS already does.


> 
> Routers on both sides are just simple boxes which support only built-in
> dhcp.
> Central DNS and/or routed VPN does not solve problem of compute not in
> any of "known" networks.

Both would solve the problem.

If the routers are the VPN gateways as well, you could decide e.g. that
a certain chunk of the VPN space belongs to location 1, and then have
the router at location 1 do the appropriate thing (all packets travel
through it, after all). This can be done directly with some VPN
software, or you can translate the addresses on the fly with iptables.

With a DNS server at each physical location, you just have the DNS
server at location 1 return the local (location 1) address instead of
the VPN address for any hostnames physically located at location 1.



  reply	other threads:[~2013-05-22 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 16:36 [gentoo-user] VPN vs LAN address hostname resolution Samuraiii
2013-05-22 17:36 ` Michael Orlitzky
2013-05-22 17:52   ` Michael Mol
2013-05-22 18:30     ` Samuraiii
2013-05-22 18:40       ` Michael Mol
2013-05-22 18:52       ` Michael Orlitzky
2013-05-22 19:35         ` Samuraiii
2013-05-22 19:44           ` Michael Orlitzky [this message]
2013-05-22 20:52           ` Alex
2013-05-22 22:32         ` William Kenworthy
2013-05-22 20:43     ` covici
2013-05-22 20:40   ` covici
2013-05-31 16:04 ` [gentoo-user] " Samuraiii
2013-05-31 16:32   ` Samuraiii

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=519D2011.1000402@orlitzky.com \
    --to=michael@orlitzky.com \
    --cc=gentoo-user@lists.gentoo.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