1 |
I am doing something sort of similar ... use a routing protocol and set |
2 |
the metrics to make the LAN more attractive so it will get used over the |
3 |
wifi. Use dhcp to update dns. |
4 |
|
5 |
I was using ospf (quagga), dns and ISC dhcp which auto-updates bind. |
6 |
This is "transparent" to the the hosts, is a pain to set up but then |
7 |
just works. |
8 |
|
9 |
Pinning addresses makes like life very difficult though as dhcp wont |
10 |
update dns so Ive gone back to manually setting up the dns side for some |
11 |
hosts :( |
12 |
|
13 |
BillK |
14 |
|
15 |
|
16 |
On 23/05/13 02:52, Michael Orlitzky wrote: |
17 |
> On 05/22/13 14:30, Samuraiii wrote: |
18 |
>> I'm sorry for mistake the subnet mask for both spaces IS 255.255.255.0. |
19 |
>> so it is not overlapping at all. |
20 |
>> I apologise for my mistake in notation. |
21 |
>> still this is not (mainly) problem with routing but problem with |
22 |
>> assigning name to address. |
23 |
>> If I had superfast internet connection I would not mind and just use vpn |
24 |
>> address space. |
25 |
>> So basically i need to assign lan address to computer (laptop) which is |
26 |
>> in same location (LAN) as other machines. And vpn address on all other |
27 |
>> computers. |
28 |
>> |
29 |
>> to illustrate: |
30 |
>> |
31 |
>> hostname: foo |
32 |
>> Location:1 |
33 |
>> address eth0: 10.1.1.3 |
34 |
>> address tap0: 10.2.2.3 |
35 |
>> |
36 |
>> hotname: bar |
37 |
>> Location: 1 |
38 |
>> addresses are irrelevant |
39 |
>> hosts entry for foo is 10.1.1.3 *(this is what I want to update if foo |
40 |
>> moves to location 2 to 10.2.2.3)* |
41 |
>> |
42 |
>> hosname baz |
43 |
>> Location: 2 |
44 |
>> addresses are irrelevant |
45 |
>> Hosts entry for foo is 10.2.2.3 *(this is what I want to update if foo |
46 |
>> moves to location 2 to 10.1.1.3)* |
47 |
>> |
48 |
> |
49 |
> Which machines are joined to the VPN? For a location-to-location VPN, |
50 |
> the simplest thing to do would be to have your gateway routers |
51 |
> participate in the VPN and handle the routing appropriately. That way if |
52 |
> you're on the LAN at location 1 and you send a packet to another machine |
53 |
> on the same LAN (using its VPN address), the gateway router knows to |
54 |
> send the packet right back onto the LAN. No configuration necessary on |
55 |
> the hosts. You can use the same VPN addresses at both locations. |
56 |
> |
57 |
> If that's not possible, set up a DNS resolver at each location and |
58 |
> return the appropriate (local or VPN) address. |
59 |
> |
60 |
> |