On 2013-05-22 20:52, Michael Orlitzky wrote: > On 05/22/13 14:30, Samuraiii wrote: >> I'm sorry for mistake the subnet mask for both spaces IS 255.255.255.0. >> so it is not overlapping at all. >> I apologise for my mistake in notation. >> still this is not (mainly) problem with routing but problem with >> assigning name to address. >> If I had superfast internet connection I would not mind and just use vpn >> address space. >> So basically i need to assign lan address to computer (laptop) which is >> in same location (LAN) as other machines. And vpn address on all other >> computers. >> >> to illustrate: >> >> hostname: foo >> Location:1 >> address eth0: 10.1.1.3 >> address tap0: 10.2.2.3 >> >> hotname: bar >> Location: 1 >> addresses are irrelevant >> hosts entry for foo is 10.1.1.3 *(this is what I want to update if foo >> moves to location 2 to 10.2.2.3)* >> >> hosname baz >> Location: 2 >> addresses are irrelevant >> Hosts entry for foo is 10.2.2.3 *(this is what I want to update if foo >> moves to location 2 to 10.1.1.3)* >> > Which machines are joined to the VPN? For a location-to-location VPN, > the simplest thing to do would be to have your gateway routers > participate in the VPN and handle the routing appropriately. That way if > you're on the LAN at location 1 and you send a packet to another machine > on the same LAN (using its VPN address), the gateway router knows to > send the packet right back onto the LAN. No configuration necessary on > the hosts. You can use the same VPN addresses at both locations. > > If that's not possible, set up a DNS resolver at each location and > return the appropriate (local or VPN) address. > > 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. For me personally is not problem to remember where am I - but other users need names instead of adresses. 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. S
