From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (rrcs-45-59-245-186.west.biz.rr.com [45.59.245.186]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 2CCFF3B2A4 for ; Mon, 23 Oct 2023 15:01:52 -0400 (EDT) Received: from dlang-mobile (unknown [10.2.2.69]) by mail.lang.hm (Postfix) with ESMTP id 58F8A1B4E1F; Mon, 23 Oct 2023 12:01:51 -0700 (PDT) Date: Mon, 23 Oct 2023 12:01:51 -0700 (PDT) From: David Lang To: Jack Haverty via Nnagain In-Reply-To: Message-ID: <94pn9o32-p3nn-44q2-5051-92oo4o52384q@ynat.uz> References: MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="===============5170593874708348161==" Subject: Re: [NNagain] upgrading old routers to modern, secure FOSS X-BeenThere: nnagain@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: =?utf-8?q?Network_Neutrality_is_back!_Let=C2=B4s_make_the_technical_aspects_heard_this_time!?= List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2023 19:01:52 -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. --===============5170593874708348161== Content-Type: text/plain; format=flowed; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT On Mon, 23 Oct 2023, Jack Haverty via Nnagain wrote: > We discovered that most computers simply believed the latest ARP information > it received.   So it was easy for the Flakeway to insert itself into any IP > traffic flow and do its work, without any changes to software in any other > computer.  It was handy not only for testing but also for diagnosing all > sorts of problems, simply capturing the traffic flows for later analysis > (similar to wireshark). > > That was all done in the IPV4 world, 40+ years ago, so I'm not sure how it > might relate to today's Internet.   We reported this "feature" to IETF and > some IEEE 802.x committee as a likely vulnerability, but I'm not sure if > anything changed. This is commonly used today for failover/load balancing David Lang --===============5170593874708348161== Content-Type: text/plain; CHARSET=utf-8 Content-Transfer-Encoding: BASE64 Content-ID: <1o761rr8-922o-4o9s-6qr2-q4012q3895p2@ynat.uz> Content-Description: Content-Disposition: INLINE X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm5hZ2FpbiBt YWlsaW5nIGxpc3QKTm5hZ2FpbkBsaXN0cy5idWZmZXJibG9hdC5uZXQKaHR0cHM6Ly9saXN0cy5i dWZmZXJibG9hdC5uZXQvbGlzdGluZm8vbm5hZ2Fpbgo= --===============5170593874708348161==--