similar to: nm-bridge & nm-team and no connection.

AFAIK, and my setups thus far, unless you have NodeB’s public key in Nodes C-Z (with NodeB’s public/reachable IP configured in Nodes C-Z) *and* you have the PublicKeys for NodesC-z configured in NodeB, there is no way that NodesC-Z will be able to establish a connection directly with NodeB, and it’ll have to forward via NodeA (or any other node that do have a direct connection established with

On Mon, May 22, 2017 at 11:03:30AM +0200, Keith Whyte wrote: > I have two tinc nodes (A and B) behind a firewall > > NodeA and NodeB have 192.168.1.2 and 192.168.1.3 assigned on an internal > LAN, and they both have different public IP addresses forwarded to them, > port 655 udp/tcp > > I would like any given node in the C-Z group to be able to find Node B > on it's

Hi all I feel like I should know the answer to this question, like I read it someplace sometime, but it evades me right now. It's also an opportunity to say hello to the list and many thanks for writing and supporting tinc vpn! We make great use of it at rhizomatica. So, Let's take this example setup. I have two tinc nodes (A and B) behind a firewall NodeA and NodeB have 192.168.1.2

Dear all Recently, i did some work to test small files performance for gnfsv3 transport. Following is my scenario. #####environment##### ==2 cluster nodes(nodeA/nodeB)== each is equipped with E5-2650*2, 128G memory and 10GB*2 netcard nodeA: 10.254.3.77 10.128.3.77 nodeB: 10.254.3.78 10.128.3.78 ==2 stress nodes(clientA/clientB)== each is equipped with E5-2650*2, 128G memory and 10GB*2

Hi Guus, I've been a huge fan of the GraphDumpFile parameter in tinc -- it certainly beats sending USR2 to tincd, and ploughing through syslog to figure out which nodes are connected. Could I request that GraphDumpFile dumps a little more data to the file, namely, the subnet; changing the output file from (for example): digraph { nodeA [label = "nodeA"];

I have an rsync server running on nodeA and a client, nodeB. I am attempting to do a sync/copy from the local machine, nodeB, to the rsync server, nodeA. The following line from the rsync man page makes it look like this is relatively simple: for copying from the local machine to a remote rsync server. This is invoked when the destination path contains a :: separator or a rsync:// URL. I have

From: Xue jiufei <xuejiufei at huawei.com> Subject: ocfs2: dlm_request_all_locks() should deal with the status sent from target node dlm_request_all_locks() should deal with the status sent from target node if DLM_LOCK_REQUEST_MSG is sent successfully, or recovery master will fall into endless loop, waiting for other nodes to send locks and DLM_RECO_DATA_DONE_MSG to me. NodeA

dlm_request_all_locks() should deal with the status sent from target node if DLM_LOCK_REQUEST_MSG is sent successfully, or recovery master will fall into endless loop, waiting for other nodes to send locks and DLM_RECO_DATA_DONE_MSG to me. NodeA NodeB selected as recovery master

llseek requires ocfs2 inode lock for updating the file size in SEEK_END. because the file size maybe update on another node. if it not . after call llseek in SEEK_END. the position is old. this bug can be reproduce the following scenario: at first ,we dd a test fileA,the file size is 10k. on NodeA: --------- 1) open the test fileA, lseek the end of file. and print the position. 2) close the test

You have a typo in your routes: fd80:2015:2105:adcd::/6 abcd vs. adcd On 21 May 2015, at 19:35, Martin <martinmoen at gmail.com<mailto:martinmoen at gmail.com>> wrote: I have 2 nodes nodeA and nodeB I'm using tinc 1.1pre11 -- nodeA(fd80:2015:2105:abcd::1) : $ ip -6 route fd80:2015:2105:abcd::1 dev tun0 proto kernel metric 256 fd80:2015:2105:adcd::/64 dev tun0 metric 1024

I have 2 nodes nodeA and nodeB I'm using tinc 1.1pre11 -- nodeA(fd80:2015:2105:abcd::1) : $ ip -6 route fd80:2015:2105:abcd::1 dev tun0 proto kernel metric 256 fd80:2015:2105:adcd::/64 dev tun0 metric 1024 fe80::/64 dev eth0 proto kernel metric 256 $ ping6 fd80:2015:2105:abcd::1 PING fd80:2015:2105:abcd::1(fd80:2015:2105:abcd::1) 56 data bytes 64 bytes from fd80:2015:2105:abcd::1:

llseek requires ocfs2 inode lock for updating the file size in SEEK_END. because the file size maybe update on another node. if it not . after call llseek in SEEK_END. the position is old. this bug can be reproduce the following scenario: at first ,we dd a test fileA,the file size is 10k. on NodeA: --------- 1) open the test fileA, lseek the end of file. and print the position. 2) close the test

quoted from http://www.tinc-vpn.org/examples/redirect-gateway/ "In fact, one does not have to set the VPN_GATEWAY variable at all. In switch mode, the gateway routes are necessary" i don't get it. it's is too short to understand. is VPN_GATEWAY set by tinc in switch mode? and why is "In switch mode, the gateway routes are necessary" mentioned here suddenly? afaik,

On Mon, May 22, 2017 at 4:03 AM, Keith Whyte <keith at rhizomatica.org> wrote: > Is there a way to force NodeA or NodeB to "advertise" it's public IP to > the rest of the tinc network, or did I miss something really obvious? the config files can use DNS names, right? Have the nodes that you want to advertise their public IP addresses sign up with Dyndns or similar,

Hi, [sorry for the crosspost, I don''t know whether this is a routing or ebtables problem] I want to redirect all HTTP traffic passing through my bridge to a squid proxy on another machine. However, setting up brouting as suggested in the ebtables examples doesn''t work and the packets get dropped on the floor completely. /\/\/\/\/\/\/\/\ +----------------------+

Hi all, I've recently started using NetworkManger service and nmcli tool, I like it much better than the old network service and manually modifying network scripts. I've seen many online questions on how to disable NetworkManger but I have the opposite question! I am wondering if it be OK to disable network service altogether and just use NetworkManger for configuring and managing Ethernet

Shorewall 4.5.15 3 Interface setup em1 p3p1 p4p4 ppp0 Hi, Since changing to NetworkManger on Fedora 18 I can no longer connect to the DSL Modem, which is connected to Interface em1. When the NetworkManger brings up the interfaces and ppp0, it no longer assigns an IP to em1. If I have ppp0 disabled and NetworkManger brings up the interfaces, em1 gets an IP of 192.168.1.2. Then when I get

Hi all, Long email but please be patient :) I am part of EHAS [1], a non profit organization which main goal is to improve the Healthcare assistance in isolated rural areas in developing countries. Recently we have developed a long distance Wi-Fi network in Cuzco (Peru). This network provides connectivity to 12 nodes (they are in fact Health Centers). As VoIP is a essential service in this

We use puppet with two environments: [main] and [development]. These environments have different locations for their puppet manifests and modules (see puppet.conf below). Whenever I change/update a file in the directories belonging to the “main” environment, puppetmaster notices these changes and reacts to them w/o any hiccups. In contrast to this – if I change/touch a file in a directory

On 09/04/2016 05:00 PM, Ulf Volmer wrote: >> IPADDR2=192.168.1.10 >> BROADCAST2=192.168.1.255 <-- >> NETMASK2=255.255.255.0 >> NETWORK2=192.168.1.0 <-- >> GATEWAY2=192.168.1.1 <-- >> >> in case they don't match the first IP address? > > I'm not sure at this point. If you have to add a second ip in another > different network