From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: chm.duquesne@gmail.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 4337a3de for ; Wed, 18 Apr 2018 09:25:40 +0000 (UTC) Received: from mail-it0-f42.google.com (mail-it0-f42.google.com [209.85.214.42]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 646d474f for ; Wed, 18 Apr 2018 09:25:40 +0000 (UTC) Received: by mail-it0-f42.google.com with SMTP id l83-v6so592552ita.5 for ; Wed, 18 Apr 2018 02:40:26 -0700 (PDT) MIME-Version: 1.0 Sender: chm.duquesne@gmail.com From: Christophe-Marie Duquesne Date: Wed, 18 Apr 2018 11:40:05 +0200 Message-ID: Subject: Broadcast on wireguard To: wireguard@lists.zx2c4.com Content-Type: text/plain; charset="UTF-8" List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi list, Maybe the answer is obvious to some of you, but I don't quite understand why wireguard does not support broadcasting, and I found no clear explanation in the archive. In fact, this [1] seems to indicate that implementing it would be doable, so I am wondering why this has not been done. Could anyone explain - roughly - why this is the case? Is it for security reasons? Performance? Complexity of implementation? Lack of interest? Another possibility could be that my question is just poorly asked or irrelevant, in that case I would also appreciate a hint :-) Best, Christophe-Marie [1]: https://lists.zx2c4.com/pipermail/wireguard/2016-December/000813.html