aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/src/timers.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* global: use pointer to net_deviceJason A. Donenfeld2017-07-201-4/+4
| | | | | | DaveM prefers it to be this way per [1]. [1] http://www.spinics.net/lists/netdev/msg443992.html
* timers: queue up killing ephemerals only if not alreadyJason A. Donenfeld2017-05-311-1/+1
|
* timers: reset retry-attempt counter when not retryingJason A. Donenfeld2017-05-311-2/+2
|
* timers: the completion of a handshake also is on key confirmationJason A. Donenfeld2017-05-311-2/+2
|
* timers: rework handshake reply control flowJason A. Donenfeld2017-05-311-9/+8
|
* debug: print interface name in dmesgJason A. Donenfeld2017-05-311-3/+5
|
* timers: fix typo in commentJason A. Donenfeld2017-05-301-1/+1
| | | | Suggested-by: Peter Wu <peter@lekensteyn.nl>
* handshake: process in parallelJason A. Donenfeld2017-05-301-1/+1
|
* data: cleanup parallel workqueue and use two max_activeJason A. Donenfeld2017-04-081-1/+1
|
* timers: elide enable checkJason A. Donenfeld2017-03-141-3/+3
|
* timers: use simpler uninit sync techniqueJason A. Donenfeld2017-02-071-35/+22
|
* timers: use setup_timer macro helperJason A. Donenfeld2017-01-231-20/+5
|
* Update copyrightJason A. Donenfeld2017-01-101-1/+1
|
* peer: don't use sockaddr_storage to reduce memory usageJason A. Donenfeld2016-12-131-3/+3
|
* socket: clear src address when retrying handshakeJason A. Donenfeld2016-12-091-0/+6
|
* timers: add random jitter to handshake retryJason A. Donenfeld2016-12-091-1/+1
|
* headers: cleanup noticesJason A. Donenfeld2016-11-211-1/+1
|
* socket: keep track of src address in sending packetsJason A. Donenfeld2016-11-151-3/+3
|
* send: simplify handshake initiation queueing and introduce lockJason A. Donenfeld2016-11-071-4/+6
|
* timers: take reference like a lookup tableJason A. Donenfeld2016-11-031-23/+18
|
* timers: only have initiator rekeyJason A. Donenfeld2016-10-191-33/+0
| | | | | | | | | If it's time to rekey, and the responder sends a message, the initator will begin the rekeying when sending his response message. In the worst case, this response message will actually just be the keepalive. This generally works well, with the one edge case of the message arriving less than 10 seconds before key expiration, in which the keepalive is not sufficient. In this case, we simply rehandshake immediately.
* timers: always delay handshakes for responderJason A. Donenfeld2016-10-191-0/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With the prior behavior, when sending a packet, we checked to see if it was about time to start a new handshake, and if we were past a certain time, we started it. For the responder, we made that time a bit further in the future than for the initiator, to prevent the thundering herd problem of them both starting at the same time. However, this was flawed. If both parties stopped communicating after 2.2 minutes, and then one party decided to initiate a TCP connection before the 3 minute mark, the currently open session would be used. However, because it was after the 2.2 minute mark, both peers would try to initiate a handshake upon sending their first packet. The errant flow was as follows: 1. Peer A sends SYN. 2. Peer A sees that his key is getting old and initiates new handshake. 3. Peer B receives SYN and sends ACK. 4. Peer B sees that his key is getting old and initiates new handshake. Since these events happened after the 2.2 minute mark, there's no delay between handshake initiations, and problems begin. The new behavior is changed to: 1. Peer A sends SYN. 2. Peer A sees that his key is getting old and initiates new handshake. 3. Peer B receives SYN and sends ACK. 4. Peer B sees that his key is getting old and schedules a delayed handshake for 12.5 seconds in the future. 5. Peer B receives handshake initiation and cancels scheduled handshake.
* timers: move constants to headerJason A. Donenfeld2016-10-191-11/+6
|
* timers: kill half-open handshakes after a whileJason A. Donenfeld2016-10-191-0/+4
|
* timers: avoid thundering herd for simultaneous initiationJason A. Donenfeld2016-10-191-1/+1
| | | | | | Since it's extremely unlikely for jiffies to be exactly identical everywhere, applying quarter second power of two slack not only improves power efficiency but also ensures that retries have a bit of jitter.
* debug: keep alive -> keepaliveJason A. Donenfeld2016-10-191-2/+0
|
* Rework headers and includesJason A. Donenfeld2016-09-291-2/+2
|
* timers: use more clear pow macroJason A. Donenfeld2016-08-021-1/+1
|
* timers: upstream removed the slack conceptJason A. Donenfeld2016-07-231-4/+7
| | | | | No longer do we specify slack ourselves. Instead we need to add it directly in the main scheduling.
* timers: apply slack to hotpath timersJason A. Donenfeld2016-07-101-0/+3
| | | | | | | | | | | For timers in the hotpath, we don't want them to be rescheduled so aggressively, and since they don't need to be that precise, we can set a decent amount of slack. With the persistent keepalive timer, we have something of a special case. Since the timeout isn't fixed like the others, we don't want to make it more often than the kernel ordinarily would. So, instead, we make it a minimum.
* timers: document conditions for callingJason A. Donenfeld2016-07-101-0/+8
|
* persistent keepalive: use unsigned long to avoid multiplication in hotpathJason A. Donenfeld2016-07-101-2/+2
|
* persistent keepalive: use authenticated keepalivesJason A. Donenfeld2016-07-101-2/+3
|
* timers: rename *authorized* functions to *authenticated*Jason A. Donenfeld2016-07-081-1/+1
|
* persistent keepalive: add kernel mechanismJason A. Donenfeld2016-07-081-0/+23
|
* Initial commitJason A. Donenfeld2016-06-251-0/+168
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.