Bryan,
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.
I can use the new machine (Jaunt) and can push to both Hardy and
Jaunt machines.
At least it solved one issue, but we
On Fri, Apr 3, 2009 at 5:18 PM, Prasad Tadi pt...@roshitech.com 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
On Thu, Apr 2, 2009 at 7:33 PM, Prasad Tadi pt...@roshitech.com wrote:
My hardware is little more complicated, I will explain that below...
But wants to make sure that I understood Local Link.
Link Local is the ipv6 address assigned to the interface that starts
with fe80:: [1] You don't have to
On Fri, Apr 3, 2009 at 12:23 PM, Prasad Tadi pt...@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
Bryan,
Thanks for the details
Here is some more data following your mail.
The problem still persists...
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.
Bryan,
My hardware is little more complicated, I will explain that below...
But wants to make sure that I understood Local Link.
Hope you are not referring to IPv4 address.
scp over IPv4 is fine. No issues at all. Only when I use the IPv6, it
chokes.
scp /tmp/x.iso 172.16.109.50:/tmp
