[Bug 352841] Re: SCP over IPv6 address is very Slow. Takes Hours
Bryan McLellan
btm at loftninjas.org
Fri Apr 3 21:53:42 BST 2009
On Fri, Apr 3, 2009 at 12:23 PM, Prasad Tadi <ptadi at roshitech.com> wrote:
> I am not really an expert, but I think the "Local link" may use Loop back
>
> Link-local is the fe80 addresses that refer to devices on a particular data link, such as a single Ethernet network, or a point-to-point serial connection. If you're using your own link-local address, then yes, that traffic will - I believe - traverse the loopback interface.
This is not correct. If you read the link I provided earlier it starts
with "All interfaces have an associated link-local address". Loopback
is it's own interface (lo) and is independent of your ethN interfaces.
The loopback interface also has it's own inet6 address (ifconfig lo0 |
grep inet6) in the specified ipv6 loopback address range.
> eth1 Link encap:Ethernet HWaddr 00:50:56:b5:52:c1
> inet6 addr: fdf8:c879:493e:1:250:56ff:feb5:52c1/64 Scope:Global
> inet6 addr: fe80::250:56ff:feb5:52c1/64 Scope:Link
The second address, that starts with fe80::, and additionally says
"Scope: Link" is the "Link Local" address. This is because this
address is for the local link only.
Try copying between two hosts using these address with Scope:Link to
rule out any addressing problems. Because these are local addresses,
you may need to specify the interface you want scp to use by adding
'%interface' to the end of the address, such as:
scp -6 desktone.tar [fdf8:c879:493e:1:250:56ff:feb5:52c1%eth1]:/tmp
It may be helpful to run 'sudo tshark ip6' on the originating host
while copying the file to look for any network errors.
--
SCP over IPv6 address is very Slow. Takes Hours
https://bugs.launchpad.net/bugs/352841
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
More information about the Ubuntu-server-bugs
mailing list