similar to: Hardcoded limit on the number of meta-connections

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

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:

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

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

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:

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

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

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

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,

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

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, >

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

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

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

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

On Tue, Jan 13, 2015 at 10:37:28AM +0530, Anil Moris wrote: > 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

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:

Dear Mark, thanks for the additional hints. On 22/09/2020 17:26, Mark Milhollan wrote: > On Tue, 22 Sep 2020, Felix K?lzow wrote: > >> A secondary ip address seems to be automatically added to a nic which >> causes several issues in our setup. > >> # nmcli con show >> NAME????? UUID????????????????????????????????? TYPE????? DEVICE >> eno4?????

Dear members, Please tell me what's wrong. After setig firewalld, I got fail on cloud-init with reboot. The server is rebooted, but I cannot access from internet. Before reboot I can access form internet. And before setig firewalld, there's no problem on reboot. /var/log/cloud-init.log shows following Jul 17 14:18:46 biz105 cloud-init: ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info

On Tue, Dec 11, 2018 at 02:36:18PM +0800, Amit Lianson wrote: > We're suffering from sporadic network blockage(read: unable to ping > other nodes) with 1.1-pre17. Before upgrading to the 1.1-pre release, > the same network blockage also manifested itself in a pure 1.0.33 > network. > > The log shows that there are a lot of "Got ADD_EDGE from nodeX >