wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Justin Kilpatrick" <justin@althea.net>
To: wireguard@lists.zx2c4.com
Subject: Re: Wireguard compatible with Omega2 / Omega2+
Date: Sun, 25 Aug 2019 15:23:28 -0400	[thread overview]
Message-ID: <4d3d2a31-79b6-4d30-92a4-ccfe81e9acba@www.fastmail.com> (raw)
In-Reply-To: <87ef2c4ttm.fsf@line.ungleich.ch>

For our application (Althea) we run Wireguard on embedded routers, I think the most similar CPU I have experience with is the MT7621[1] in the Edgerouter X.  We see a little over 100mbps of throughput with that. 

This chip is lower clocked and single rather than dual core. So expect low to mid double digit mbps (10-40mbps). Hard to predict more than that without trying it out. 

You don't need to concern yourself with ram, I would be far more concerned about getting your hands on the LEDE fork they are using on these devices. I'm not seeing a source code link after glancing at the site. 

If you don't have the kernel sources you can't build a WireGuard module. They may have their own build in a repository but I don't think you want to be at their mercy for updates either. 

[1] https://wikidevi.com/wiki/MediaTek_MT7621

-- 
  Justin Kilpatrick
  justin@althea.net

On Sun, Aug 25, 2019, at 11:42 AM, Nico Schottelius wrote:
> 
> Good evening,
> 
> I was wondering if an MT7688 SoC that features a 580 MHz MIPS CPU
> is feasible for running wireguard? With either 64 or 128 MB RAM.
> 
> To be specific, we are considering to get a a batch of Omega2/Omega2
> [0][1] and deploy IPv6 nodes on it that get their IPs via wireguard.
> 
> If anyone has experience with such lowe power device, any input would be
> appreciated.
> 
> Best,
> 
> Nico
> 
> [0] https://onion.io/store/omega2p/
> [1] https://onion.io/store/omega2/
> 
> --
> Your Swiss, Open Source and IPv6 Virtual Machine. Now on www.datacenterlight.ch.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-08-25 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26 16:57 Wireguard compatible with Omega2 / Omega2+ Nico Schottelius
2019-08-25 19:23 ` Justin Kilpatrick [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4d3d2a31-79b6-4d30-92a4-ccfe81e9acba@www.fastmail.com \
    --to=justin@althea.net \
    --cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).