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.
