From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 31B573B25E for ; Thu, 9 Jun 2016 19:11:58 -0400 (EDT) Received: from [10.137.13.46] ([95.91.197.216]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LrIPo-1baCw41GmK-013AEl; Fri, 10 Jun 2016 01:11:56 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: moeller0 In-Reply-To: Date: Fri, 10 Jun 2016 01:11:39 +0200 Cc: cake@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: <0B4652E3-F061-479D-8BB3-EA0193333A51@gmx.de> References: <7409a52d-8c81-25f0-e070-c7638fdf9d83@gmail.com> To: Dennis Fedtke X-Mailer: Apple Mail (2.2104) X-Provags-ID: V03:K0:nnOauXFSpqsCXcodd8V/C37j8CnmRnrC+NuvhAjnudcnUtPoPp8 9i7DVo3Aa8RnykEgGO2oajrnt0g+tKdQZ10Y6iM/n0wqYv0vmDNgVn1/TNDCwVLow4cAbo/ AowefWrqBoHiLiHL2YgXdA4LMLXhIcEkAxI7jmOy2vqg2Ar8gXQw8r069UGHvri924PmF/q U7CU801ZsFwr1yCn7sXKQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:SB1Y4Xz2BXM=:iiMlVwJDl7/pFpcKaFAmea 8Gxy1ixKIJNJNKw55SNKxgupQhWsH5Xh7nm3mtRZdA9a81dygRhOSkBM0/k9eH+OznmHdgLN+ Zk7PYY2Ej5Bb3CVVmruFOgYqgEyMApNc/WkDxenQ1rLebfxcSHe/wLmzISCSetEfjC8e2nytk yP/iNka3sIbmcQCdgFFPjGKjDDcAwPsQrUA2NclQsvR/c6/3AdtKaNpYex0asQ102Yjm7z+ey Oajcxz0lOP5wdY/xEyN6YurECYmUlBQZorrh46DJoOzQWiPwywbvkTNtknAThWYVq3iD2zJwk d9mgms8pOUNE7ryJrF5C6ZPVKJ/QSr9JNiJAm1pQmS4nraBsFJHNQzDxxG3uyrAORv6P2LHkf dmjmUh5HYI/OULywvuyv1tcdqUGXfzAU28xgjJttyeztgM4o0V+GtKS+VeXYCOCLz1T4S7ipz LNyuoGKUErHQ64Ry1eMH/hd8VUOLVddyLo4SbL3/Yzn0QWQ8lEKgSd9fiPTqwNAedtw7zHxzG XYnCtyj52w45TuFntu1bs8bU44y6sloFhAXTJm9EnSTXqET1omM8BWeepUPtjp98lIYcwmreD iHMnWWCR8aWHLivp49W/5N0mdJum1R4wqWkERwW6RNGZ4GQo3sbv02hr3Nqnf+PQih/B3pw6B bWVr2sUzbvyS7TFqX/Y2NymcAa3bK7J4xfBewwTss0putWAlb6bff5ccvzLS+nuySm69XRQnz aNByP2a/pkIlgRdxie6HBV8emXP+FsdihNgZ9+5gcfcPgmwLJUMpaiIyB2vBcLZ1HpMliOI2b wCotQu50JCYQ8ZGQQWNnDaI29X04Q== Subject: Re: [Cake] New to cake. Some questions 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, 09 Jun 2016 23:11:59 -0000 Hi Dennis, > On Jun 10, 2016, at 00:45 , Dennis Fedtke = wrote: >=20 > Hi Sebastian, >=20 > thank you for your answers :) >=20 > The ATM overhead detector script is currently running. > I read the wiki about it but im not quite sure how to interpret the = plot. > I mean what info should i read from it? maximum packet size? The relevant number is reported as =E2=80=9CEstimated overhead = preceding the IP header=E2=80=9D in the top part of the second figure = created by the script. But that is only relevant.useful if you see a = nice step like plot in figure 2 as well ( the second figure in = https://github.com/moeller0/ATM_overhead_detector/wiki as positive and = the fourth figure as negative example. > If yes do i set the overhead in cake? Or do i set iptables to clamp to = new mtu/mss? If you use plain cake and you know the numerical overhead (NN) = the easiest is to add the following to your cake invocation: =E2=80=9Catm = overhead NN=E2=80=9D Please note that if you use cake on an ethernet interface the kernel = will already account for 14 byte of ethernet overhead, so if the script = told you 44 as actual overhead, you use =E2=80=9Doverhead 30=E2=80=9D to = address that. If you use a pppoe interface the kernel will most likely = not add the 14 bytes for you, so then you would use =E2=80=9Coverhead = 44=E2=80=9D (I excluded the atm option in the last examples for = clarity=E2=80=A6) >=20 > Regarding UDP paket dropping problem: > I just read some forums and users stated that under heavy load cake = starts to drop udp packets which causes lag ingame. > My idea was to set ingress/egress to diffserv4 and apply the EF dscp = mark on those packets. Ell, not a bad idea, but often the problem are in the incoming = traffic, and unfortunately with the ifb we use we can not use iptables, = but only tc, and remarking with tc is unpleasant. > Will this even work? if yes how to do this? iptables? No, you wuld need tp use tc. >=20 > ipt -t mangle -A PREROUTING -p udp -m multiport --ports 5000:5500 -j = DSCP --set-dscp-class EF >=20 > Like thia? Is prerouting correct here? (Taken from layer cake script) This will affect outgoing packets and might be a good idea in = your specific case. BUT why don=E2=80=99t you try the default behaviour with specific rules = and tricks and report success or failure back to us, after all the = fastest/easiest classification is one one does not need to perform at = all. >=20 >=20 > For the squash and wash feature. > Im asking because if i choose to squash in the advanced options of sqm = scripts. > The dscp fields/marks will be overwritten by iptables to 0 = (besteffort). (layer cake script) > So then it makes no sense to manually set dscp fields/marks or? (Or = even setting diffserv) No unfortunately on ingress cake sees the packets before = iptables, so the effective behavioral emulation of wash/squash by cake = is to set ingress cake to besteffort (basically cake ignores the dscp = field which functionally is identical to all packets having the same = value). The squashing by iptables just clears the dscp marls so that = internal networking elements like potentially wifi liknks are not = confuzed by the dscp information. >=20 > Did i understand this correctly. Per rfc isps should not provide dscp = fields/marks? Not exactly, per RFC DSCPs are only ever valid/defined inside a = DSCP domain and your ISPs domain ends before it reaches your CPE. Since = you have no control over your ISPs markings, they can be very much not = like you want them to be (Dave That reported that his ISP re-mapped = almost 1/3 or so of packets into the CS1 background class). So it is = recomended that each DSCP domain re-mapps the code points at its entry = point, which in your case is your router=E2=80=A6 Best Regards Sebastian >=20 >=20 > Thank you. >=20 >=20 >=20 > Am 09.06.2016 um 23:30 schrieb moeller0: >> Hi Dennis, >>=20 >> let me start with a disclaimer, I am not the best information source = for cake on this mailing list, but I assume the others will chime in if = I say something questionable=E2=80=A6 >>=20 >>> On Jun 9, 2016, at 22:58 , Dennis Fedtke = wrote: >>>=20 >>> Hi >>>=20 >>> Currently im running lede + cake + sqm_scripts and i have some = questions: >>>=20 >>> 1. What is considered the =E2=80=9Coptimal" setup atm for cake? >> The same as without cake; really, proper per-packet-overhead = accounting is important for bandwidth shaping, especially for ATM -based = links. I would recommend to follow the method on = https://github.com/moeller0/ATM_overhead_detector to m\empirically = measure whether your link uses ATM encapsulation and what exact overhead = is in use. >>=20 >>> e.g. which cake script should i use piece or layer cake? >> piece_of_cake has only one tier of priority, while layer_cake = currently offers 4. Packets are put into the different priority bands = based on the content of their TOS/DSCP filed in the IP header; if this = is greek to you, I guess piece_of_cake most likely is what you are = looking for.. >>=20 >>> 2. Recently squash and wash was removed. >>> But the sqm scripts were not updated. In the advanced options should = i set that the dcsp marks are kept? >> This really is an implementation detail that has no immediate = effect if you choose piece_of_cake as typically only the bottleneck is = sensitive to DSCP based priority banding. (Typically in that if you are = unlucky your WLAN will use the DSCP marks to move packets into 4 = different priority classes, which is fine if you want that, but bad for = not sanity checked packets coming in from the wider internet (one is not = supposed to assume incoming packets have sensible dscp markings as per = RFC) that is why the wash/squash option is missed by some of us, = independent of the fact that it was a layering violation). >>=20 >>> 3. Should i use advanced options in sqm scripts and set = triple-isolate + diffserv8 ? >> If you understand what these options do and believe that this is = the best for your network go ahead, otherwise=E2=80=A6 The = triple-isolate option will try to be fair to host_IP addresses first and = then for each hostIP fair to each flow, but for that to do something you = will most likely want this requires that cake sees internal IP addresses = of your end-hosts. In the typical configuration with SQM on the WAN = interface of a NAT router all internal addresses are replaced with the = external IP address of the router it self and triple-isolates per host = fairness will pretty much be equal to per flow fairness (not exactly, = but in essence). So if you want to try tiple-isolate or its better = defined brothers dual-srchost and dual-dsthost you would need to = instantiate SQM on an internal interface like LAN. But then the = direction of ingress and egress from the routers perspective changes = with regards to the internet download and upload direction and you will = need to put the internet upload bandwidth into the download field of the = sqm GUI and vice versa. Also SQM on an internal interface will also = shape internal traffic over the same interface, and that often affects = traffic to and from the wifi/wlan radios to the lan switch=E2=80=A6 (I = guess you would have preferred a shorter less vague response, but such = are the constraints=E2=80=A6) >>=20 >>> 4. Is it recommend to enable diffserv on ingress? >> If you trust/konw/have confirmed that your upstream (ISP?) sends = you sensible and reasonable DSCP markings by all means enable diffserv = on ingress. But the default assumption should be that your upstream used = a dscp mapping that only makes sense for them and not for you. >>=20 >>> 5. Is there still the udp packet dropping problem? e.g. games that = are using udp. >>> If yes does it make sense to apply diffserv classes manually? How to = do this? >> I am not sure what you mean, but if you test this and have some = findings please report here=E2=80=A6 >>=20 >>> 6. is the autorate_ingress still under development? >>> This very interesting feature. especially for docsis networks. Will = it be possible to set target ping time? >> The last tests did indicate that this feature is not ready for = primetime at least not on typically fixed bandwidth links and I assume = docsis links are fixed enough. >>=20 >>> 6. What difference does it make to set a different rtt? >>> Setting lower rtt will reduce download speed i guess but will it = allow better ping times (because of lower downloadrate uh)? >>> What happens if rtt is set way higher? >> With the RTT parameter you in essence specify how much time you = give the endpoints of a flow to respond to a congestion signal (ECN = marking or packet drop) if you select this way to small you will = sacrifice bandwidth, if you set this too high you will accumulate more = latency under load. The good thing seems to be that this does not need = to be terribly precise, order of magnitude correctness seems to be = sufficient (at least in base2) >>=20 >>=20 >>> Thank you! >> I am sure the real experts will also chime in=E2=80=A6 >>=20 >> Best Regards >> Sebastian >>=20 >>> _______________________________________________ >>> Cake mailing list >>> Cake@lists.bufferbloat.net >>> https://lists.bufferbloat.net/listinfo/cake >=20 >=20 > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake