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 A33F03B29E for ; Sun, 17 Sep 2023 15:58:58 -0400 (EDT) Received: from dlang-mobile (unknown [10.2.2.69]) by mail.lang.hm (Postfix) with ESMTP id 8672D1AC100; Sun, 17 Sep 2023 12:58:57 -0700 (PDT) Date: Sun, 17 Sep 2023 12:58:57 -0700 (PDT) From: David Lang To: Alexandre Petrescu cc: starlink@lists.bufferbloat.net In-Reply-To: <40da3b55-38ad-4e02-8c58-afea2bd02279@gmail.com> Message-ID: <2sp89904-o460-976s-4rsq-55nn6ps84464@ynat.uz> References: <2d05e701-7556-8ae4-122c-e2f2d23feff2@gmail.com> <4o116qp9-6108-91r8-pn91-o37o6629npqo@ynat.uz> <2012b68c-2e15-4b5c-b36b-3b1d7eff12b4@gmail.com> <0q3n1sp5-09r5-5pqn-3p9p-opq883305s1s@ynat.uz> <340fd78d-39eb-e9af-c15a-7ca87b173e4e@auckland.ac.nz> <40da3b55-38ad-4e02-8c58-afea2bd02279@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="228850167-1803587948-1694980737=:15407" Subject: Re: [Starlink] Main hurdles against the Integration of Satellites and Terrestial Networks 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: Sun, 17 Sep 2023 19:58:58 -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. --228850167-1803587948-1694980737=:15407 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT it's very clear that there is a computer in the dishy that you are talking to. You get the network connection while the dishy is not connected to the satellites (there's even a status page and controls, stowing and unstowing for example) I think we've seen that the dishy is running linux (I know the routers run an old openwrt), but I don't remember the details of the dishy software. David Lang On Sun, 17 Sep 2023, Alexandre Petrescu via Starlink wrote: > Date: Sun, 17 Sep 2023 19:21:50 +0200 > From: Alexandre Petrescu via Starlink > Reply-To: Alexandre Petrescu > To: starlink@lists.bufferbloat.net > Subject: Re: [Starlink] Main hurdles against the Integration of Satellites and > Terrestial Networks > > > Le 16/09/2023 à 01:32, Ulrich Speidel via Starlink a écrit : >> On 16/09/2023 5:52 am, David Lang wrote: >>> >>> In addition to that Ulrich says, the dishy is a full computer, it's >>> output is ethernet/IP and with some adapters or cable changes, you >>> can plug it directly into a router. >> >> We've done that with the Yaosheng PoE Dishy adapter - actually plugged >> a DHCP client straight in - and it "works" but with a noticeably >> higher rate of disconnects. > > It is good to know one can plug a DHCP client into the Ethernet of the > DISHY and receive DHCP replies. > > But that would be only a lead into what kind of DHCPv4 is supported, or not. > > I would ask to know whether the DHCP server runs on the DISHY, or > whether it is on the ground network of starlink, i.e. the reply to DHCP > request comes after 50ms, or after 500microseconds (timestamp difference > can be seen in the wireshark run on that Ethernet). > > This (DHCP server daemon on dishy or on ground segment) has an impact of > how IPv6  can be, or is, made to work. > > This kind of behaviour of DHCP - basically asking who allocates an > address - has seen a continous evolution in 3GPP cellular networks since > they appeared.  Nowadays the DHCP behaviour is very complex in a 3GPP > network; even in a typical smartphone there are intricacies about where > and how the DHCP client and server works. With it comes the problem of > /64 in cellular networks (which some dont call a problem, but I do). > > So, it would be interesting to see whether starlink has the same /64 > problem as 3GPP has, or is free of it (simply put: can I connect several > Ethernet subnets in my home to starlink, in native IPv6 that is, or not?). > > Alex > > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > --228850167-1803587948-1694980737=:15407--