From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 860513B2A2 for ; Thu, 31 Mar 2016 07:49:39 -0400 (EDT) Received: by mail-oi0-x22c.google.com with SMTP id o62so56487490oig.1 for ; Thu, 31 Mar 2016 04:49:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=rk27arm8CxsgSQfJyJMpCERYn9uzh8HpZlnYPsAw81o=; b=vKoGrQ8tjOmIAGGs0m2er+wz9YFe/sOemxYuUKEtYIrBaQTJF55JFposNnPnlHcjrt dPZPSYfJ3dlmvoMGkW2uKK8Is875iLNiuvTcw5gVuM0AavbIZuTQ11GqwdaGyhhbIh5q kfYZsoXjw4/2SWXqa8thCY7YHWah007jsgeIwKj+e5MyWOj7+9FIhAx2z9b7MwNn9V04 3jHsSXRIuaaJos5qYQriMJUQDQ5J60FyiKZH2wJ23XwubcGZlaurtWbDvaCNWLsBRfl+ yfb+ZtiyjubaIQ5k5C6J/NW8SZP2EQiMC/sB/o3gs+jiwu6Y80zNd3oy2a1edtTrUELZ 3C2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=rk27arm8CxsgSQfJyJMpCERYn9uzh8HpZlnYPsAw81o=; b=QNvL6uJr99FHv5SSuD378dRIeBE5sNs7qB521bgE9kn6URoTKb0WwHhGAjeHqJ24YE Y2U8QW1/wLKIhZrZpIEpzUS02GPmlcfHI888HXOK5irD1g0TRd0VnL7lt9LgTaUFtk9s l8SgjMLxLI4UzXHBm6Vbk3XpheTqNS7ympvgi3vz+WZxo4zhnGlKk+Idp/dnoU1cLwJb 65BQwOXFrVC+A0x8lVH9Vy8Uv5WguVazti3XKRCMMScki3PPp0XmtDhWg7Ppi2md/5+B ikPb5LwPva15hIT8hxKoqy+DKnYEVPgCpkOlpyKbaXPzMbGlHxmq8i8xea1X6nu3QKwQ znZg== X-Gm-Message-State: AD7BkJL/ivslXBtlPbCcL8N1t70lLuWaLP9x6YTY/AQmL1QJje1HgMZe32rAK0sl4rfjSof5T5p14KcWVk/tVg== MIME-Version: 1.0 X-Received: by 10.157.0.10 with SMTP id 10mr8516583ota.194.1459424978903; Thu, 31 Mar 2016 04:49:38 -0700 (PDT) Received: by 10.202.89.130 with HTTP; Thu, 31 Mar 2016 04:49:38 -0700 (PDT) In-Reply-To: References: <34953EAA-4C76-456E-9B9E-3A73D0DACCDE@gmail.com> <855E3354-30E6-4658-AF38-A0C1E92085CE@gmail.com> <66A00804-E571-4A44-BE3E-422F78C1F1F7@gmail.com> <198CD4FC-6BD4-40DA-BE2F-22BBBA1E204D@gmail.com> <20160328140104.3c55079e@xeon-e3> <87lh51bjx9.fsf@toke.dk> Date: Thu, 31 Mar 2016 17:19:38 +0530 Message-ID: From: Allan Pinto To: Dave Taht Cc: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , cake@lists.bufferbloat.net Content-Type: multipart/alternative; boundary=94eb2c03265871abb6052f56db92 Subject: Re: [Cake] cake separate qos for lan 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, 31 Mar 2016 11:49:39 -0000 --94eb2c03265871abb6052f56db92 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable >I gave this a shot, it doesn't route the packets back trhough the >underlying interface... >perhaps policy routing? tried it with policy routing too, packets get dropped when i point them to the ifb interfaces fast/slow. tried both dummy and ifb. ip route add $custip dev fast table 10 ip route add $custip dev slow table 11 ip rule add from $cacheip to $custip lookup 10 priority 10 ip rule add from all to $custip lookup 11 priority 11 im not sure if we can route it to ifb this way,( maybe only works with tc redirection?) as i feel that i have just set up a routing loop. i did not have time to recompile the kernel for imq, as jonathan mentioned but will try that too, did not try the ifb method mentioned by jonathan yet. On Wed, Mar 30, 2016 at 5:46 AM, Dave Taht wrote: > I gave this a shot, it doesn't route the packets back trhough the > underlying interface... > perhaps policy routing? > > TC=3D/home/d/git/tc-adv/tc/tc > IFACE=3Deno1 > > F=3D2601:640:4103:56c0:2ab4:103a:39c5:a43a > S=3D2601:640:4103:56c0:120d:7fff:0:647 > > ip link add $IFACE name fast type dummy # maybe ifb? > ip link add $IFACE name slow type dummy # maybe ifb? > > ip link set fast up > ip link set slow up > > $TC qdisc add dev fast root cake bandwidth 20Mbit > $TC qdisc add dev slow root cake bandwidth 5Mbit > $TC qdisc add dev $IFACE root cake bandwidth 20Mbit > > ip route add $F dev fast metric 1 > ip route add $S dev slow metric 1 > Dave T=C3=A4ht > Let's go make home routers and wifi faster! With better software! > https://www.gofundme.com/savewifi > > > On Tue, Mar 29, 2016 at 4:31 PM, Dave Taht wrote: > > An overall ISP in tc need exposed by this discussion is some means of > > mapping multiple ipv4 and ipv6 addresses and netmasks into something > > that will return a (key,value) pair. This would work something like > > ipset does, although what you would return is not "present or not" but > > present and a value > > > > insert customers 1.1.1.1,1 > > insert customers 2001:db1::/64,1 > > insert customers 2.2.2.2,2 > > insert customers 2001:db2::/64,1 > > > > then on the relevant path you'd set up the qdisc hierarchy and do a > > lookup into that to get the right number to go to the right cake > > instance. You'd also have to do a longest prefix match into the above, > > so a 1x1 hash won't do. > > > > the massive tc filter option discussed already does not scale to a > > random number of customers with randomly different numbers of ip > > addresses, types, and netmasks. Code like this must exist in dedicated > > devices already, CMTSes, BRASes, deep packet inspection devices, etc. > > > > Secondly, in the case of cake the hierarchy could just be a bunch of > > somewhat unassociated queues, not htb or drr, letting cake do the > > scheduling of deliveries. > > > > Regrettably I know of few ISPs that are actively using linux in any > > way they have sources to. I suspect a few dslams are linux based, but > > nobody's talking. > > > > ... > > > > Another way to maybe get there is to use the ip route functionality > > instead and send stuff to virtual devices layered on top of the real > > device. > > > > ip route add from :: to 1.1.1.0/24 dev dev1 > > ip -6 route add from :: to 2001:db1::/64 dev dev1 > > ip -6 route add from :: to 2001:db2::/64 dev dev2 > > ip route add from :: to 2.2.2.0/24 dev dev2 > > > > Then the reverse would be out one of two devices, one device > > configured for the "fast, local cache server", the other for the > > regular internet. > > > > solution too long to fit in the margins of this email. > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake > --=20 Thanx and regd's. Allan. --94eb2c03265871abb6052f56db92 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
>I gave this a shot, it doesn't route the packets b= ack trhough the
>underlying interface...
>perhaps policy routin= g?

tried it with policy routing too, packets get dro= pped when i point them to=C2=A0
the ifb interfaces fast/slow. tri= ed both dummy and ifb.

ip route add $custip dev fa= st table 10
ip route add $custip dev slow table 11
ip r= ule add from $cacheip to $custip lookup 10 priority 10
ip rule ad= d from all to $custip lookup 11 priority 11

im not= sure if we can route it to ifb this way,( maybe only works with tc redirec= tion?) as i feel that i have just set up a routing loop.

i did not have time to recompile the kernel for imq, as jonathan men= tioned but will try that too,
did not try the ifb method mentione= d by jonathan yet.=C2=A0



On Wed, Mar 30, 2016 at 5:= 46 AM, Dave Taht <dave.taht@gmail.com> wrote:
I gave this a shot, it doesn't route the packets = back trhough the
underlying interface...
perhaps policy routing?

TC=3D/home/d/git/tc-adv/tc/tc
IFACE=3Deno1

F=3D2601:640:4103:56c0:2ab4:103a:39c5:a43a
S=3D2601:640:4103:56c0:120d:7fff:0:647

ip link add $IFACE name fast type dummy # maybe ifb?
ip link add $IFACE name slow type dummy # maybe ifb?

ip link set fast up
ip link set slow up

$TC qdisc add dev fast root cake bandwidth 20Mbit
$TC qdisc add dev slow root cake bandwidth 5Mbit
$TC qdisc add dev $IFACE root cake bandwidth 20Mbit

ip route add $F dev fast metric 1
ip route add $S dev slow metric 1
Dave T=C3=A4ht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi


On Tue, Mar 29, 2016 at 4:31 PM, Dave Taht <dave.taht@gmail.com> wrote:
> An overall ISP in tc need exposed by this discussion is some means of<= br> > mapping multiple ipv4 and ipv6 addresses and netmasks into something > that will return a (key,value) pair. This would work something like > ipset does, although what you would return is not "present or not= " but
> present and a value
>
> insert customers 1.1.1.1,1
> insert customers 2001:db1::/64,1
> insert customers 2.2.2.2,2
> insert customers 2001:db2::/64,1
>
> then on the relevant path you'd set up the qdisc hierarchy and do = a
> lookup into that to get the right number to go to the right cake
> instance. You'd also have to do a longest prefix match into the ab= ove,
> so a 1x1 hash won't do.
>
> the massive tc filter option discussed already does not scale to a
> random number of customers with randomly different numbers of ip
> addresses, types, and netmasks. Code like this must exist in dedicated=
> devices already, CMTSes, BRASes, deep packet inspection devices, etc.<= br> >
> Secondly, in the case of cake the hierarchy could just be a bunch of > somewhat unassociated queues, not htb or drr, letting cake do the
> scheduling of deliveries.
>
> Regrettably I know of few ISPs that are actively using linux in any > way they have sources to. I suspect a few dslams are linux based, but<= br> > nobody's talking.
>
> ...
>
> Another way to maybe get there is to use the ip route functionality > instead and send stuff to virtual devices layered on top of the real > device.
>
> ip route add from :: to 1.1.1.0/24 dev dev1
> ip -6 route add from :: to 2001:db1::/64 dev dev1
> ip -6 route add from :: to 2001:db2::/64 dev dev2
> ip route add from :: to 2.2.2.0/24 dev dev2
>
> Then the reverse would be out one of two devices, one device
> configured for the "fast, local cache server", the other for= the
> regular internet.
>
> solution too long to fit in the margins of this email.
_______________________________________________
Cake mailing list
Cake@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake



--
=
Thanx and regd's.
Allan.

--94eb2c03265871abb6052f56db92--