Re: USB-serial adapter suggestions needed
- Reply: bob prohaska : "Re: USB-serial adapter suggestions needed"
- In reply to: bob prohaska : "Re: USB-serial adapter suggestions needed"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 14 Jan 2024 01:06:33 UTC
On Jan 13, 2024, at 13:36, bob prohaska <fbsd@www.zefox.net> wrote: > On Fri, Jan 12, 2024 at 09:49:47PM -0800, Mark Millard wrote: >> On Jan 12, 2024, at 17:52, bob prohaska <fbsd@www.zefox.net> 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. Okay. There was 1 reference to a login from "gateway.zefox.net" as a "Last login", as reported by a ns1.zefox.net login sequence. >> 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-( It now shows: |-50.1.20.29 ns1.zefox.net Pi2 12.3 armv7 ftdi usb-serial----50.1.20.27 |-50.1.20.30 ns2.zefox.net Pi2 12.3 armv7 2303 usb-serial----50.1.20.29 |-50.1.20.27 www.zefox.net Pi2 12.3 armv7 2303 usb-serial----50.1.20.26 But it later lists the older/inaccurate numbering as well: 50.1.20.30 ns1.zefox.net Pi2 v1.1 . . . 50.1.20.29 ns2.zefox.net Pi2 v1.1 . . . 50.1.20.27 www.zefox.net Pi2 v1.1 >> 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. Definitely improved description of the context, thanks. > 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)! === Mark Millard marklmi at yahoo.com