Problem happens on win 7 so it is not system related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/60764
Title:
Large file transfer gives error: Corrupted MAC on input
To manage notifications
Just for anyone that's reading, I had this problem while rsync-ing large
files from a server to client. The probably ended up being the RAM. Run
memtest just to be sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I realize this is closed. Just adding a few notes from my own experience
since the discussion here has been useful to me. In my case the error
shows up in running ssh -Y to a second system, and then starting
dosemu on the remote system (which will tunnel to my desktop). The
remote system has an
Here's helpful background:
https://blogs.oracle.com/janp/entry/ssh_messages_code_bad_packet
It doesn't look to me like turning off rx and tx should in any way
lessen OpenSSH's resistance to corruption, so should be safe as far as
this goes. The other side of this is that it looks like somehow
Here was my problem, it looks like: A firewall rule on the remote box
(which is on my LAN) which rejected traffic to IP 224.0.0.1, which is
part of the Local Network Control Block. That's evidently a channel
required by the two host systems in connection with rx and tx delay
requests.
--
You
I'm getting the same problem. Never had the problem before, but now I
get it constantly when I attempt to use SFTP, and it started after I
upgraded to Oneiric the other day.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just got bitten once again by this bug on my Lenovo IdeaPad S10e with
a freshly installed Oneiric. The old broadfix woraround is still
working, from what I can tell so far. So please re-open this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
So I wrote up the following application to help me debug:
https://github.com/kitscuzz/n_stress (please note that the CRC32 doesn't
work quite how it's meant to, but it has caught corruption pretty
consistently)
I have now confirmed that it is not any of my networking equipment, or
specific to my
Here is the 64bit debian server output of lspci -vvv
** Attachment added: deb_64bit_server_lspci.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/60764/+attachment/1974156/+files/deb_64bit_server_lspci.txt
--
You received this bug notification because you are a member of Ubuntu
And last but least here is the 32bit ubuntu machine's lspci -vvv output
** Attachment added: ubuntu_32bit_laptop_lspci.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/60764/+attachment/1974157/+files/ubuntu_32bit_laptop_lspci.txt
--
You received this bug notification because you
BTW, On an Asus EEE PC, ethtool -K eth0 rx off is rejected. However,
ethtool -K eth0 tx off will in fact turn off *both* TX and RX
checksumming (and vice versa).
romulus@meatwad:~$ sudo ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: off
Well I'm definitely willing to believe this is a hardware error but at
this point it is wholly bewildering to me. I'll have to try new sticks
of ram though I'm reluctant to believe that is the issue as the single
stick of 4gig ram which is in the machine has the correct voltages and
timings which
Just an update on my earlier posts. It was definitely a RAM issue on my
machine. First I thought I fixed it by changing voltage in BIOS. But
after a while the problem showed up again -- seldom but very annoying.
So I replaced RAM more than half a year ago. Since then everything is
fine.
My
I'm also suffering from this bug, and I'm willing to do as much as is humanly
possible to fix it in a reasonable time frame.
---
So first and foremost, I am suffering from this bug on two separate platforms:
I have an Ubuntu
I can confirm this bug is still present in Maverick (10.10), 32 bit
system, copying files over scp to an eeepc 1005H running Mint 8:
I am getting this error both with rx / tx set to off as suggested by
others, or without running ethtool first.
scp testfile.dat eeepc:
eeepc password:
Sorry, forgot to include some info on the ethernet controller:
lspci | grep eth -i
00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network
Connection (rev 02)
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug
I got the same problem in ubuntu 10.04. The server runs OpenSuse 11.2.
I used to get Corrupted MAC on input very often. After running ethtool in the
server as commented above, I'm getting the errors much less often (but they
still appear).
Running it on the client gives me Operation not
Also affects Karmic Server on Lenovo S10e,
sudo ethtool -K eth0 tx off
on server was sufficient to solve this problem.
If it is impossible to get it properly fixed in the kernel,
how about an error handler that does the equivalent
of the ethtool fix, and automatically submits a bug report
It's possible that this could be caused by faulty hardware, but I doubt
it. This seems to come up every other Ubuntu/Debian upgrade reinstall I
do. I noticed this with Mint8 fresh install. After upgrade it went away.
Now after trying Ubuntu 10.04 it's back. On my part it's definitely
software
9.10 on the S10e on my left? Corrupted MAC on input.
9.10 on the S10e on my right? Works a champ.
We've got dodgy hardware, friends.
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification because you are a member of
Argh, no, the 9.10 on my right isn't working either. I'd merely assumed
that since I had never seen that problem before, and I was able to fetch
those files in the first place, that the corrupted mac problem wasn't
present. But when I tried to transfer the files away to a known-good
machine,
I'm getting this error ON MY VERIZON WIRELESS NOVATEL USB760 which of
course uses ppp. Natch, the broadfix doesn't change anything. Neither
does typing the command using only my left hand. My expectation of
either of those fixing the problem was very low.
Have never seen this problem using
I'm still getting the same old transfer errors in Lucid Alpha 3 on my
Lenovo S10e (clean install, fully updated). The broadfix workaround
still does it, though.
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification
Today I switched back to my Atheros card and I transferred _without_ error in
scp more times an iso image without any error. I'm using the kernel
2.6.32-020632-generic from the Ubuntu repository.
Here's some tech details. I'm really positively surprised and I'm still using
this wifi card in
Bill, thanks for your advice. I was double checking every large transfer
for several days now. I didn't discover any md5 mismatch since I changed
the RAM settings manually to the recommended for my modules. I guess
that the voltage was not set correctly. Greetings Peter
--
Large file transfer
Peter - keep pushing lots of data to be sure. I had the same problem
and 'solution' on an ASUS mobo, but I found that every once in a while
the Corrupted MAC error comes back on atl1e , though much more
infrequently. Switching to a different gigabit network card/driver
results in zero errors, so
I found out that it was a RAM issue on my machine! I noticed that the
workaround of burianek resolved the Corrupted MAC messaged, however
md5 sums of large files often mismatched after trandfer! Also noticed
that ubuntu CD/DVD media verification often turned up a lot of errors on
this machine but
The workaround of burianek seems to work fork for me. I had several
checksum errors even with ubuntu updates before applying the update.
Seems to work fine now. Did not perform the nc test yet.
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You
Unfortunately the workaround does not work on Asus Eee PC 1000HE with an
Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (1969:1026) and
atl1e driver.
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification
Ignore my comment #62.
The bug is more difficult to reproduce when downloading random files
from the Internet, but it does occur every once in a while. This
difficulty may have something to do with the speed or bandwidth of the
download, ie. the probability of the bug showing up is less likely
I am seeing this problem using scp to copy large files from a Karmic
(ubuntu 64 bit, Intel DG45ID board, Q9550 CPU) system to a Jaunty 64 bit
system.
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification because you
Peter P.: If you download Linux kernel source from www.kernel.org and
then check the md5sum of the downloaded file, do you get different
results on the computers? If not, suspend, resume, download and check
md5sum again to see if that changes anything.
--
Large file transfer gives error:
I can confirm this Corrupted MAC on input bug on i386 desktop version
of Ubuntu 9.10 karmic. Silent file corruption also happens when
downloading files using HTTP or FTP protocols. This bug is easily
reproducible.
The computer on which this bug manifests itself is an Asus Eee PC 1000HE
with 2 GB
Please don't change status if you don't know what you are doing.
https://wiki.ubuntu.com/Bugs/Status
Thank you.
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug
** Changed in: linux (Ubuntu)
Status: Triaged = Confirmed
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I can confirm that this issue still exists in Karmic (9.10) [actual, not
RC] on a lenovo S10e
Fortunately for me the fix suggested by Johan Christiansen on 2008-09-08
works on this hardware.
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You
This is still an issue in Karmic (RC). On my Lenovo S10e I'm still
getting errors when copying large files to my Jaunty fileserver via the
machine's LAN interface using SSH(FS). Fortunately the workaround
suggested by burianek on 2009-08-19 helps in Karmic too. (BTW, a restart
is not required
Hmm. I seeing this problem with scp of large files to a jaunty box.
[0.00] Linux version 2.6.28-15-generic (bui...@palmer) (gcc
version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18
18:40:08 UTC 2009 (Ubuntu 2.6.28-15.49-generic)
Unfortunately the turning off checksumming
I made this automatic workaround for my firend with Lenovo S10. It's
based on altering eth with ethtool.
Place this script in
/etc/network/if-up.d/broadfix
Make it executable
sudo chmod +x /etc/network/if-up.d/broadfix
Restart
---
You may want to specify which eth you want to alter.
I made this automatic workaround for my firend with Lenovo S10. It's
based on altering eth with ethtool.
Place this script in
/etc/network/if-up.d/broadfix
Make it executable
sudo chmod +x /etc/network/if-up.d/broadfix
Restart
---
You may want to specify which eth you want to alter.
I an experiencing the same problem with one of my Systems
I am using a rather old Laptop (Pentium MMx-233) with Debian Lenny as download
server.
Originally this Laptop only had a 10 MBit D-Link PCMCIA-NIC. With this card
there were no problems at all.
Since i replaced it with a (rather slow)
I solved the problem changing the minipciex card on my Acer AspireOne with an
Intel 3945ABG. Yesterday, for the first time and _without_ errors, I
transferred a 1.7 G. I'm thinking that this bug is left opened intentionally.
I'm agree with Johan Christiansen, two years and a half is enough to
I'm seeing this in Jaunty on a Lenovo laptop. lspci says
02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast
Ethernet PCI Express (rev 02)
The symptoms are so severe that running google-chrome over ssh dies within a
few seconds.
Happily, the workaround sudo ethtool -K eth0
** Tags added: ct-rev
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Great finding. I can confirm that the command from gloawu fixes the problem.
My curiosity drives me to ask how did you find this out?
Is there possibly anything that we can do to get this fixed in the
upstream?
Thanks.
On Tue, Apr 7, 2009 at 7:15 PM, gloawu glo...@gmail.com wrote:
I can also
Unfortunately I didn't figure it out myself. The command was posted here by
Johan Christiansen on 2008-09-08 . Maybe he can go into more detail on this.
You're welcome
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug
Yes, this is indeed a very embarrassing driver problem, where the
hardware TCP offloading in the driver seems to corrupt frames that use
SSL. The bug has been reported over 2½ year ago, and nobody seem to have
what it takes to get it fixed, or the guts to increase the priority so
it will reach the
I can also confirm this bug when running Intrepid on an Lenovo Ideapad
S10e and trying to move files to another computer via ssh over the
ethernet interface. The command sudo ethtool -K eth0 rx off tx off
fixes the problem.
--
Large file transfer gives error: Corrupted MAC on input
I have the same problem on Jaunty Jackalope Beta 9.04 with the following
network card:
Ethernet controller: Attansic Technology Corp. L1e Gigabit Ethernet Adapter
(rev b0).
I stumbled upon this error while doing a large file transfer using scp.
--
Large file transfer gives error: Corrupted
I get the same problem: Corrupted MAC on input when running on
Intrepid on Lenovo Ideapad S10e connected via ethernet.
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification because you are a member of Ubuntu
Bugs,
I get this problem when running rdiff-backup (which uses ssh) between
two machines both running Debian Lenny, with kernel 2.6.26-1-amd64 #1
SMP Wed Nov 26 18:26:02 UTC 2008 x86_64 GNU/Linux. The server machine
has a Macronix ethernet device using the tulip driver. I also can solve
the problem by
Running sudo ethtool -K eth0 rx off tx of only gives me an error
[EMAIL PROTECTED]:~$ sudo ethtool -K eth0 rx off tx off
Cannot set device rx csum settings: Operation not supported
Im not sure what this does exatly, so im sorry I cant give any more
details.
Upgrade today
[EMAIL PROTECTED]:~$
I am running Ubuntu 8.04 here at the moment. And I have this Corrupted
MAC on input issue here too when using ssh. I even had it when ssh'ing
to the same machine. I did
ssh -X [EMAIL PROTECTED]
and the ssh connection over the loop back device also got disconnected
due to the MAC issue. Hope
This bug is still present in Intrepid Ibex.
running:
sudo ethtool -K eth0 rx off tx off
fixes the problem.
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
The 18 month support period for Edgy Eft 6.10 has reached it's end of
life. As a result, we are closing the linux-source-2.6.17 Edgy Eft
kernel task. However, please note that this report will remain open
against the actively developed kernel. Thank you for your continued
support and help as we
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Triaged
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification
** Changed in: linux (Ubuntu)
Sourcepackagename: linux-source-2.6.24 = linux
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have this same problem on a Hardy laptop running:
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit
Ethernet PCI Express (rev 11)
Subsystem: IBM Unknown device 0577
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at a010 (64-bit,
I can confirm that turning offload parameters to off solves the issue.
What might be wrong here?
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
--
Large file transfer gives error: Corrupted MAC on input
https://bugs.launchpad.net/bugs/60764
You
I am assigning this bug to the 'ubuntu-kernel-team' per their bug
policy. For future reference you can learn more about their bug policy
at https://wiki.ubuntu.com/KernelTeamBugPolicies .
** Changed in: linux-source-2.6.17 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team
I had the same problem with my LOM NIC Marvell 88E8001. I´m quite sure
it was a hardware/driver issue, but in my case I solved it disabling the
offload checksum on the NIC with the following command:
ethtool -K eth0 rx off tx off
I hope this could help
--
Large file transfer gives error:
Unfortunately my card does not support this :(
$ sudo ethtool -K eth0 tx off
Cannot set device tx csum settings: Operation not supported
$ sudo ethtool -K eth0 rx off
Cannot set device rx csum settings: Operation not supported
--
Large file transfer gives error: Corrupted MAC on input
On of the host I manage has been affected by the problem discussed in
this thread for months now. It occurs both when transferring files with
scp and during ssh sessions, however at a time from the start of
transfer or of session that appears to be random. It's avery annying
problem: some days it
Mika - I don't easily see what network driver you are using. Is it the
e1000 also? Thanks in advance.
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm afraid it's a different card: 3Com PCI 3c905C Tornado
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Oh, and the driver is 3c59x.
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi,
I have the same issue with a dapper server. In my case not only happen
with scp to another machine. Sometimes just after login in via ssh.
In the same switch there are anothers ubuntu dapper server without
problem, so I think is a driver issue. The machine have two same nics
and in both
I switched the NIC with another one of the same type and put it into
another PCI slot. Didn't change anything...
Then I let memtest86+ run and it also didn't detect anything.
I then lowered the bus clock frequency from 133 to 100 MHz. Also no
effect.
So I'm quite stuck here. The only thing I
** Changed in: openssh (Ubuntu)
Sourcepackagename: openssh = linux-source-2.6.15
Assignee: Brian Murray = (unassigned)
Status: Needs Info = Confirmed
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
The kernel used is actually 2.6.17-10-generic version 2.6.17.1-10.34
from edgy
** Changed in: linux-source-2.6.15 (Ubuntu)
Sourcepackagename: linux-source-2.6.15 = linux-source-2.6.17
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs
OK. I also tried only using one memory module at a time. Still no luck.
I then tried to rule out the obvious by connecting the computers using a
crossover-cable. No change...
I then tried transmitting a file consisting only of zero bytes. This
surprisingly worked.
I then discovered vbindiff and
Very good idea!
As it turns out you're right. The same thing happens with netcat. Also
only when the broken computer acts as server. The other way round works
fine...
05fab97be7fd5e7c9229187c24c89ea0 test.bin.orig
05fab97be7fd5e7c9229187c24c89ea0 test.bin.m2s
7dcb7bef6d1af049bd63fcf6d180685e
To eliminate ssh from the equation I was wondering if you could test
doing a file transfer with netcat. Here is an example of that:
At the server console:
$ nc -v -w 30 -p 5600 -l filename.back
and on the client side:
$ nc -v -w 2 10.0.1.1 5600 filename
The file named filename is being
** Attachment added: dmesg output from the server
http://librarian.launchpad.net/6351956/dmesg-server.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: dmesg output from the client
http://librarian.launchpad.net/6351957/dmesg-client.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Come to think about it, I can pretty much rule out the client in this.
This is a completely different machine than the one I used when I first
reported this bug...
It also can't be something in the network infrastructure because it was
the same when I wasn't using the switch but the server was
** Attachment added: ifconfig output from the server
http://librarian.launchpad.net/6351959/ifconfig-server.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: ifconfig output from the client
http://librarian.launchpad.net/6351960/ifconfig-client.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This is extremely strange. Could you attach the dmesg from both the
client and server, and the output of ifconfig from both? (Feel free to
edit out any private IPs or anything like that)
You say you saw this when the client was on wireless and also tried
plugging the client into the switch (so
Perhaps using scp in verbose mode would more informative. The switch
for verbose is '-v' so could you try 'scp -v'? Also is there anything
in your kernel log around the time when these errors occur?
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
** Attachment added: Logfile from the server
http://librarian.launchpad.net/6341823/server-log.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Ah, sorry. I forgot to say that there's nothing in the kernel log,
neither on the client nor on the server.
I've tried running the server and the client at LogLevel DEBUG3 and will
attach the logs.
I also inserted some debug output which gives this additional
information (as an example, the
** Attachment added: Logfile from the client
http://librarian.launchpad.net/6341822/client-log.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Could you please add information regarding the type of network adapter
on both machines? ('lspci -vvn') Additionally if you could add 'sudo
ethtool eth0' where eth0 is the network interface being used in the file
transfer that would help. Thanks again.
--
Large file transfer gives error:
On the server the NIC has PCI id 00:0a.0.
On the client I actually have no idea which one of the PCI devices
corresponds to the NIC because it's an onboard one...
** Attachment added: lspci output from the server
http://librarian.launchpad.net/6342353/lspci-server.txt
--
Large file transfer
** Attachment added: lspci output from the client
http://librarian.launchpad.net/6342354/lspci-client.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: ethtool output from the server
http://librarian.launchpad.net/6342356/ethtool-server.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: ethtool output from the client
http://librarian.launchpad.net/6342364/ethtool-client.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks for updating the bug report. Come to find out the output of
'ethtool -k' would be more informative. Could you add that too? I
apologize for the mistake.
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
** Attachment added: ethtool -k output from the client
http://librarian.launchpad.net/6346527/ethtool-k-client.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
No problem :)
** Attachment added: ethtool -k output from the server
http://librarian.launchpad.net/6346522/ethtool-k-server.txt
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks for your bug report. I was wondering if this is still an issue
for you. If it is approximately how large of a file are you copying?
Furthermore do you notice anything in 'dmesg' when the connection is
lost? Thanks in advance.
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) =
Unfortunately it's still an issue.
I first suspected the WLAN router but now the machines are directly
connected by a switch and the problem still occurs...
I initially noticed the problem with a video file taken with a digicam.
I don't know exactly how big it was, probably around 50 MB. But the
Correction: I can reproduce it, it just takes longer until the error
occurs. So it's not fixed after all...
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Well, I can't seem to reproduce this after the latest kernel update of
dapper.
So you can consider this fixed.
--
Large file transfer gives error: Corrupted MAC on input
https://launchpad.net/bugs/60764
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
97 matches
Mail list logo
