search for: eminarcissus

...fig, and even though A is in a private subnet, it might still possible for A to establish connection with X(X is public IP address)? 2. If there any parameter to disable the direct connection discovery, and only allow to through intermediate node? > On 1 May 2017, at 3:16 PM, Narcissus Emi <eminarcissus at gmail.com> wrote: > > Indeed it depends, tinc will have a port listening for incoming connections(both tcp and udp), if A have exposed its listening ports, a direct connection will be tried to build between the nodes, otherwise it will go from the intermediate node. > > -- >...

...connection to node X, then I found node A will be able to talk to node X, but the communication path is go through node B, instead of build direct connection between A and X, is that right? I tested this in my environment. A >> B >> X > On 1 May 2017, at 3:07 PM, Narcissus Emi <eminarcissus at gmail.com> wrote: > > X-up is being called when any connection is being built between node A and node X, it doesn't have anything to do whether you have connectTo in the config file or not. > Because tinc is a mesh network, if node A have a direct connection to node B, and node...

...a private > subnet, it might still possible for A to establish connection with X(X is > public IP address)? > 2. If there any parameter to disable the direct connection discovery, and > only allow to through intermediate node? > > > On 1 May 2017, at 3:16 PM, Narcissus Emi <eminarcissus at gmail.com> wrote: > > Indeed it depends, tinc will have a port listening for incoming > connections(both tcp and udp), if A have exposed its listening ports, a > direct connection will be tried to build between the nodes, otherwise it > will go from the intermediate node. >...

...I found node A will be able > to talk to node X, but the communication path is go through node B, instead > of build direct connection between A and X, is that right? I tested this in > my environment. > > A >> B >> X > > On 1 May 2017, at 3:07 PM, Narcissus Emi <eminarcissus at gmail.com> wrote: > > X-up is being called when any connection is being built between node A and > node X, it doesn't have anything to do whether you have connectTo in the > config file or not. > Because tinc is a mesh network, if node A have a direct connection to node &gt...

Hi, Tinc Expert in my tinc.conf, the ConnectTo to host X is commented, like below: #ConnectTo = X and there is a script: /etc/tinc/netname/hosts/X-up, I thought commented the ConnectTo X wouldn’t trigger the X-up, but it did. Why? What’s the logic behind to trigger host-up? How can I avoid this except remove the host-up file? Bright Zhao

X-up is being called when any connection is being built between node A and node X, it doesn't have anything to do whether you have connectTo in the config file or not. Because tinc is a mesh network, if node A have a direct connection to node B, and node B have a connection to node X, you can have a connection between A and X, and X-up is being called at the moment when it built a connection

Hi, I've created a VPN network using route mode with 8 nodes,for example 10.0.0.1-10.0.0.8 I've already set Every node's subnet to 10.0.0.0/24 and set forwarding option to kernel. After I deleted the default route table(ip route 10.0.0.0/24 dev tun) and added the following route options: ip route add 10.0.0.1 dev tun ip route add 10.0.0.2 dev tun10 via 10.0.0.1 and then I tried

Hi, I use tinc-vpn to create private mesh vpn networks between office and house in different locations and it works really well. But somehow I'm considering if there were any possibility to add radius support for single node traffic management. I does think it will be really difficult to implement such functions as a feature of a mesh network,because all of the traffic was initiated end to