[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 02678) Command can not receive response to own ipv6 linklocal address
- To: usagi-users@xxxxxxxxxxxxxx
- Subject: (usagi-users 02678) Command can not receive response to own ipv6 linklocal address
- From: Hiroaki Kago <kago@xxxxxxxxxxxxxx>
- Date: Mon, 08 Dec 2003 19:48:21 +0900
- Reply-to: kago@xxxxxxxxxxxxxx
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
Hello,
I executed ftp and telnet command to own ipv6 linklocal address for the
interface eth0, but I could not receive their response. I used kernel,
ftp, ftpd, telnet and telnetd of usagi snap shot linux24-s20031013.
The result of the ftp command on IPv6 was as follows, and ftp was time out.
---------------------------------------------------------------------
[root]$ /usr/bin/ftp fe80::230:5ff:fe4a:4fc3%eth0
ftp: connect: Connection timed out
ftp> by
[root]$
---------------------------------------------------------------------
I supervised eth0 and lo using 'tcpdump' at the time of ftp execution,
and I found that the packets were transmitted from lo, and received
by lo.
The result of supervised eth0
---------------------------------------------------------------------
[root]$ tcpdump -v -e -n -i eth0 ip6
tcpdump: listening on eth0
0 packets received by filter
0 packets dropped by kernel
[root]$
---------------------------------------------------------------------
The result of supervised lo
---------------------------------------------------------------------
[root]$ tcpdump -v -e -n -i lo ip6
tcpdump: listening on lo
19:27:45.579557 0:0:0:0:0:0 0:0:0:0:0:0 ip6 94: ::1.32798 >
fe80::230:5ff:fe4a:4fc3.ftp: S [tcp sum ok] 2012622026:2012622026(0) win
32752 <mss 16376,sackOK,timestamp 989256 0,nop,wscale 0> (len 40, hlim 64)
19:27:45.579579 0:0:0:0:0:0 0:0:0:0:0:0 ip6 94:
fe80::230:5ff:fe4a:4fc3.ftp > ::1.32798: S [tcp sum ok]
2004983229:2004983229(0) ack 2012622027 win 32728 <mss
16376,sackOK,timestamp 989256 989256,nop,wscale 0> (len 40, hlim 64)
19:27:45.579583 0:0:0:0:0:0 0:0:0:0:0:0 ip6 74: ::1.32798 >
fe80::230:5ff:fe4a:4fc3.ftp: R [tcp sum ok] 2012622027:2012622027(0) win
0 (len 20, hlim 64)
19:27:48.579116 0:0:0:0:0:0 0:0:0:0:0:0 ip6 94: ::1.32798 >
fe80::230:5ff:fe4a:4fc3.ftp: S [tcp sum ok] 2012622026:2012622026(0) win
32752 <mss 16376,sackOK,timestamp 989556 0,nop,wscale 0> (len 40, hlim 64)
19:27:48.579130 0:0:0:0:0:0 0:0:0:0:0:0 ip6 94:
fe80::230:5ff:fe4a:4fc3.ftp > ::1.32798: S [tcp sum ok]
2007982779:2007982779(0) ack 2012622027 win 32728 <mss
16376,sackOK,timestamp 989556 989556,nop,wscale 0> (len 40, hlim 64)
19:27:48.579134 0:0:0:0:0:0 0:0:0:0:0:0 ip6 74: ::1.32798 >
fe80::230:5ff:fe4a:4fc3.ftp: R [tcp sum ok] 2012622027:2012622027(0) win
0 (len 20, hlim 64)
:
:
36 packets received by filter
0 packets dropped by kernel
[root]$
---------------------------------------------------------------------
The telnet command was the same result.
I think it is the cause that the kernel transmits and receives packets
by the loopback interface lo, in spite of specifying eth0.
Is this a problem of kernel?
Regards,
Hiroaki Kago