Address Variabme for Roadwarriors]

[Lonnie Cumberland]

I'm sorry for not being clear in my message.

What I want to do is this. Take your documentation example where you 
have 4 hosts, A, B, C, and D.  You state that B, C will connect to A and 
that D will connect to C.

In my case, I will have node C being a road warrior and node D wants to 
connect to it who is also a road warrior. 

My solution to this is to have a private DNS inside the VPN network, 
maybe on node A for example, such that all nodes can see the DNS server 
and in the case of the road warriors, nodes C & D, we will have that D 
can find C because it resolved the 10.0.0.21 ip, for example, from our 
private VPN DNS.

At least that is the idea anyway.

As I understand things now, a roadwarrior host that is going to allow 
connection other connections must use something like dyndns to allow 
others to resolve a "real" ip.

I want to find a way to allow the roadwarior host to allow connections 
by letting other nodes in the vpn resolve the roadwarrior host through 
the private VPN DNS instead of the service like dyndns.

Thanks again,
Lonnie

Guus Sliepen wrote:

>On Sun, Oct 24, 2004 at 05:08:39PM -0500, Lonnie Cumberland wrote:
>
>  
>
>>What I will like to do is to give all of the uses, including 
>>roadwarriors, a static IP address on the 10.x.x.x address net and have a 
>>name in our VPN DNS associated with each one. This lead to the next problem.
>>
>>Is there a way that the TinC project can come up with a new variable 
>>possibly called "VPNDNS=" or something like that such that the 
>>roadwarriors hosts files can use it to resolve the "ADDRESS=" variable.
>>    
>>
>
>I don't know what you want exactly. Is VPNDNS the address of the DNS
>server that tincd should use to resolve the Address? In that case, just
>put that in /etc/resolv.conf. Is it the address of the DNS server that
>your system should use after connecting to the VPN? In that case you can
>use a host-up script[1] to modify /etc/resolv.conf after connecting to the
>VPN. Or do you mean something else?
>
>Anyway, the tinc daemon itself doesn't really care or know about DNS
>servers. It just transports network packets.
>
>[1] http://www.tinc-vpn.org/documentation/tinc_4.html#SEC45
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>tinc mailing list
>tinc at tinc-vpn.org
>http://brouwer.uvt.nl/cgi-bin/mailman/listinfo/tinc
>  
>