VPN Single Daemon For LAN/WAN

[md at rpzdesign.com]

Guus:

Ok, I accept your challenge.

But I am clueless in terms of getting the routing table correct.

So each server has a dual identity, both a LAN private identity with a
PRIVATE IP address and a WAN public identify with a PUBLIC ip address.

And how to have 2 different tun devices show up in the ifconfig -a so
that LAN IP address can be assigned to the tun0 and a WAN IP address can
be assigned to the tun1

When I run 2 tincd daemons, I keep both "networks" separate.

You expert judgement needed here to realize your statement about only
needing a single tincd daemon.


md

On 12/14/2014 7:14 AM, Guus Sliepen wrote:
> On Fri, Dec 12, 2014 at 02:21:08AM -0500, md at rpzdesign.com wrote:
> 
>> Oops, I got it to work only after putting the WAN on port 656 so it
>> did not interfere with port 655 for the LAN.
> 
> You should not need to have two tinc daemons just because you have a WAN
> and a LAN interface. By default (ie, if you don't specify BindToAddress
> and/or BindToInterface), tinc listens on all interfaces, and the
> kernel should normally take care of selecting which outgoing interface
> to use for tinc's packets.
> 
> 
> 
> _______________________________________________
> tinc-devel mailing list
> tinc-devel at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc-devel
>