search for: autoconnecting

Displaying 20 results from an estimated 110 matches for "autoconnecting".

2017 Aug 22
2
using both ConnectTo and AutoConnect to avoid network partitions
Hi Today our Tinc network saw a network partition when we took one tinc node down. We knew there was a network partition since the graph showed a split. This graph is not very helpful but its what I have at the moment: http://i.imgur.com/XP2PSWc.png - (ignore node labeled ignore, since its a dead node anyways) - node R was shutdown for maintenance - We saw a network split - we brought node R
2017 Aug 31
2
using both ConnectTo and AutoConnect to avoid network partitions
Thanks Guss, some comments and questions: If you make the yellow nodes ConnectTo all other nodes, and not have > AutoConnect = yes, and the other nodes just have AutoConnect = yes but > no ConnectTo's, then you will get the desired graph. The reason this approach is not desirable is because it fails at automation. It requires us to add a new line of AutoConnect = <new node that
2017 Jan 13
2
Reliable way of having both LAN and WIFI on headless box
On Fri, Jan 13, 2017 at 12:33 PM, Gary Stainburn <gary at ringways.co.uk> wrote: > > > Also, it was suggested that I use nmcli in a cronjob to re-activate it if > it > drops. I can check to see if it's still active by 'grep'ing the IP > address, > but I don't know the nmcli to re-activate an existing WIFI connection. > > Can anyone help here too,
2017 Aug 31
2
using both ConnectTo and AutoConnect to avoid network partitions
Hi Guus Following your suggestion we reconfigured our tinc network as follows. Here is a new graph and below is our updated configuration: http://imgur.com/a/n6ksh - 2 Tinc nodes (yellow labels) have a public external IP and port 655 open. They both have ConnectTo's to each other and AutoConnect = yes - The remainder tinc nodes (blue labels) have their tinc.conf set up as follows:
2017 Jan 18
2
Reliable way of having both LAN and WIFI on headless box
You could say the same thing about computers in general: I hate them, they automated many tasks in life and took many jobs out of the market!. Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: eliezer at ngtech.co.il -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Gary Stainburn Sent: Monday, January 16, 2017
2017 Aug 22
0
using both ConnectTo and AutoConnect to avoid network partitions
On Mon, Aug 21, 2017 at 05:37:06PM -0700, Nirmal Thacker wrote: > Today our Tinc network saw a network partition when we took one tinc node > down. > > We knew there was a network partition since the graph showed a split. This > graph is not very helpful but its what I have at the moment: > > http://i.imgur.com/XP2PSWc.png The graph is very clear. > Some questions:
2016 Jul 07
2
NetworkManger creates extra bonds; is this a bug?
Hi All, I see an unexpected beahviour from NetworkManager on CentOS 7.1. Using nmcli tool, I create a bond with two slaves as explained in the Red Hat 7.1 Networking guide. I enable slaves and master; bond works as expected. When I restart NetworkManager, it creates a new bond with the same name but not connected to any device. Two bonds with the same name is confusing for my other monitoring
2017 Aug 22
3
using both ConnectTo and AutoConnect to avoid network partitions
Hi Guus Thanks for clarifying. Some follow up questions: - How do we patch 1.1pre14 with this fix? Or will there be a 1.1pre15 to upgrade to? - What is the workaround until we patch with this fix? Using a combination of AutoConnect and ConnectTo? - When we use ConnectTo, is it mandatory to have a cert file in the hosts/* dir with an IP to ConnectTo ? -nirmal On Tue, Aug 22, 2017 at 12:10
2017 Aug 31
0
using both ConnectTo and AutoConnect to avoid network partitions
On Thu, Aug 31, 2017 at 01:37:28PM -0700, Nirmal Thacker wrote: > If you make the yellow nodes ConnectTo all other nodes, and not have > > AutoConnect = yes, and the other nodes just have AutoConnect = yes but > > no ConnectTo's, then you will get the desired graph. > > The reason this approach is not desirable is because it fails at > automation. It requires us to
2017 Jan 16
0
Reliable way of having both LAN and WIFI on headless box
On Friday 13 January 2017 12:40:33 Gianluca Cecchi wrote: > On Fri, Jan 13, 2017 at 12:33 PM, Gary Stainburn <gary at ringways.co.uk> > > wrote: > > Also, it was suggested that I use nmcli in a cronjob to re-activate it if > > it > > drops. I can check to see if it's still active by 'grep'ing the IP > > address, > > but I don't know the
2017 Aug 31
0
using both ConnectTo and AutoConnect to avoid network partitions
On Thu, Aug 31, 2017 at 10:40:39AM -0700, Nirmal Thacker wrote: > Following your suggestion we reconfigured our tinc network as follows. > Here is a new graph and below is our updated configuration: > http://imgur.com/a/n6ksh [...] > We are concerned that: > - We still dont see edges in the graph that show connections between every > blue labeled node to both the yellow labeled
2017 Jan 18
0
Reliable way of having both LAN and WIFI on headless box
On Wed, January 18, 2017 4:24 am, Eliezer Croitoru wrote: > You could say the same thing about computers in general: > I hate them, they automated many tasks in life and took many jobs out of > the > market!. And they suck. All systems suck. And thanks to that I got my job. Valeri > > Eliezer > > ---- > Eliezer Croitoru > Linux System Administrator > Mobile:
2015 Jan 13
2
tinc connectTo cleanup
thanks Guus for the quick response. I am using tinc 1.1 if I use AutoConnect = yes then will it automatically remove connections that are no longer in use? What are the security issues with 'AutoConnect = yes' I should be worried? for my use case I might go upto 20 to 30 + tinc hosts connected to single tinc box. as per the doc AutoConnect = yes is experimental, I am using it in our
2016 Jul 07
2
NetworkManger creates extra bonds; is this a bug?
On 07/07/16 05:36 PM, Digimer wrote: > On 07/07/16 05:21 PM, Joe Smithian wrote: >> Hi All, >> >> I see an unexpected beahviour from NetworkManager on CentOS 7.1. >> Using nmcli tool, I create a bond with two slaves as explained in the Red >> Hat 7.1 Networking guide. I enable slaves and master; bond works as >> expected. >> When I restart
2014 Jul 06
1
Hardcoded limit on the number of meta-connections
Hi, I was quite surprised to see commmit 332b55d4 ("Change AutoConnect from int to bool"). Is there experimental evidence supporting 3 as the hardcoded maximum number of meta-connections? If there is a good reason for this limit on the number of meta-connections, maybe it should apply whatever the value of AutoConnect (currently, it is only enforced when AutoConnect is on). We may
2016 Jul 07
0
NetworkManger creates extra bonds; is this a bug?
On 07/07/16 05:21 PM, Joe Smithian wrote: > Hi All, > > I see an unexpected beahviour from NetworkManager on CentOS 7.1. > Using nmcli tool, I create a bond with two slaves as explained in the Red > Hat 7.1 Networking guide. I enable slaves and master; bond works as > expected. > When I restart NetworkManager, it creates a new bond with the same name but > not connected to
2017 May 11
0
AutoConnect option and 1.1pre version
Hello, I want to know how works exactly the AutoConnect option, and what happen if we have more than 1000 nodes, with this option enabled. And another question is, how much stable is the version 1.1pre14 for production use. Thanks.
2017 Aug 23
0
using both ConnectTo and AutoConnect to avoid network partitions
On Tue, Aug 22, 2017 at 03:19:18PM -0700, Nirmal Thacker wrote: > - How do we patch 1.1pre14 with this fix? Or will there be a 1.1pre15 to > upgrade to? There will be an 1.1pre15, but if you want you can apply the following commit: https://tinc-vpn.org/git/browse?p=tinc;a=commitdiff;h=92fdabc439bdb5e16f64a4bf2ed1deda54f7c544 > - What is the workaround until we patch with this fix?
2016 Jul 11
0
NetworkManger creates extra bonds; is this a bug?
Hi Neil, Thanks for your comments. What's the purpose of creating spurious ?bond0?? It's confusing. Is it anywhere documented? Every time I restart NetworkManager it creates another bond0! Joe On Thu, Jul 7, 2016 at 5:44 PM, Digimer <lists at alteeve.ca> wrote: > On 07/07/16 05:36 PM, Digimer wrote: > > On 07/07/16 05:21 PM, Joe Smithian wrote: > >> Hi All, >
2017 Aug 24
1
using both ConnectTo and AutoConnect to avoid network partitions
Thanks Guus I have one more question. - We see several log messages that we dont currently understand - Can you comment on what they mean and if they are concerning? I've obfuscated IP's and node names so please ignore those. Our tinc daemon command is: tincd -n <vpn name> -- Received short packet -- Got REQ_KEY from node003 while we already started a SPTPS session! -- Invalid