From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vw0-f43.google.com (mail-vw0-f43.google.com [209.85.212.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id E1556200588; Wed, 1 Feb 2012 12:08:42 -0800 (PST) Received: by vbbfq11 with SMTP id fq11so2224887vbb.16 for ; Wed, 01 Feb 2012 12:08:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QTHAaIxmsnKnVszwyWF9SOcE2Iv6ZMznJhukvop6luc=; b=JTdQchsCH3RpB7tfLlAaJ6WeB69l8y7wFyVmbEOxp3+Co8zqFt5Mp5kLD2KhyGPAeR T0S2aclNEorWSyba8LO/TWWangNkPWLK+4wWh6kOaf3sPXVesUp3aZmBExnvo4dYwMKu njovw4LnmrDqge9XCgMa0r5ZgxJucLOTjyDoM= MIME-Version: 1.0 Received: by 10.52.22.143 with SMTP id d15mr3884vdf.18.1328126921911; Wed, 01 Feb 2012 12:08:41 -0800 (PST) Received: by 10.52.165.165 with HTTP; Wed, 1 Feb 2012 12:08:41 -0800 (PST) In-Reply-To: References: Date: Wed, 1 Feb 2012 15:08:41 -0500 Message-ID: From: Justin McCann To: Dave Taht Content-Type: text/plain; charset=ISO-8859-1 Cc: cerowrt-devel@lists.bufferbloat.net, bloat Subject: Re: [Bloat] Testing Queue models X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 20:08:43 -0000 On Wed, Feb 1, 2012 at 12:12 PM, Dave Taht wrote: >... > Even getting 1/d is hard because the filters can only use IP and IPv6 > addresses, so a device issuing traffic on both ipv4 and ipv6 can get > twice what it deserves in terms of bandwidth, or more if it has > multiple ipv6 addresses. > > My preferred solution to this (and part of the wireless problem) is to > sort things out by source mac address. How to do that, remains a > mystery. The way I'm leaning is to invent some sort of "src mac-to-id" > filter that is global router-wide. A friend and I were discussing last week how each device on an IPv6 network can and will have multiple addresses, so classifying becomes a bit trickier. But I guess most devices are supposed to have one (ha!) /64, so you can ignore the lower-order bits? I assume that sort of IPv6 alias resolution is a solved problem already...? It sounds to me like you want to assign each device its own netfilter MARK, and mark each packet (by MAC?) on ingress, and then use the mark plus any other port/protocol selection you want to put it into the appropriate queue. > I tend to view (in the home) as having 1/u network performance as the > ideal. There are exceptions to this, notably video vs. say, > bittorrent. A clever way of getting closer to 1/u might be to sense > for more recent DNS queries and move that to a more interactive class. You might try assigning each device to a user, and then marking as above, assuming only one user at a time on a device. I guess that doing this would address (in the local/home network) what Bob Briscoe was getting at in our earlier thread: "Since 2004, we now understand that fairness has to involve accounting over time. That requires per-user state, which is not something you can do, or that you need to do, within every queue. We should leave fairness to separate code, probably on machines specialising in this at the edge of a provider's network domain - where it knows about users/customers - separate from the AQM code of each specific queue." Justin