From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x244.google.com (mail-lf0-x244.google.com [IPv6:2a00:1450:4010:c07::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id B83D33BA8D for ; Tue, 31 Jan 2017 16:14:09 -0500 (EST) Received: by mail-lf0-x244.google.com with SMTP id h65so34807904lfi.3 for ; Tue, 31 Jan 2017 13:14:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=O90bk0LymqBy+CdFk0JoChdr6j/0lFYDvljL7AvJSO0=; b=PXEyCl6ZSHX0WJdul8ikfUbf/0WyZ5WZNTJdFKyf3CeCyPfYzti9Nj3jfCoisn+rrF hoHXvS20HpZF98TokP7O/1rD4IhLXjB1gmJXAr5RWnzizdM7X8v6XUUocZjoJM0qvEpE rQPybc/TpuuV6ZZlVPDAP3sWbuE1GNJA/shlENG0D70Pj6X+AUQS6CqpF0Z+dIZlSS9K Ug7Mvc8B1Tqx/3mzhcgZeaVnCozQuC6yTsHVlyM04NH/YU+pRXgfwK1YJiKCOMKw0tTO uFjZy2DEVrUYwV5jvBwSOUQ/VOJUK/XiUHmFsT9lmPbYkp/SWf1oh+gHG3GJB+eFVjOt qBFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=O90bk0LymqBy+CdFk0JoChdr6j/0lFYDvljL7AvJSO0=; b=V2b1Vbb1/BQPpKSyrCTXDJyeeNmKy779LjQiYszN6Lq9bQjX9lo2VCrONLL+sWcXDl U74Lrf6avElyH3HUt1MUijYXNJWChMFmKlgHHlB55nHxsH9fxspQiaFob6ACL+KdqEUo j89wvJ1PiI8N57/MGrHfOOygz7zwKgr/KkplFjCaXwRY41jG6hnkYaP28vTMp8txvTsj cRdavK5/A+3ofW4lr4W2+BIfqKd4cIavzK5T5aD6x9ixUPRXly4oIjXXGEX8ZotjA7v8 Rgwl6xOy+xQITRIDdoVIU7GaL2bhJ973hi+77rLnJuQMDWZ20RW3rSqy7FXr8xpW6tjN Omog== X-Gm-Message-State: AIkVDXL50Bxy1rNJxHIPBs1wQrj7CHa1TClhX1hqlkKmktfvBYxEdUOdVF6FbBHHRouqHg== X-Received: by 10.46.5.130 with SMTP id 124mr11273191ljf.17.1485897248414; Tue, 31 Jan 2017 13:14:08 -0800 (PST) Received: from [192.168.100.16] (37-136-45-245.rev.dnainternet.fi. [37.136.45.245]) by smtp.gmail.com with ESMTPSA id k127sm4879929lfg.10.2017.01.31.13.14.06 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 31 Jan 2017 13:14:07 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: text/plain; charset=utf-8 From: Jonathan Morton X-Priority: 3 In-Reply-To: <1010949359.501064.1485874182374@webmail.strato.de> Date: Tue, 31 Jan 2017 23:14:05 +0200 Cc: cake@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: <6BA19F35-E3BB-48C4-9010-2153908E1DFA@gmail.com> References: <1010949359.501064.1485874182374@webmail.strato.de> To: Felix Resch X-Mailer: Apple Mail (2.3124) Subject: Re: [Cake] conntrack lookup continuation X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 21:14:09 -0000 > On 31 Jan, 2017, at 16:49, Felix Resch wrote: >=20 > Since we now already do the conntrack-lookup for the nat keyword, = would it be=20 > expensive to implement a kind of internal conntrack-mark-and-restore = by cake-tin? >=20 > E.g. when traffic leaves throu canke tin#x, the conntrack entry will = get a fwmark and return traffic is put in the corresponding tin/bin on = the ingress cake. That=E2=80=99s an interesting idea. At this point I don=E2=80=99t know = how easy it is to implement, though. Certainly we need to clean up some other things first. - Jonathan Morton