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 673403CB49 for ; Mon, 20 Mar 2023 22:15:17 -0400 (EDT) Received: by mail-wr1-x42e.google.com with SMTP id o7so12211096wrg.5 for ; Mon, 20 Mar 2023 19:15:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679364916; 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=7nMrzcsf2nENH1GnSnDSF+ucz7GErHvUF9NuOuWq2Fg=; b=mYJJvaFL1gZAAuHLpxzsxqkz+jTU4frJEQbKPztYR0DlSHYw2mXOYwgR8IVgg4Vf/W rEOjKtwzKJ/dcogSfkP3HhShmkqD9wElfKVux1pcSPVSVHIZSUhDNXmA5aM5abzlTfVH Uqnbn+YyXKE7+wCIrDCLbCwk4cyNkL3xl/ATbK8j4qXjR7Ae7y1/K1DvpfanjEAMGoS3 0/BQ2W+N/pil1BNqZX5QDqxombrZuZT9BcKZz+uQRKncYgZNPd1XS2SQK2ZqE3ji7bEG PAM9lO6doCKsoAQzbxQAaSOqL0LLoVyiKRaDt+CKRLh7t1O1dR7L5PO3RPbZrmdodjrf 5vsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679364916; 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=7nMrzcsf2nENH1GnSnDSF+ucz7GErHvUF9NuOuWq2Fg=; b=Fu41m1hvuC6JJeit/p01y4RYN5/Ci7jHhDsWa7qeFeMVbXg4HrAx6eLuWl/+mRzmB1 nV10sJOUb/rE5QNM53Y0GMHF3j6t+DlEjtgqdC+t9TOHcUb8kQoAgNSUWtuvjUyx8Lt7 QHg3yjBVaWxYAoQB6gb7FEw5YIXkCHhVTQMQYEl/epnLGrTTjiprI73UFuhCVFLjjiBc q47j8oW5NLw96OrKyKonS5oFegGKvQG3IGZ2dhGZrjOVv4ievs3uDvIQksRRKJf40lx+ 0v2uKDlKS+3ST/ueW+6YSqbEPnS+amOgDDc27ErPIrbI5NowXM2X3MMgNFU/3EhDdU8s NaOA== X-Gm-Message-State: AO0yUKXRWUj4WJQ4vsi5mM/3cy1P8UGuyIbGobfpeXv7KxeecVcT+85b eD1gOeUtwnOhmseUZtsuH9rgwkkKAa5A4GiSLaLy7NRbEwk= X-Google-Smtp-Source: AK7set9m3Yr9UHM+IZXbv0aks7tprpUSOkknPMPwVCmNsVyBZLB+EZSMXqlvbTWkILWoyGSgKszIDB3sQhzqlMKdqcs= X-Received: by 2002:adf:e490:0:b0:2d7:8d9d:a2b9 with SMTP id i16-20020adfe490000000b002d78d9da2b9mr268521wrm.13.1679364916096; Mon, 20 Mar 2023 19:15:16 -0700 (PDT) MIME-Version: 1.0 References: <9EF819F0-E158-4CCB-A2AF-FC3430D637BF@ascendency.net> In-Reply-To: <9EF819F0-E158-4CCB-A2AF-FC3430D637BF@ascendency.net> From: Dave Taht Date: Mon, 20 Mar 2023 19:15:05 -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:15:17 -0000 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, real= ly 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 Shap= edDevices.csv given the following parameters: > > 1. I have three very asymmetric WANs that connect to my pfSense Edge rout= er/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 tr= ansit 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 bridg= e 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 t= o 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 --=20 Come Heckle Mar 6-9 at: https://www.understandinglatency.com/ Dave T=C3=A4ht CEO, TekLibre, LLC