From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Jason@zx2c4.com Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 3617d66c for ; Thu, 7 Jul 2016 16:18:07 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 181a7b7f for ; Thu, 7 Jul 2016 16:18:07 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id f689538c (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Thu, 7 Jul 2016 16:18:06 +0000 (UTC) Received: by mail-lf0-f48.google.com with SMTP id h129so14751525lfh.1 for ; Thu, 07 Jul 2016 09:18:19 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20160706154834.GH2040@lud.polynome.dn42> From: "Jason A. Donenfeld" Date: Thu, 7 Jul 2016 18:18:17 +0200 Message-ID: To: Norman Shulman Content-Type: text/plain; charset=UTF-8 Cc: WireGuard mailing list Subject: Re: [WireGuard] WireGuard cryptokey routing List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Jul 7, 2016 at 6:15 PM, Norman Shulman wrote: > Look at it from the server side. There are millions of clients on millions > of 192.168.1.0/24 networks, yet a server can communicate with no more than > 254 of them. Voila, this is where you are most certainly mistaken. While a client might have 192.168.1.8 as their IP address for eth0, their IP address for wg0 can be something completely different. Want a million clients? Use a /20 as your wireguard device inner IP. Anyway, why don't you tell us all what you actually want to do, rather than these meandering theoretical questions? Then maybe we can help you effectively.