From: Dave Taht <dave.taht@gmail.com>
To: Luke Hamburg <luke@lighthousecorp.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] BQL on the via rhine?
Date: Thu, 17 Jul 2014 09:25:02 -0700 [thread overview]
Message-ID: <CAA93jw4z_7DbU0oCZ9xD_CHKYkHoAD1ZxU=javR8HEp5p59MiQ@mail.gmail.com> (raw)
In-Reply-To: <431D2ED1-8A72-496F-9C53-1115BC9E5276@lighthousecorp.com>
On Thu, Jul 17, 2014 at 6:26 AM, Luke Hamburg <luke@lighthousecorp.com> wrote:
> The APU boards are wonderful pieces of kit. I've been running pfSense on them since they came out a few months ago and they've been extremely robust. Yes they are a little costly when compared to the WNDR3800 but it's still a good value imo.
Pfsense so far as I know has codel but not fq_codel, and people are
typically using hfsc + something to do qos. What are you using?
>
> Netgate sells a DIY kit that includes an unbranded case, power supply, and heatsink for US$179. The case has cutouts for 2 antennas as well which you can connect to a miniPCI WLAN board via pigtail. You can boot from the SD slot or mSATA and the 2GB of RAM is spacious. They also have a 4GB variant for $20 more.
>
> http://store.netgate.com/kit-APU1C.aspx
Thank you. The problem(s) that I'm trying to solve are multifold.
0) Have an existing stable distro that solves most edge qos problems
1) Get more hw with good support out there
2) have a device that can run htb at > 200mbit and ethernet at gbit.
3) have something simpler to work on that can take a 802.11ac card so
we can finally get to work on fixing wifi.
I've kind of given up on doing all that in one box, and the current
generation of 802.11ac APs lack oomph, and historically it's a real
pain the tukkus to ask people to continually update their main gateway
in order to make progress on beating bufferbloat. So having a stable
main gateway and working on fixing wifi in a separate box seems good.
My own inclination was towards the intel ivy bridge products as the
onboard cache is dma accessible, and thus at least theoretically
faster in a packet forwarding engine. On the other hand, my attempts
to use dual ethernet boards from various vendors have been often
frustrating.
I don't know a lot about the current generation of amd gear. I would
still prefer moving to an arm product actually...
>
> On Jul 17, 2014, at 1:28 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> or, hmm:
>>
>> http://www.pcengines.ch/apu.htm
>>
>> $136 dollars qty 500, probably needs power supply, heatsink and and case...
>>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
prev parent reply other threads:[~2014-07-17 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 5:08 Dave Taht
2014-07-17 5:28 ` Dave Taht
2014-07-17 13:26 ` Luke Hamburg
2014-07-17 16:25 ` Dave Taht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4z_7DbU0oCZ9xD_CHKYkHoAD1ZxU=javR8HEp5p59MiQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=luke@lighthousecorp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox