From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2a0c:4d80:42:2001::664]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 1BA7F3B29E for ; Sun, 5 Feb 2023 17:17:39 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1675635457; bh=FH4ksNfvYIfaLMKGi65RKseBwBXNgFgBPSwVDLRUKwo=; h=From:To:Subject:In-Reply-To:References:Date:From; b=N29wfz/NCOZ7uImldfqqjw12JqUSqVBjalKlMH/PUkwd0NXbNE0fUKgutDOgD0w8J E/U4WODjk0nCu9lDcy7Ewgbe+3igxQgKc7t1YR4bi4+eDkNs++ifknrbskc4sjKZFf aobzrXYa+idS/dqvF+1Fhwagv71/l1ruBwoTpdX0eYImm1O7VgYMeVzgMlhTe+GFJK Lmnqbg7f715UDSViP07O8oACZxNBHU1iM0kmBYX6/GzvADxObs+E5MUYmFDETx8Z/Y WW52kFBKuTPSQwGexEI97F0DY1wfyWXSBZzgrCFiM7S65ZZJ5crs0t8z/EMeXZD5fd bl4u7FEfQEuQg== To: Dave Taht , Cake List In-Reply-To: References: Date: Sun, 05 Feb 2023 23:17:35 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87ilgfdaf4.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] flow dissection vs encapsulated traffic? 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: Sun, 05 Feb 2023 22:17:39 -0000 Dave Taht via Cake writes: > In looking how the code has morphed since I last looked at it, I found > myself staring at this bit... > > skb_flow_dissect_flow_keys(skb, &keys, > FLOW_DISSECTOR_F_STOP_AT_FLOW_LABEL); > > // so we have delved deeply into the packet at this point... finding > various encapsulations... > > then we get to: > > /* Don't use the SKB hash if we change the lookup keys from conntrack */ > if (nat_enabled && cake_update_flowkeys(&keys, skb)) > use_skbhash = false; > > This leverages skb_protocol(), which as best as I can tell just peers > into the *vlan headers*, > not deeper into the packet... > > Then we proceed merrily into the update_flowkeys code thinking it is > the outer type > (ipv4), not the inner, then dissect away, using a v4 union... > > Am I reading this wrong? Please tell me I am reading this wrong... I don't follow. What's the bug you are seeing, specifically? -Toke