similar to: Windows not reconnecting after Standby

Thank you very much. I can confirm that the TAP-WIN32 driver behaves differently. The quick tests so far revealed that it either reconnected after Standby and Hibernation. I think that at some point I started using the OpenVPN drivers when I had either had trouble with unsigned drivers or the network detection and then just stayed with it. Thanks for pointing out my self-made problem. On

You should try using the older TAP-Win32 drivers that are bundled with tinc (i.e. 9.0.0.9). Using the newer, NDIS6 drivers (>= 9.0.0.21) is not recommended; according to some testing I did in the past it seems to result in poor tinc performance (for reasons I wasn't quite able to determine). I am using tinc 1.1 with 9.0.0.9 on Windows 10 and it behaves correctly when returning from standby.

Hello everyone, I am running into the following error messages everytime I try to use a docker overlay network on top of tinc-vpn: Error getting read result from Windows tap device {F30C422F-4524-435F-A15B-71A7E08C260D}: (995) The I/O operation has been aborted because of either a thread exit or an application request. Received packet of 106 bytes from ... (... port 655) Writing packet of 106

Hi Etienne, Am 20.05.2018 um 10:58 schrieb Etienne Dechamps: > Hi Marc, > > A number of bugs have been found and fixed in the code that deals with > Windows devices in tinc 1.1: > > https://github.com/gsliepen/tinc/pull/169 > https://github.com/gsliepen/tinc/pull/173 > https://github.com/gsliepen/tinc/pull/174 > https://github.com/gsliepen/tinc/pull/181 >

Hi Guillermo, Yes, I've also noticed there are still issues with resuming from standby on Windows, despite the latest fixes that I wrote (which are included in 1.1pre15). I think my fixes covered some of the causes of tinc misbehaving on standby, but not all of them. Are you able to reproduce the issue reliably? If so, can you please file an issue at https://github.com/gsliepen/tinc/issues

Hi Guillermo, Yes, I've also noticed there are still issues with resuming from standby on Windows, despite the latest fixes that I wrote (which are included in 1.1pre15). I think my fixes covered some of the causes of tinc misbehaving on standby, but not all of them. Are you able to reproduce the issue reliably? If so, can you please file an issue at https://github.com/gsliepen/tinc/issues

Thanks for the update! I've been testing Tinc 1.1pre14 for a while in linux and windows, and it's working very well. But I'm having some trouble with Windows machines (mostly Win8 and Win10) when resuming from suspended state or hibernation the tinc daemon just stop responding. I have to shut down the process and start it back up to be able to connect to the VPN. The first line on

Thanks for the update! I've been testing Tinc 1.1pre14 for a while in linux and windows, and it's working very well. But I'm having some trouble with Windows machines (mostly Win8 and Win10) when resuming from suspended state or hibernation the tinc daemon just stop responding. I have to shut down the process and start it back up to be able to connect to the VPN. The first line on

On Mon, Sep 04, 2017 at 04:16:46PM +0000, Nirmal Thacker wrote: > Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Yes, but I have not tested this extensively. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833

On Mon, Sep 04, 2017 at 04:16:46PM +0000, Nirmal Thacker wrote: > Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Yes, but I have not tested this extensively. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833

I think you answered your own question. Samba (smbd) is a service. It is doing its job and ready to offer service at any time. Apparently this involves periodically accessing the disk. There is nothing wrong with this; it is normal operation. Samba won't work anyway when you are in standby, so you might as well stop it when you are done using it. PG > -----Original Message----- >

https://bugs.freedesktop.org/show_bug.cgi?id=108022 Bug ID: 108022 Summary: Cannot resume from standby - Link training fails Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

I have a scenario whereby two servers are acting in active-standby mode. In case the active server fail, the shared IP is activated on standby server for continuity. However, SIP phones (all are Polycom) takes quite a long time to register to the Standby Server (up to 1-10min). While Polycom allow double registration, we would like to make it simple by provision only one registration server at a

I'd like to to put the hard drives in standby mode during periods of no activity. I'm just running a file server plus a couple small things on a Qube 3 from home, although the web stuff will increase it's still minimal. On my NetBSD systems I can use atactl to do this via: mount -u -o async,noatime,nodevmtime / mount -u -o async,noatime /usr atactl wd0 setidle 5 [wait a time]

since I got the big bolus of updates from the CR repo a few days ago my netbook (AcerAspire One D255E) will no longer go to standby when the lid is closed. This was a Gnome desktopp installation with theh MATE desktop fromm EPEL. I've verified that the correct setting still exists in power manager but it persists in continuing to run when the lid closes. it WILL go to standby if explicitly

Hi List, I've setup 2 openldap servers in n-way multimaster replication mode in a test environment, both run centos 6.2, this works well but now i'm trying to make these 2 servers failover using heartbeat. i've got no experience with heartbeat (or setting up clusters in general) however from what i understand heartbeat starts/stops the service if the server has the virtual IP

Hi List, I'm running Centos 5.2 on an Pentium III-1000 The box has been running for almost a year without any (hardware) issues. SInce a few weeks the box goes into standby (power led flashes) without any obvious reason (ie. i cannot find anything). This happens randomly (box runs for 1 day and does this, next time it runs for 5 days and it happens). Normally when a box goes into standby,

On Fri, Dec 11, 2015 at 03:40:27PM +0000, Nux! wrote: > I've heard this happening to someone on IRC, the solution if I remember correctly is to update MATE from epel-testing. > See if that works for you. > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro thanks, Nux. I've just installed allthe MATE packaages from epel testing, and

On Fri, Dec 11, 2015 at 03:42:21PM +0000, Richard wrote: > > > > Date: Friday, December 11, 2015 10:29:20 -0500 > > From: Fred Smith <fredex at fcshome.stoneham.ma.us> > > > > since I got the big bolus of updates from the CR repo a few days > > ago my netbook (AcerAspire One D255E) will no longer go to standby > > when the lid is closed. > >

Hi, I've decided to use an external USB disk as backup with rsync. This works fine. When the external disk is mounted, it does not go into standby/sleep/whatever, though I'm using it only for 30minutes at night. Is there a way to do this with C4, 2.6.9-78.0.8.ELsmp? E.g. unmount/some special command/upgrade to 5.2? Thx Raier