Comment 8 for bug 352841

On Fri, Apr 3, 2009 at 5:18 PM, Prasad Tadi <email address hidden> wrote:
> However, when I run the command on local link (local machine's) , It
> completes and not even a single trace on tshark ip6 -i eth1
>
> But when I traced on  " lo",  it did show the data.

Right, because you're using the local machines link local address. You
need to use the local link address of the remote machine you want to
copy the file to.

I just built two hardy guests using python-vm-builder and ran them
under KVM using bridging. I had no problems with sustained traffic
ipv6 traffic between the two over scp using the link local addresses.

> tshark ip6 output.... on the originator.... No Errors
>
>  16.867469 fe80::250:56ff:fe8d:5c00 -> fe80::250:56ff:fe8d:403c
> SSHv2 [TCP Retransmission] Encrypted request packet len=1428

Actually, that is indicative of an error. A retransmission occurs when
the host sending the data doesn't get an acknowledgement that the
remote host received the data, so it sends it again. Either the
sending host isn't seeing them, or the receiving host isn't sending
them. This can be caused by a network or hardware problem on either
host or the equipment (or virtualized equipment) in between.

On Mon, Apr 6, 2009 at 9:35 AM, Prasad Tadi <email address hidden> wrote:
> Have a good news. I installed Jaunt (9.04) on a new VM and I could
> push the Large size files without any issues over IPv6.
>
> So it looks like OS/ Kernl level issue.

Perhaps, glad it's working for you now though.