Date: Mon, 25 Feb 2002 22:18:27 +1100 From: Edwin Groothuis <edwin@mavetju.org> To: "JINMEI Tatuya / ?$B?@L@C#:H?(B" <jinmei@isl.rdc.toshiba.co.jp> Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPv6-over-IPv4 problems since the upgrade to 4.5 Message-ID: <20020225221827.F491@k7.mavetju.org> In-Reply-To: <y7vwux1q2e4.wl@condor.jinmei.org>; from jinmei@isl.rdc.toshiba.co.jp on Mon, Feb 25, 2002 at 07:30:59PM %2B0900 References: <0D9185CE635BD511ACA50090277A6FCF1359DB@axcs18.cos.agilent.com> <20020216130842.A19081@energyhq.homeip.net> <20020217122510.D491@k7.mavetju.org> <y7v4rk9lobt.wl@condor.jinmei.org> <20020222234829.F492@k7.mavetju.org> <y7vit8pbmg8.wl@condor.jinmei.org> <20020223084616.G492@k7.mavetju.org> <y7vwux1q2e4.wl@condor.jinmei.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 25, 2002 at 07:30:59PM +0900, JINMEI Tatuya / ?$B?@L@C#:H?(B wrote: > >>>>> On Sat, 23 Feb 2002 08:46:16 +1100, > >>>>> Edwin Groothuis <edwin@mavetju.org> said: > > >> > And the interface configuration: > >> > gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 > >> > tunnel inet 203.173.130.126 --> 206.123.31.114 > >> > inet6 fe80::250:8bff:feb9:2d24%gif0 prefixlen 64 scopeid 0x9 > >> > inet6 3ffe:b80:2:460::2 --> 3ffe:b80:2:460::1 prefixlen 128 > >> > >> Hmm, and what command did you type to cause this problem? If possible, > >> please give me the network topology as well. > > > The problem was when "route add -inet6 default -interface gif0" was > > used instead of the "route ... <ipaddress>". For the rest the > > configuration and the commands were the same. > > > This is a layout of the 'network': > > (snip) > > > The symptons were that if I setup a TCP-session, the original message > > is at: > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=279914+284924+/usr/local/www/db/text/2002/freebsd-hackers/20020217.freebsd-hackers > > Okay, I understand the configuration. I did a similar test on a > 4.5-RELEASE box, but could not reproduce the problem. The main > difference in my test case is I did not use ppp, so I guess ppp is > somehow related to this problem... > > Now I'd like to know: > > - did you see the same problem in an environment without ppp? That PPP link is my link to the outside world, I'm afraid I can't help you with this one. (Yes I'm living in a backwards country) > - what is the result of netstat -rnal when the kernel is sending > neighbor solicitations? I have three captures for you: one before, one during and one in hang state: *** This one is from before any session: Routing tables Internet: Destination Gateway Flags Refs Use Mtu Netif Expire default 203.109.251.3 UGSc 11 2073 1524 tun0 62.163.31.203 203.109.251.3 UGHW 1 1900 1524 tun0 63.149.6.93 203.109.251.3 UGHW 1 2036 1524 tun0 127.0.0.1 127.0.0.1 UH 7824 496162 16384 lo0 129.127.28.4 203.109.251.3 UGHW 1 1862 1524 tun0 131.155.132.36 203.109.251.3 UGHW 1 2408 1524 tun0 152.163.159.234 203.109.251.3 UGHW3 0 1969 1524 tun0 71 192.168.0 link#7 UC 2 0 1500 vmnet1 192.168.0.1 0:bd:10:10:0:1 UHLW 0 4 1500 lo0 192.168.0.44 link#7 UHLW 1 11 1500 vmnet1 192.168.1 link#1 UC 3 0 1500 fxp0 192.168.1.1 0:50:8b:b9:2d:24 UHLW 0 31541 1500 lo0 192.168.1.2 0:5:2:b1:89:ee UHLW 2 95980 1500 fxp0 1163 192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb 0 38 1500 fxp0 203.12.68.36 203.109.251.3 UGHW 1 1751 1524 tun0 203.109.251.3 203.173.157.67 UH 12 0 1524 tun0 204.57.55.54 203.109.251.3 UGHW 1 1630 1524 tun0 206.123.31.114 203.109.251.3 UGHW 2 2000 1524 tun0 212.204.230.141 203.109.251.3 UGHW 3 649 1524 tun0 217.120.67.246 203.109.251.3 UGHW 1 2049 1524 tun0 254.237.183.234 203.109.251.3 UGHW 2 2065 1500 tun0 Internet6: Destination Gateway Flags Refs Use Mtu Netif Expire ::/96 ::1 UGRSc 0 0 16384 lo0 => default gif0 ULSc 0 0 1280 gif0 ::1 ::1 UH 4 458445 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 fe80::%lo0/64 fe80::1%lo0 Uc 0 0 16384 lo0 fe80::1%lo0 link#3 UHL 0 0 16384 lo0 fe80::%vmnet1/64 link#7 UC 0 0 1500 vmnet1 fe80::2bd:10ff:fe10:1%vmnet1 0:bd:10:10:0:1 UHL 0 0 1500 lo0 fe80::%tun0/64 fe80::250:8bff:feb9:2d24%tun0 Uc 0 0 1500 tun0 fe80::250:8bff:feb9:2d24%tun0 link#8 UHL 0 0 1500 lo0 fe80::%gif0/64 link#9 UC 0 0 1280 gif0 fe80::250:8bff:feb9:2d24%gif0 link#9 UHL 0 0 1280 lo0 ff01::/32 ::1 U 0 0 16384 lo0 ff02::/16 ::1 UGRS 0 0 16384 lo0 ff02::%fxp0/32 link#1 UC 0 0 1500 fxp0 ff02::%lo0/32 ::1 UC 0 0 16384 lo0 ff02::%vmnet1/32 link#7 UC 0 0 1500 vmnet1 ff02::%tun0/32 fe80::250:8bff:feb9:2d24%tun0 UC 0 0 1500 tun0 ff02::%gif0/32 link#9 UC 0 0 1280 gif0 *** This one is just after the tcp-session is setup: Routing tables Internet: Destination Gateway Flags Refs Use Mtu Netif Expire default 203.109.251.3 UGSc 11 2073 1524 tun0 62.163.31.203 203.109.251.3 UGHW 1 1902 1524 tun0 63.149.6.93 203.109.251.3 UGHW 1 2036 1524 tun0 127.0.0.1 127.0.0.1 UH 7824 496172 16384 lo0 129.127.28.4 203.109.251.3 UGHW 1 1862 1524 tun0 131.155.132.36 203.109.251.3 UGHW 1 2408 1524 tun0 152.163.159.234 203.109.251.3 UGHW3 0 1969 1524 tun0 66 192.168.0 link#7 UC 2 0 1500 vmnet1 192.168.0.1 0:bd:10:10:0:1 UHLW 0 4 1500 lo0 192.168.0.44 link#7 UHLW 1 11 1500 vmnet1 192.168.1 link#1 UC 3 0 1500 fxp0 192.168.1.1 0:50:8b:b9:2d:24 UHLW 0 31541 1500 lo0 192.168.1.2 0:5:2:b1:89:ee UHLW 2 95980 1500 fxp0 1158 192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb 0 38 1500 fxp0 203.12.68.36 203.109.251.3 UGHW 1 1752 1524 tun0 203.109.251.3 203.173.157.67 UH 12 0 1524 tun0 204.57.55.54 203.109.251.3 UGHW 1 1631 1524 tun0 206.123.31.114 203.109.251.3 UGHW 2 2003 1524 tun0 212.204.230.141 203.109.251.3 UGHW 3 649 1524 tun0 217.120.67.246 203.109.251.3 UGHW 1 2049 1524 tun0 254.237.183.234 203.109.251.3 UGHW 2 2065 1500 tun0 Internet6: Destination Gateway Flags Refs Use Mtu Netif Expire ::/96 ::1 UGRSc 0 0 16384 lo0 => default gif0 ULSc 1 0 1280 gif0 ::1 ::1 UH 4 458445 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea gif0 UHLW 1 3 1280 gif0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 fe80::%lo0/64 fe80::1%lo0 Uc 0 0 16384 lo0 fe80::1%lo0 link#3 UHL 0 0 16384 lo0 fe80::%vmnet1/64 link#7 UC 0 0 1500 vmnet1 fe80::2bd:10ff:fe10:1%vmnet1 0:bd:10:10:0:1 UHL 0 0 1500 lo0 fe80::%tun0/64 fe80::250:8bff:feb9:2d24%tun0 Uc 0 0 1500 tun0 fe80::250:8bff:feb9:2d24%tun0 link#8 UHL 0 0 1500 lo0 fe80::%gif0/64 link#9 UC 0 0 1280 gif0 fe80::250:8bff:feb9:2d24%gif0 link#9 UHL 0 0 1280 lo0 ff01::/32 ::1 U 0 0 16384 lo0 ff02::/16 ::1 UGRS 0 0 16384 lo0 ff02::%fxp0/32 link#1 UC 0 0 1500 fxp0 ff02::%lo0/32 ::1 UC 0 0 16384 lo0 ff02::%vmnet1/32 link#7 UC 0 0 1500 vmnet1 ff02::%tun0/32 fe80::250:8bff:feb9:2d24%tun0 UC 0 0 1500 tun0 ff02::%gif0/32 link#9 UC 0 0 1280 gif0 *** And this one is after is hangs: Routing tables Internet: Destination Gateway Flags Refs Use Mtu Netif Expire default 203.109.251.3 UGSc 11 2073 1524 tun0 62.163.31.203 203.109.251.3 UGHW 1 1907 1524 tun0 63.149.6.93 203.109.251.3 UGHW 1 2036 1524 tun0 127.0.0.1 127.0.0.1 UH 7824 496188 16384 lo0 129.127.28.4 203.109.251.3 UGHW 1 1862 1524 tun0 131.155.132.36 203.109.251.3 UGHW 1 2408 1524 tun0 152.163.159.234 203.109.251.3 UGHW3 0 1969 1524 tun0 45 192.168.0 link#7 UC 2 0 1500 vmnet1 192.168.0.1 0:bd:10:10:0:1 UHLW 0 4 1500 lo0 192.168.0.44 link#7 UHLW 1 11 1500 vmnet1 192.168.1 link#1 UC 3 0 1500 fxp0 192.168.1.1 0:50:8b:b9:2d:24 UHLW 0 31541 1500 lo0 192.168.1.2 0:5:2:b1:89:ee UHLW 2 95980 1500 fxp0 1137 192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb 0 38 1500 fxp0 203.12.68.36 203.109.251.3 UGHW 1 1755 1524 tun0 203.109.251.3 203.173.157.67 UH 12 0 1524 tun0 204.57.55.54 203.109.251.3 UGHW 1 1631 1524 tun0 206.123.31.114 203.109.251.3 UGHW 2 2017 1524 tun0 212.204.230.141 203.109.251.3 UGHW 3 649 1524 tun0 217.120.67.246 203.109.251.3 UGHW 1 2049 1524 tun0 254.237.183.234 203.109.251.3 UGHW 3 2072 1500 tun0 Internet6: Destination Gateway Flags Refs Use Mtu Netif Expire ::/96 ::1 UGRSc 0 0 16384 lo0 => default gif0 ULSc 1 0 1280 gif0 ::1 ::1 UH 4 458445 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 fe80::%lo0/64 fe80::1%lo0 Uc 0 0 16384 lo0 fe80::1%lo0 link#3 UHL 0 0 16384 lo0 fe80::%vmnet1/64 link#7 UC 0 0 1500 vmnet1 fe80::2bd:10ff:fe10:1%vmnet1 0:bd:10:10:0:1 UHL 0 0 1500 lo0 fe80::%tun0/64 fe80::250:8bff:feb9:2d24%tun0 Uc 0 0 1500 tun0 fe80::250:8bff:feb9:2d24%tun0 link#8 UHL 0 0 1500 lo0 fe80::%gif0/64 link#9 UC 0 0 1280 gif0 fe80::250:8bff:feb9:2d24%gif0 link#9 UHL 0 0 1280 lo0 ff01::/32 ::1 U 0 0 16384 lo0 ff02::/16 ::1 UGRS 0 0 16384 lo0 ff02::%fxp0/32 link#1 UC 0 0 1500 fxp0 ff02::%lo0/32 ::1 UC 0 0 16384 lo0 ff02::%vmnet1/32 link#7 UC 0 0 1500 vmnet1 ff02::%tun0/32 fe80::250:8bff:feb9:2d24%tun0 UC 0 0 1500 tun0 ff02::%gif0/32 link#9 UC 0 0 1280 gif0 For your convenience, this is in the diff between the first and the second: Internet6: Destination Gateway Flags Refs Use Mtu Netif Expire ::/96 ::1 UGRSc 0 0 16384 lo0 => -default gif0 ULSc 0 0 1280 gif0 +default gif0 ULSc 1 0 1280 gif0 ::1 ::1 UH 4 458445 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 +3ffe:8050:201:1860:2a0:c9ff:feed:b7ea gif0 UHLW 1 3 1280 gif0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 And this in the diff between the second and the third: ::ffff:0.0.0.0/96 ::1 UGRSc 0 0 16384 lo0 3ffe:b80:2:460::1 3ffe:b80:2:460::2 UH 0 0 1280 gif0 3ffe:b80:2:460::2 link#9 UHL 1 0 1280 lo0 -3ffe:8050:201:1860:2a0:c9ff:feed:b7ea gif0 UHLW 1 3 1280 gif0 fe80::/10 ::1 UGRSc 0 0 16384 lo0 fe80::%fxp0/64 link#1 UC 0 0 1500 fxp0 fe80::250:8bff:feb9:2d24%fxp0 0:50:8b:b9:2d:24 UHL 0 0 1500 lo0 > - I guess some process (or kernel) modifies the route to the > destination. Could you run 'route -n monitor' while the session to > see the modification? The first message is when the session is setup, the second one is a short time later (not directly after the last neighbour solicitation message). I don't know what the 254.237.183.234 is. got message of size 260 on Mon Feb 25 22:04:25 2002 RTM_ADD: Add Route: len 260, pid: 0, seq 0, errno 0, flags:<UP,HOST,DONE,LLINFO,WASCLONED> locks: inits: sockaddrs: <DST,GATEWAY,IFP,IFA> 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea gif0 gif0 fe80::250:8bff:feb9:2d24%gif0 got message of size 124 on Mon Feb 25 22:04:38 2002 RTM_LOSING: Kernel Suspects Partitioning: len 124, pid: 0, seq 0, errno 0, flags:<UP,GATEWAY,HOST,DONE,WASCLONED> locks: inits: sockaddrs: <DST,GATEWAY> 254.237.183.234 203.109.251.3 If you need more information, feel free to ask. Edwin -- Edwin Groothuis | Personal website: http://www.MavEtJu.org edwin@mavetju.org | Interested in MUDs? Visit Fatal Dimensions: ------------------+ http://www.FatalDimensions.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020225221827.F491>