From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: wireguard@lists.zx2c4.com
Subject: Running Wireguard on a switch
Date: Sat, 27 Jul 2019 14:27:43 +0200 [thread overview]
Message-ID: <20190727122743.GA31059@lud.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 474 bytes --]
Hi,
Nowadays, manageable switches often run Linux. Ben Cox managed to run
wireguard on such a switch from Dell: https://blog.benjojo.co.uk/post/dell-switch-hacking
He's not talking about performance (that was not the goal): the CPU on
this switch looks like a low-end ARM so it's probably not that good, but
it's still fun :)
Cisco datacenter switches like the Nexus n3k have a x86 CPU and run
CentOS, so I wonder if somebody already tried Wireguard on those?
Baptiste
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-07-27 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 12:27 Baptiste Jonglez [this message]
2019-07-27 12:49 ` Vincent Wiemann
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=20190727122743.GA31059@lud.localdomain \
--to=baptiste@bitsofnetworks.org \
--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).