[SOLVED] Can't ssh to a specific computer after upgrade
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am having a weird issue that doesn't make sense with what I could find on google. When I try to ssh from my newly upgrade Fedora 22 to an Arch Linux machine, I get this error:
Code:
ssh root@babyluigi
Corrupted MAC on input.
ssh_packet_read: message authentication code incorrect
But I am able to SSH from this Fedora 22 machine to my VPS server on the Internet. And I can SSH to babyluigi from another Kubuntu machine on the network.
Everything is connected via my router and an ethernet switch. Fedora and babyluigi are on same switch. Kubuntu machine is on router that's connected to switch.
I might suggest to flush the arp tables on both machines, as described in the following article. You can ignore adding static arp entries, very bad idea unless you seriously know exactly when and why to do so.
You mention that the old machine is running OpenSSH 6.1. Version 6.7 got rid of some insecure MACs. Can it be that it is using deprecated MACs and is in need of an upgrade?
MAC is typically referring to the MAC Address embedded in the hardware of a network interface card. A bad MAC would imply that the data got corrupted on a MAC address request from one machine to another. See "arping man" for an example on the details. The least invasive thing to do first is to flush the ARP cache on the machines to ensure that the MAC is being retransmitted and not read from the TCP cache where the cache itself might be corrupted. I found an article describing the same error you are speaking of.
I might suggest to flush the arp tables on both machines, as described in the following article. You can ignore adding static arp entries, very bad idea unless you seriously know exactly when and why to do so.
I had the same problem and fixed it by forcing ssh to use another mac method. My ssh communication used: umac-64@openssh.com (ssh -vvv username@pc) I changed to hmac-md5 (ssh -m hmac-md5 username@pc) and everyhing was working again.
OK, I decided to upgrade and it worked. Until the next upgrade borked my system. So, I'm just letting people know for completion's sake - it was just an out of date ssh. Won't matter anymore, I'm moving to CentOS on a real computer where I can get to a console if things get messed up rather than Pogoplug with Arch breaking with every update.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.