From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 81C643B29E for ; Sun, 17 Sep 2023 13:13:01 -0400 (EDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 38HHD0qe024916 for ; Sun, 17 Sep 2023 19:13:00 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0EF172016F6 for ; Sun, 17 Sep 2023 19:13:00 +0200 (CEST) Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 0410F200D13 for ; Sun, 17 Sep 2023 19:13:00 +0200 (CEST) Received: from [10.14.0.60] ([10.14.0.60]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 38HHCxiW001518 for ; Sun, 17 Sep 2023 19:12:59 +0200 Message-ID: <78e3ddc5-4f78-48d5-abd3-de1a1f140794@gmail.com> Date: Sun, 17 Sep 2023 19:12:59 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: fr To: starlink@lists.bufferbloat.net 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> From: Alexandre Petrescu In-Reply-To: <0q3n1sp5-09r5-5pqn-3p9p-opq883305s1s@ynat.uz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 17:13:01 -0000 Le 15/09/2023 à 19:52, David Lang via Starlink a écrit : > On Sat, 16 Sep 2023, Ulrich Speidel via Starlink wrote: > >> On 15/09/2023 11:29 pm, Alexandre Petrescu via Starlink wrote: >>> >>> I must say that I dont know whether the original 'DISHY' is simply a >>> dish antenna with an analog amplifier and maybe some mechanical motor >>> steering, or whether DISHY includes a computer to execute some >>> protocol, >>> some algorithm. > > 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. > > There are numberous teardown videos on youtube now, for both the > original and the 1st of the rectangular dishys, they will show you how > complex the system is. Thanks for the note.  It's always interesting to look at teardowns. The Ethernet/IP capability in the antenna box is very promising. If I had one, the first think I'd do is to use wireshark to listen on that Ethernet port to see whether it sends Router Advertisements (IPv6). People say IPv6 is supported but there are many ways in which IPv6 can be 'supported', and some are better than others, not the least being NAT66, IPv6-in-IPv4 and the prefix length (64 or not).  And DHCPv6 of course.  Native vs non native IPv6, in short. Alex > > David Lang > >  > >> It's a phased array, not a dish, even if it looks like one. It >> consists of 100's of fingernail-sized antenna elements that: >> >> * during transmissions, have an individual phase delay added to the >>   signal transmitted from that element, in order to permit >>   transmission of the combined signal from all elements into a >>   particular direction. >> * during reception, have an individual phase delay added to the signal >>   collected by that element, before the signals are added to obtain >>   the combined received signal. This allows reception from a >>   particular direction. >> >> Dishy's main direction of transmission / reception is therefore not >> its surface normal - this simply points to the area of the sky where >> Dishy expects to see most satellites (a function of geographical >> latitude and constellation design - essentially straight up in the >> tropics, and elsewhere in the direction of the 53rd parallel, which >> corresponds to the predominant orbital inclination in the Starlink >> fleet). The actual tracking is then done with the phased array >> without mechanical movement by Dishy. >> >> From what I've seen, Dishy seems to consume more power on receive >> than on transmit - that's if you actually download stuff. This is >> somewhat counter-intuitive if you're used to putting link budgets >> together. But I'd attribute that to a higher degree of digital signal >> processing required on the receive and demodulation path. >> >> > > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink