From patchwork Sun Apr 7 10:37:00 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: =?utf-8?q?Linus_L=C3=BCssing?= X-Patchwork-Id: 17880 Return-Path: X-Original-To: patchwork@open-mesh.org Delivered-To: patchwork@open-mesh.org Received: from open-mesh.org (localhost [IPv6:::1]) by open-mesh.org (Postfix) with ESMTP id CCCE681017; Sun, 7 Apr 2019 12:37:17 +0200 (CEST) Authentication-Results: open-mesh.org; dkim=fail reason="key not found in DNS" (0-bit key; unprotected) header.d=c0d3.blue header.i=@c0d3.blue header.b="Tx5PjMMB"; dkim-atps=neutral Received-SPF: None (mailfrom) identity=mailfrom; client-ip=2a01:4f8:171:314c::100:a1; helo=mail.aperture-lab.de; envelope-from=linus.luessing@c0d3.blue; receiver= Received: from mail.aperture-lab.de (mail.aperture-lab.de [IPv6:2a01:4f8:171:314c::100:a1]) by open-mesh.org (Postfix) with ESMTPS id E29D9806A6 for ; Sun, 7 Apr 2019 12:37:16 +0200 (CEST) From: =?utf-8?q?Linus_L=C3=BCssing?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c0d3.blue; s=2018; t=1554633436; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=mMbaeVVchH6xAxe3zff2XqTZagNyOTF2ynfbzTm3cHw=; b=Tx5PjMMBlRfemzZqYY5Ja7UXLBCv2WVP/8DKK2yu5I7Sbro/D42pQPL3rpkI//SwhNAe3p gODEAbHOhpiOualcnytEgVzWa0b4/NKKkT6ji4b+96CHPAPnrjrcyrmPcASckJ+5+OlORq 1hKVLpPq1Zrzi3aYuzZEmXK66t6cFBV5Ch+mJNXA5JjBP/kJF1M05bj56g5N1iMIE1DjM3 jrsDwZrYS3YJ1aYYhbGAHLJoRzSm6h42lQIWY7c3CmnpXEv2mSCePQ+cbjLXxIySLfYVO3 bJiaRmFW3pgauSdw4VzDMIwmPk95+7Jm47zUwmvmTOO3MAMR9dafgdy+2E2ZSg== To: b.a.t.m.a.n@lists.open-mesh.org Date: Sun, 7 Apr 2019 12:37:00 +0200 Message-Id: <20190407103702.30435-1-linus.luessing@c0d3.blue> MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=c0d3.blue; s=2018; t=1554633436; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=mMbaeVVchH6xAxe3zff2XqTZagNyOTF2ynfbzTm3cHw=; b=ZbZ5pgY51w3uTvco/Q65ur21u7lYnrTDtyYzfaNjmAOXac4tPqJLlwM2ntU4wqtJoaiLhM TLr+6Ptr+m71unvXsqpjwCQO3FjilXrJxY9wdSU0x0AinPZxI+KPHwx+l5XSsIGWfBJAgC PYIUOQg9bKE0nZVXeGMm7VZpHjpgrXBkB5KvbsL1/fNGqcNw2bIfpQpAhYRAbQPHxLRXMW JXayAMEinpFbXTroPacUYzmksPaJtI5G/Nzcj1O7kPUPEob/+fA0rFHnNjJkI5NqMJO5Tr uzpeWURjapuSaupR3hV2UegTAXJpYM7tAsaNygPPskL8BvGrBL8L5AyEhFxCFw== ARC-Seal: i=1; s=2018; d=c0d3.blue; t=1554633436; a=rsa-sha256; cv=none; b=GBm703FVo3rluDPuF4xTqUXnqT98EshT2MYWKSQWQGrbi3jaE7thvzm3Q5Mk7wT0j6x/IZ LNO4QkGsV12b6INOQSfRKd1Vzl+WaJi9JEM1qtVBPMqFFPPP4kCPRYW52F3Hi3VGb/MnVY l7NCp0qS+ukJqlWboQObbi9CGzMqkYSHutAvTPylRO64rMKY70jhy8juqlnNTTyp7aV7Ei wqGtziE2XQpTQ10TiMkU8KD0J1bHiUIHnloU/7xec6Q0lajUxKpu3qpof26FQBpWT9qmiP tLOfPyW8PGsXQak9SChZos4HTLrimb4rm9jH3v2q4kwVXK808ez7+RhfuSrYoA== ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=linus.luessing@c0d3.blue smtp.mailfrom=linus.luessing@c0d3.blue Authentication-Results: ORIGINATING; auth=pass smtp.auth=linus.luessing@c0d3.blue smtp.mailfrom=linus.luessing@c0d3.blue Subject: [B.A.T.M.A.N.] [PATCH v3 0/2] batman-adv: increase DAT DHT timeout X-BeenThere: b.a.t.m.a.n@lists.open-mesh.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking Errors-To: b.a.t.m.a.n-bounces@lists.open-mesh.org Sender: "B.A.T.M.A.N" Hi, This is the third attempt to increase the DAT DHT timeout to reduce the amount of broadcasted ARP Replies. To increase the timeout only for DAT DHT entries added via DHT-PUT but not for any other entry in the DAT cache the DAT cache and DAT DHT concepts are first split into two separate hash tables (PATCH 1/2). PATCH 2/2 then increases the timeout for DAT DHT entries from 5 to 30 minutes. The motivation for this patchset is based on the observations made here: https://www.open-mesh.org/projects/batman-adv/wiki/DAT_DHCP_Snooping Regards, Linus --- Changelog v2: formerly: "batman-adv: Increase DHCP snooped DAT entry purge timeout in DHT" (https://patchwork.open-mesh.org/patch/17364/) - removed the extended timeouts flag in the DHT-PUT messages introduced in v1 again - removed DHCP dependency Changelog v3: formerly: "batman-adv: Increase purge timeout on DAT DHT candidates" https://patchwork.open-mesh.org/patch/17728/ - fixed the potential jiffies overflow and jiffies initialization issues by replacing the last_dht_update timeout variable with a split of DAT cache and DAT DHT into two separate hash tables -> instead of maintaining two timeouts in one DAT entry two DAT entries are created and maintained in their respective DAT cache and DAT DHT hash tables