INTL 3:770/1 3:770/3
REPLYADDR invalid@invalid.invalid
REPLYTO 3:770/3.0 UUCP
MSGID: 5d5a9e12
REPLY: 6a81a0ab
PID: SoupGate-Win32 v1.05
bob prohaska writes:
> I'm seeing errors like this on my RasPiOS Pi4 ssh client host:
>
> Connection closed by remote host
> Corrupted MAC on input.
> ssh_dispatch_run_fatal: Connection to 50.1.20.29 port 22:
> message authentication code incorrect
A message received from the server was corrupted. Off the top of my
head, possible causes include:
- some fault in the network between the two endpoints
- faulty network device on one endpoint or the other
- faulty RAM on one endpoint or the other
- software bug on end endpoint or the other (unlikely, everyone else
would be impacted)
> They show up after a successful ssh login, usually shortly after,
> sometimes never. The connection can be re-started, but the error
> persists even after rebooting the remote host.
>
> It happens with some hosts and not others, I'm trying to figure
> out if it's my RasPiOS workstation or the clients (FreeBSD)
> reporting the error. The IP number shown is of the remote host,
> but which MAC is being complained about and by whom I can't tell.
In this context ‘MAC’ means
https://en.wikipedia.org/wiki/Message_authentication_code, not a network
card’s MAC address.
--
https://www.greenend.org.uk/rjk/
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225
SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17
SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038
SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364
SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
