similar to: netname dependent segfault

I have two Windows 2003 Standard Edition Server with 2x 3,0 GHz P4 and 4 GB RAM. On each server rsync runs as cygwin daemon (rsync version 2.6.6; protocol version 29). The two servers are connected through a 2 MBit VPN link. When I sync a single large file or a whole directory, rsync only uses 50% of the available bandwidth. When I do the same between windows and linux server, rsync takes the

I think this is probably my first post to this mailing list, so hello! Occasionally I log in to my servers from IP addresses without reverse DNS configured, so sometimes I'll see an IP I don't recognise because I can't remember what I did the day before and get a bit spooked until I WHOIS the IP and find the netname reminds me I logged in from that IP. I set out prepared to script

On 01/24/2017 11:16 AM, Kevin Stange wrote: > On 01/24/2017 09:10 AM, Konrad Rzeszutek Wilk wrote: >> On Tue, Jan 24, 2017 at 09:29:39PM +0800, -=X.L.O.R.D=- wrote: >>> Kevin Stange, >>> It can be either kernel or update the NIC driver or firmware of the NIC >>> card. Hope that helps! >>> >>> Xlord >>> -----Original Message-----

On 01/26/2017 02:08 PM, Kevin Stange wrote: > On 01/26/2017 09:35 AM, Johnny Hughes wrote: >> On 01/26/2017 09:32 AM, Johnny Hughes wrote: >>> On 01/25/2017 11:49 AM, Kevin Stange wrote: >>>> On 01/24/2017 11:16 AM, Kevin Stange wrote: >>>>> On 01/24/2017 09:10 AM, Konrad Rzeszutek Wilk wrote: >>>>>> On Tue, Jan 24, 2017 at 09:29:39PM

On 01/26/2017 09:32 AM, Johnny Hughes wrote: > On 01/25/2017 11:49 AM, Kevin Stange wrote: >> On 01/24/2017 11:16 AM, Kevin Stange wrote: >>> On 01/24/2017 09:10 AM, Konrad Rzeszutek Wilk wrote: >>>> On Tue, Jan 24, 2017 at 09:29:39PM +0800, -=X.L.O.R.D=- wrote: >>>>> Kevin Stange, >>>>> It can be either kernel or update the NIC driver or

On 09/06/2017 05:21 PM, Kevin Stange wrote: > On 09/06/2017 08:40 AM, Johnny Hughes wrote: >> On 09/05/2017 02:26 PM, Kevin Stange wrote: >>> On 09/04/2017 05:27 PM, Johnny Hughes wrote: >>>> On 09/04/2017 03:59 PM, Kevin Stange wrote: >>>>> On 09/02/2017 08:11 AM, Johnny Hughes wrote: >>>>>> On 09/01/2017 02:41 PM, Kevin Stange wrote:

On 11/02/17 06:29, Kevin Stange wrote: > On 01/30/2017 06:41 PM, Kevin Stange wrote: >> On 01/30/2017 06:12 PM, Adi Pircalabu wrote: >>> On 31/01/17 10:49, Kevin Stange wrote: >>>> You said 3.x kernels specifically. The kernel on Xen Made Easy now is a >>>> 4.4 kernel. Any chance you have tested with that one? >>> >>> Not yet, however

On Tue, Jan 24, 2017 at 09:29:39PM +0800, -=X.L.O.R.D=- wrote: > Kevin Stange, > It can be either kernel or update the NIC driver or firmware of the NIC > card. Hope that helps! > > Xlord > -----Original Message----- > From: CentOS-virt [mailto:centos-virt-bounces at centos.org] On Behalf Of Kevin > Stange > Sent: Tuesday, January 24, 2017 1:04 AM > To: centos-virt

On 03/27/2017 04:03 PM, Kevin Stange wrote: > On 03/25/2017 02:35 PM, Sarah Newman wrote: >> On 03/16/2017 04:22 PM, Kevin Stange wrote: >> >>>> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >>>> server has yet had a NIC issue, with some being up almost a full month. >>>> It looks promising! (I'm knocking on all the

Hi all, I am trying to setup a configuration of Tinc to allow multiple tincd daemons for a same network (mixing bonding, etc...). I will post my solution later if I found one. This is to get better speeds in multiple gigabit/sec networks. So my question is not about this directly. I would like to know if the "netname" configured on each node, is used somewhere in communications

On 14-09-2017 20:57, Adi Pircalabu wrote: > On 08-09-2017 6:17, Kevin Stange wrote: >> On 09/06/2017 05:21 PM, Kevin Stange wrote: >>> On 09/06/2017 08:40 AM, Johnny Hughes wrote: >>>> On 09/05/2017 02:26 PM, Kevin Stange wrote: >>>>> On 09/04/2017 05:27 PM, Johnny Hughes wrote: >>>>>> On 09/04/2017 03:59 PM, Kevin Stange wrote:

If you have multiple ConnectTo statements in your tinc.conf, then tinc will attempt to establish connections with *all* of them. It is not a fallback, though it is a good idea for every node to have at least two direct connections for improved resiliency and fault tolerance. As to whether you should have just one tinc network or multiple networks, well, that depends on what you're trying to

On 02/21/2017 05:32 PM, Kevin Stange wrote: > On 02/21/2017 11:50 AM, Johnny Hughes wrote: >> On 02/21/2017 11:47 AM, Johnny Hughes wrote: >>> >>> >>> Kevin, >>> >>> Please try the 4.9.11-22 kernel that I just released for CentOS-6 (along >>> with the newer linux-firmare packages and xfsprogs). >>> >>> If you enable

greetings All, I have been reading over the Tinc manual and have become very interested in the "4.2 Multiple Networks" section of the manual. In particular, I am wondering if I read this correctly in that by using: `-n, --net=netname' Use configuration for net netname. then I can have multiple daemons running on the same machine. If I have 3 machines A, B, and C with A being

On 09/05/2017 02:26 PM, Kevin Stange wrote: > On 09/04/2017 05:27 PM, Johnny Hughes wrote: >> On 09/04/2017 03:59 PM, Kevin Stange wrote: >>> On 09/02/2017 08:11 AM, Johnny Hughes wrote: >>>> On 09/01/2017 02:41 PM, Kevin Stange wrote: >>>>> On 08/31/2017 07:50 AM, PJ Welsh wrote: >>>>>> A recently created and fully functional CentOS

That's exactly right. Corollary: if you take one node from a tinc network and connect it to a node from another isolated tinc network, the two networks become one :) On 1 May 2017 at 13:16, Bright Zhao <startryst at gmail.com> wrote: > Hi, Etienne > > Thanks for your clarification, and this helped a lot. And in order to get > a better understanding for the mechanism of Tinc

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guus: Thanks for the reply. Did you like the PDF examples? Do you want to help me build more examples for the web site so people can download the PDF network diagrams and have sample config files to match them? What changes should I make to allow for easier setup/config/config files of the 2 use cases? For the production example, would it be

On 01/30/2017 06:12 PM, Adi Pircalabu wrote: > On 31/01/17 10:49, Kevin Stange wrote: >> You said 3.x kernels specifically. The kernel on Xen Made Easy now is a >> 4.4 kernel. Any chance you have tested with that one? > > Not yet, however the future Xen nodes we'll deploy will run CentOS 7 and > Xen with kernel 4.4. I'll keep you (and others here) posted on my

Kevin has been rolling back the security updates to the 4.4 branch. He has been working with some of the other distros (debian for sure, and some others on the xen security list). I think it is his intention to continue this for as long as he is able to. (Kevin, chime in if you have a schedule lifetime or EOL in mind) As long as Kevin (or anyone else) maintains the tree, I am happy to build

Xen 4.4.4 along with kernel 4.9.44 containing patches for XSAs (226 - 230) from August 15th are now available in centos-virt-testing. If possible, please test and provide feedback here so we can move these to release soon. XSA-228 did not affect Xen 4.4 XSA-229 only applies to the kernel XSA-235 disclosed today only affects ARM and isn't going to be added to these packages. Thanks. --