From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 44C953CB49 for ; Mon, 20 Mar 2023 22:17:21 -0400 (EDT) Received: by mail-wr1-x42e.google.com with SMTP id v25so8745984wra.12 for ; Mon, 20 Mar 2023 19:17:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679365040; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=iZZQ9Z+ArLFWBnsXIAx5TOwQI3oRRts2r0mcx3BdI+w=; b=n5htpAGpOZnvqaU5z0bIcJGh8VqoZ15EZ6fL9IRG9XthxW1muC7POvrXjayCMnJpcq MNFgSUXV+4JGABGXffjkIBRumg7Q2McKKOyEcuXpT0i3KMqDDckEpvG7QBSqVsffznsi RYC0Rf1hLE74coleJYDs5LQWSkDKapA74co5npVprCJlC4GqZ4mPtg2Y1+zqyKIFTbF3 7dNpGbf+KyAaref2wktj5XRK8u9PXbTLuTtVdX8tTwtCdq6bYkcpQ7XeeNAfsaxL/TrL YfjAJg6wAP4YMi+xLlLj2zO/8Qdf2fP3VdO5VS3ZzzGwfTmkCY/k80Kn1lo9Wv9uqTSw Es3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679365040; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=iZZQ9Z+ArLFWBnsXIAx5TOwQI3oRRts2r0mcx3BdI+w=; b=TynUCOXkFu5DgwQWWGecmxBO3nX2KPH44AS0aja1w6pTAo1O2IEOCcHKt9BpBt7qTq T2rwBj2gozMqTjQsoeklh+cBC/Km5dya9RLzYp2iETnZpni6GADNF2gD+UTRYfBE8uY0 5jhgcVO096/EVtCkzEP619s+6HRH88fjtDJB2FDlaerri1G2xcjZqWzd+w0bb7lbhlsz yVU2S6cssNBfL87/khv7zI6+C8l3A89EuY+ic/Uv/6RalOQ1i31HUQ7oZ8BGRWH9DVC/ S4bzKyrBmOH7CLVRGyS0dqdKascOX32ah5mUMaarTgGjWc3Gu0v63OGDTHODwSO13Jem HjLg== X-Gm-Message-State: AO0yUKVHLiuTowOnca2Qq+gaMW+rlKyku2XgQuQTJ+vvrjIua9Fjyvsz AgxfII4lGZJXVQNJmYXW528LDvaThoz5Y6/8rPEmrUzT8y8= X-Google-Smtp-Source: AK7set+IFY5Qexs/QJMVQkM9JmenW3KmgcAUKxIrNkovsbLjpQ914iHeM8xpmitPkDFdrNrL2YaERgvAremav8WwSPo= X-Received: by 2002:a5d:67c3:0:b0:2c7:3d2:fa20 with SMTP id n3-20020a5d67c3000000b002c703d2fa20mr231802wrw.13.1679365040170; Mon, 20 Mar 2023 19:17:20 -0700 (PDT) MIME-Version: 1.0 References: <9EF819F0-E158-4CCB-A2AF-FC3430D637BF@ascendency.net> In-Reply-To: From: Dave Taht Date: Mon, 20 Mar 2023 19:17:09 -0700 Message-ID: To: Mike Loiterman Cc: libreqos@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [LibreQoS] network.json and ShapedDevices.csv for Multi-Wan SOHO X-BeenThere: libreqos@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Many ISPs need the kinds of quality shaping cake can do List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2023 02:17:21 -0000 On Mon, Mar 20, 2023 at 7:15=E2=80=AFPM Dave Taht wro= te: > > The fastest way to get support is via the #libreqos:matrix.org > chatroom, although we also do github bugs and good ole fashioned > email. > > On Mon, Mar 20, 2023 at 7:03=E2=80=AFPM Mike Loiterman via LibreQoS > wrote: > > > > Hello, all. > > > > Really new to LibreQoS, but so far it=E2=80=99s been working really, re= ally well with my pfSense setup. > > So wonderful to see you trying it. Are you using v1.3, v1.4-rc2 or the > heimdall (v1.5) branch? > > > I=E2=80=99d like some input on how best to setup my network.json and Sh= apedDevices.csv given the following parameters: In re-reading what I just wrote, I misunderstood the topology I think. > > 1. I have three very asymmetric WANs that connect to my pfSense Edge ro= uter/firewall: > > a. WAN_1 - 1200/35 > > b. WAN_2 - 25/2 > > c. WAN_3 - 50/4 > > 2. pfSense connects to my Layer 3 Aruba 2920 switch via a single 10gig = transit link so: > > a. pfSense: 172.16.0.1/30 > > b. 2920: 172.16.0.2/30 > > 3. LibreQoS sits between the pfSense and the 2920 with 10gig layer2 bri= dge between 172.16.0.1 and 172.16.0.2 setup on an intel X710. > > 4. Behind pfSense I have the following VLAN layout: > > a. VLAN_1 @ 192.168.1.0/24 via WAN_1 > > b. VLAN_2 @ 192.168.2.0/24 via WAN_1 > > c. VLAN_3 @ 192.168.3.0/24 via WAN_2 > > d. VLAN_4 @ 192.168.4.0/24 via WAN_3 > > > > So, given these parameters, can anyone provide some general tips on how= to structure the two files? > > It doesn't sound to me as though you need much of a network.json. A > flat topology will suffice, unless you need to model multiple devices > further down the chain from VLAN_X. > > As for the upstream though, load balancing that is kind of painful and > more the domain of pfsense than libre. > > Additionally, shaping those upstreams properly is problematic, I would > probably use pfsenses's native fq_codel implementation on each of > those WAN interfaces to install an upper limit for egress but on > ingress... hmm... and in either case something needs to attempt to > direct the "right" amount of traffic through those interfaces. > > > > > > ------------------------------ > > Mike Loiterman > > Cell: 630-302-4944 > > Email: mike@ascendency.net > > > > _______________________________________________ > > LibreQoS mailing list > > LibreQoS@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/libreqos > > > > -- > Come Heckle Mar 6-9 at: https://www.understandinglatency.com/ > Dave T=C3=A4ht CEO, TekLibre, LLC --=20 Come Heckle Mar 6-9 at: https://www.understandinglatency.com/ Dave T=C3=A4ht CEO, TekLibre, LLC