From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (unknown [66.167.227.145]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 355E83B29E for ; Fri, 17 Feb 2023 16:01:19 -0500 (EST) Received: from dlang-mobile (unknown [10.2.2.69]) by mail.lang.hm (Postfix) with ESMTP id 0F697175002; Fri, 17 Feb 2023 13:01:18 -0800 (PST) Date: Fri, 17 Feb 2023 13:01:18 -0800 (PST) From: David Lang To: Adam Thompson cc: "starlink@lists.bufferbloat.net" In-Reply-To: Message-ID: <53ssr050-3n7s-4647-22p7-1428r6646oo6@ynat.uz> References: MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="===============8372691667975295551==" Subject: Re: [Starlink] VPN woes, recommendations? X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2023 21:01:19 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --===============8372691667975295551== Content-Type: text/plain; format=flowed; charset=US-ASCII On Fri, 17 Feb 2023, Adam Thompson via Starlink wrote: > First, having multiple devices in serial is generally not a great idea for reliability. Can we realistically plug our remote AP directly into the dish, still? (This is using Starlink Business, FWIW.). I know we lose access to the Starlink app, but we also lose a NATing router and an unwanted wifi AP, so that's probably a net zero. I just don't know what other dangers/problems that topology might cause. look at youtube for people running their starlink on 12v, it requires cutting the cable and putting normal ends on it, but once you do that (and have a PoE power injector) you can connect a normal router to a starlink dish I haven't heard of anyone doing this for the larger dish, but for the standard one it's quite common. The dish then gives you a 192.168.1 IP address (and only one, so you still have your router NAT and dish NAT involved) David Lang --===============8372691667975295551== Content-Type: text/plain; CHARSET=utf-8 Content-Transfer-Encoding: BASE64 Content-ID: <7n7q3880-qs23-np5q-50p3-875741po5o94@ynat.uz> Content-Description: Content-Disposition: INLINE X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KU3Rhcmxpbmsg bWFpbGluZyBsaXN0ClN0YXJsaW5rQGxpc3RzLmJ1ZmZlcmJsb2F0Lm5ldApodHRwczovL2xpc3Rz LmJ1ZmZlcmJsb2F0Lm5ldC9saXN0aW5mby9zdGFybGluawo= --===============8372691667975295551==--