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 CEDC03B2A0 for ; Thu, 2 Jun 2016 08:29:29 -0400 (EDT) Received: by mail-lf0-x244.google.com with SMTP id 65so4967359lfq.1 for ; Thu, 02 Jun 2016 05:29:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=U8ZPjPxwYTR+64ixOncZdnHcPh9bGEWKFctz1AZMod8=; b=NSEFOuI9Au5xQf2LUNvzPeAR2pGOHRF5T4JSAD/gYzoTuCEPhFMdBCMN/h5EfnwCN5 MxAZDKscXy2nwPIFTkBEwtDryUscwUy1PiCSm4vQE3qbQEpYPHqdhzPKlftBbuIQla8O 1YIUX1z1bwjeAgpjT3Z8mWOmUXP6hsQ2EBdfFFdZX5CQS0Xj6j4Ys3PUFGtS+y4Q4+sZ q2AM2yVduvR+/+ca4hj6DEXii7ns+EyYZKwSz5hQwuiIMN0yzOUdAsuVQ3v2F7PPujYj H/2ehTWRpmkYYuzXOrIqNaN66g+jmxweNo+MC4S+FPGLgYE48BgjH9QMo4ARcuSB6IGR yIRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=U8ZPjPxwYTR+64ixOncZdnHcPh9bGEWKFctz1AZMod8=; b=hgw5IGZ3G9qiP51XTxWSvUqCglddGe++KOESDi8er2u7QNWgeh6gIE5sztTLUBSJHR uK6WwsDgEBasC/o0ukQjYxnaQbLAbSQaggeNF4eKRVR5yQMo7zRXEFy0uuCv10OPT2vB pNya9tZqkjZdPLQdrMaLYiYpr9awZSTCOkfool/Q58fRYizr+ob0X7o5Z20Cu9yQZ3lv 11kTwTyvU7jZj7Rbbsg0FW9XId2E40X2ZiCTlVE6Y5mRdoD6MohOoLzkmNMRl5VzaqzL 0ua/39pt0xX7W2iKtB4kCOaCbXjQ5zuqngENMblHMm39rkFZC+fgKWlCYK73yPNw4tqJ y+lg== X-Gm-Message-State: ALyK8tIVkKweWzXM7rii+jBYEbhz/XtMXp8ECu3KzHj2ZpKwOW5LDIYw6MsCD8jED1eOeg== X-Received: by 10.46.1.33 with SMTP id 33mr3770910ljb.44.1464870568457; Thu, 02 Jun 2016 05:29:28 -0700 (PDT) Received: from [192.168.100.11] (37-33-56-85.bb.dnainternet.fi. [37.33.56.85]) by smtp.gmail.com with ESMTPSA id g70sm3544142ljg.43.2016.06.02.05.29.27 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 02 Jun 2016 05:29:27 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Jonathan Morton In-Reply-To: <57501404.5010704@darbyshire-bryant.me.uk> Date: Thu, 2 Jun 2016 15:29:14 +0300 Cc: cake@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: <6A7C70EE-906E-4624-A84A-645ED4530A07@gmail.com> References: <57501404.5010704@darbyshire-bryant.me.uk> To: Kevin Darbyshire-Bryant X-Mailer: Apple Mail (2.3124) Subject: Re: [Cake] flow dissector idea/enhancement - help 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: Thu, 02 Jun 2016 12:29:30 -0000 > On 2 Jun, 2016, at 14:09, Kevin Darbyshire-Bryant = wrote: >=20 > Cake uses the flow dissector API to do flow hashing...including per = host flows for dual/triple isolation. The unfortunate bit is that the = qdisc inevitably gets placed after packets have been NATed on egress and = before they've been de-NATed on ingress. >=20 > When mentioned before Johnathan said "flow dissector ideally needs to = be tweaked to do this" or words to that effect. >=20 > I'd like to progress that idea...the thought of me kernel programming = should horrify everyone but really I'm asking for help in being pointed = in the right direction to ask for help...and go from there :-) I believe Linux does NAT using a =E2=80=9Cconnection tracker=E2=80=9D = subsystem. That would contain the necessary data for resolving NAT = equivalents. I don=E2=80=99t know how easy it is to query in a qdisc = context, though. - Jonathan Morton