Hardware related with the bug.Cable/dsl Lynksys router, tyan k7x motherboard, dual athlon mp. X11 forwarding fails and ssh disconnects in the LAN when trying to resolve the host by using DNS servers. For example if you try to connect whithin your LAN to your host computer running sshd. (assume that your host has a domainname host.bug.com= 65.92.197.129) and you try: ssh -X -l username host.bug.com this will lead to corrupted MAC address If you are within your LAN you have to use the internal LAN ip of the host. ssh -X -l username 192.168.1.106 (Asuming 192.168.1.106 is the internal ip address of the host. It should be assigned statically by th lynksys router)
You bug report makes _zero_ sense. Corrupted MAC address? Where? This sounds like a network misconfiguration, not any sort of OpenSSH bug.
I think what he actually means is "Corrupted MAC on input" - i.e. Message Authentication Code, not Media Access Control.
Please attach full version information (client + server) and debug traces from each end.
I have the exact same problem. Here is a bit more information: I have the following setup: 1 linksys router (BEFW11S4 version 1, latest firmware: 1.44.2z, Dec 13 2002) with 1 sshd server: imscamtlcvs02:~# /usr/sbin/sshd -v sshd: illegal option -- v sshd version OpenSSH_3.4p1 Debian 1:3.4p1-1 [...] The client uses: david@Fish:~$ ssh -V OpenSSH_3.4p1 Debian 1:3.4p1-1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f The exact error message I receive is: Disconnecting: Corrupted MAC on input The server has a STATIC IP and the client has a dynamic IP allocated by the linksys router. I tried to connect to the local server IP (192.168.1.200) from another local IP (192.168.1.100 for example) OR from the Internet (work) and I received the error from both locations. If I remove the server from the DMZ, it still crashes. I'm totally out of ideas. There is nothing in the logs relating to this behavior.
A similar problem reported recently: http://groups.google.com/groups?group=comp.security.ssh&selm=86smo2fxxh.fsf%40 bernard.hq.vetinsite.com "This morning the admin at the remote site upgraded the router firmware (presumably to 1.45.6, but all I'm certain of "something above 1.43.1"). After the upgrade, and until the router was restored to 1.43.1, my computer was unable to call home. In every other aspect the router appeared to work normally." You could try downgrading your router firmware to 1.43.1.
I'm closing this as the cause does not seem to be in OpenSSH. If you can provide some evidence this is due to a fault in OpenSSH, please re-open this bug.
Mass change of RESOLVED bugs to CLOSED
Jim Knoble reports that firmware 1.45.7 fixed this issue for him: http://marc.theaimsgroup.com/?m=108363895306157 [quote] I've experienced exactly the same MAC corruption using OpenSSH through a BEFSR41 with that firmware; a later firmware (1.45.7, 2003-07-31) fixed the problem. Beware and write down all your configuration settings; this one caused a factory reset after installation, if memory serves. This (slightly reformatted) changelog entry may be a telltale: Ver #. Date Description ------------------------------------------------------------------------ 1.45.7 Jul 31,2003 [...] 3.Fixed fragmented packets arriving out of order [/quote]