Is there a bug in the DYNDNS code that it is using time() instead of our now() (which is guaranteed not to go backwards) ?
Paul ---------- Forwarded message ---------- Date: Wed, 23 Apr 2014 01:01:31 From: brijeshvalera <[email protected]> Cc: "Paul Wouters (libreswan)" <[email protected]> To: xelerance/Openswan <[email protected]> Subject: Re: [Openswan] Openswan is not sending packets on new ip after dpd (#74) X-Spam-Flag: NO I digged into the code & environment. I have found that there is two ntp working on appliance which has set anonymous timezone value. Both are setting appliance time +7 hours & -7 hours. In code EVENT_PENDING_DDNS is using time() function which is getting time_t (long value) from system time. And due to this misbehaving system time event is not getting happened again. This is the issue (from my side). Thanks a lot for support. :dash: :dancer: :+1: — Reply to this email directly or view it onGitHub.[3003897__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcxMzg0ODQ5MSwiZGF0YSI6eyJpZCI6MjkyODI1MTZ9fQ==--f a8e5732ff004d2d5658a11b4f626210a3b4f43e.gif] _______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
