From nobody Sat Jan 13 21:36:33 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TCBYX2Pkrz56jRZ for ; Sat, 13 Jan 2024 21:36:32 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TCBYW5HyXz4RTS for ; Sat, 13 Jan 2024 21:36:31 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 40DLaXME021835 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 13 Jan 2024 13:36:34 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 40DLaXSI021834; Sat, 13 Jan 2024 13:36:33 -0800 (PST) (envelope-from fbsd) Date: Sat, 13 Jan 2024 13:36:33 -0800 From: bob prohaska To: Mark Millard Cc: FreeBSD ARM List Subject: Re: USB-serial adapter suggestions needed Message-ID: References: <482FA770-89E8-42E8-945E-B662AD564AFE@yahoo.com> <9F0BEC32-93CB-4DEB-98C4-D0FF2284B9DE@yahoo.com> <85102B46-CC5E-4FDA-8736-F562512FADEC@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <85102B46-CC5E-4FDA-8736-F562512FADEC@yahoo.com> X-Rspamd-Queue-Id: 4TCBYW5HyXz4RTS X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] On Fri, Jan 12, 2024 at 09:49:47PM -0800, Mark Millard wrote: > On Jan 12, 2024, at 17:52, bob prohaska wrote: > > > > While checking, I logged in as root on the serial consoles of each host. > > When I tried to log in to www.zefox.net the response was > > This and http://www.zefox.net/~fbsd/tiptrouble/corrupt_mac do not > make clear the full chain of connections. In fact the presentation > seems inconsistent with other information so various things may > have changed. > > Some context based on prior (out of date?) information: > > |-50.1.20.30 ns1.zefox.net Pi2 12.3 armv7 ftdi usb-serial----50.1.20.27 > |-50.1.20.29 ns2.zefox.net Pi2 12.3 armv7 2303 usb-serial----50.1.20.30 > |-50.1.20.27 www.zefox.net Pi2 12.3 armv7 2303 usb-serial----50.1.20.26 > > Was "pi4 RasPiOS workstation" involved as a starting place? If so, what > sequence gets to www.zefox.net from there? Yes, the login sequence starts from a shell on pi4 RapiOS workstation, via ssh to the terminal server where tip is run to access the usb-serial adapter plugged into it. > > Starting with what you showed via: > > http://www.zefox.net/~fbsd/tiptrouble/corrupt_mac > > (not knowing how you got there) . . . > > QUOTE > FreeBSD/arm (www.zefox.net) (ttyu0) > > login: root > Password: > Corrupted MAC on input. > ssh_dispatch_run_fatal: Connection to 50.1.20.29 port 22: message authentication code incorrect > END QUOTE > > 50.1.20.29 is supposedly ns2.zefox.net instead of www.zefox.net > or ns1.zefox.net according to http://www.zefox.net/~fbsd/netmap . The netmap was wrong. ns1 and ns2 were swapped....8-( > > The bugzilla material eventually needs to be updated with something > that can be followed and noting the possible occasional hardware or > software corruptions of material that end up going over Ethernet > that are now demonstrated to be able to cause the symptoms that > you have been seeing on occasion for so long. The netmap is corrected, with a description of the login sequence used to watch the serial consoles added. I _think_ it's a bit clearer than before, if not please say so. A readable (and correct) description of this setup is quite difficult to write. Thanks very much for close reading and taking the trouble to point out my error(s)! bob prohaska