[Bug 263260] Re: ipv6 stops working after a while
swmike, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Tags added: intrepid needs-upstream-testing regression-release ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263260 Title: ipv6 stops working after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263260] Re: ipv6 stops working after a while
I have been successfully running 9.04 with the ubuntu provided kernels since its release and haven't seen the problem since. -- ipv6 stops working after a while https://bugs.launchpad.net/bugs/263260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263260] Re: ipv6 stops working after a while
Hi swmike, You mentioned you tested an upstream 2.6.27 kernel from kernel.org. Since this is the case this should really be escalated to the upstream kernel developers in a bugzilla.kernel.org report. Care to file this there as well? We can then link this bug report to the upstream one. For more information please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies#Reporting Bugs Upstream . Thanks. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- ipv6 stops working after a while https://bugs.launchpad.net/bugs/263260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263260] Re: ipv6 stops working after a while
I have now tried kernel.org latest kernels of 2.6.25, 2.6.26 and 2.6.27 and they all have the same problem, I also booted a harlddy installation with my kernel.org 2.6.26.3, and it had the same problem also. The weird thing is that I had ipv6 working perfectly with my old hardy installation (hard drive broke so I had to re-install). I'm at loss as to what is going on here... No configuration has changed on the cisco router and it's running a very recent IOS so there should be no problem there either. I have disabled IGMP snooping on my switch, didn't change anything either. -- ipv6 stops working after a while https://bugs.launchpad.net/bugs/263260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263260] Re: ipv6 stops working after a while
I ran the cron script for 14 hours, still worked, then I did the following: MikaelA7200Inf3#clear ipv6 neighbors MikaelA7200Inf3#show ipv6 neighbors MikaelA7200Inf3# Now ping doesn't work again. 08:01:23.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 213 08:01:24.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 214 08:01:25.566346 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::240:63ff:fef5:17c2 > 2a00:801:b::1: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has 2a00:801:b::1 source link-address option (1), length 8 (1): 00:40:63:f5:17:c2 0x: 0040 63f5 17c2 08:01:25.566992 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 215 08:01:25.567307 IP6 (class 0xe0, hlim 255, next-header ICMPv6 (58) payload length: 24) 2a00:801:b::1 > fe80::240:63ff:fef5:17c2: [icmp6 sum ok] ICMP6, neighbor advertisement, length 24, tgt is 2a00:801:b::1, Flags [router, solicited] 08:01:26.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 216 08:01:27.566374 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 217 08:01:28.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 218 08:01:29.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 219 08:01:30.564590 IP6 (class 0xe0, hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::20a:42ff:fedd:5470 > fe80::240:63ff:fef5:17c2: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::240:63ff:fef5:17c2 source link-address option (1), length 8 (1): 00:0a:42:dd:54:70 0x: 000a 42dd 5470 08:01:30.564622 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 24) fe80::240:63ff:fef5:17c2 > fe80::20a:42ff:fedd:5470: [icmp6 sum ok] ICMP6, neighbor advertisement, length 24, tgt is fe80::240:63ff:fef5:17c2, Flags [solicited] 08:01:30.566380 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 220 08:01:31.566377 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 221 08:01:32.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a00:801:b::10 > 2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, seq 222 on the cisco router: Sep 3 08:01:22.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Sep 3 08:01:23.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Sep 3 08:01:24.567: ICMPv6-ND: INCMP deleted: 2A00:801:B::10 Sep 3 08:01:24.567: ICMPv6-ND: INCMP -> DELETE: 2A00:801:B::10 Sep 3 08:01:24.567: ICMPv6-ND: DELETE -> INCMP: 2A00:801:B::10 Sep 3 08:01:24.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Sep 3 08:01:25.563: ICMPv6-ND: Received NS for 2A00:801:B::1 on GigabitEthernet4/0 from FE80::240:63FF:FEF5:17C2 Sep 3 08:01:25.563: ICMPv6-ND: Sending NA for 2A00:801:B::1 on GigabitEthernet4/0 Sep 3 08:01:25.563: ICMPv6-ND: STALE -> DELAY: FE80::240:63FF:FEF5:17C2 Sep 3 08:01:25.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Sep 3 08:01:26.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Sep 3 08:01:27.568: ICMPv6-ND: INCMP deleted: 2A00:801:B::10 Sep 3 08:01:27.568: ICMPv6-ND: INCMP -> DELETE: 2A00:801:B::10 Sep 3 08:01:27.568: ICMPv6-ND: DELETE -> INCMP: 2A00:801:B::10 Sep 3 08:01:27.568: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Sep 3 08:01:28.568: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Sep 3 08:01:29.568: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Sep 3 08:01:30.564: ICMPv6-ND: DELAY -> PROBE: FE80::240:63FF:FEF5:17C2 Sep 3 08:01:30.564: ICMPv6-ND: Sending NS for FE80::240:63FF:FEF5:17C2 on GigabitEthernet4/0 Sep 3 08:01:30.564: ICMPv6-ND: Received NA for FE80::240:63FF:FEF5:17C2 on GigabitEthernet4/0 from FE80::240:63FF:FEF5:17C2 Sep 3 08:01:30.564: ICMPv6-ND: PROBE -> REACH: FE80::240:63FF:FEF5:17C2 Sep 3 08:01:30.568: ICMPv6-ND: INCMP deleted: 2A00:801:B::10 Sep 3 08:01:30.568: ICMPv6-ND: INCMP -> DELETE: 2A00:801:B::10 Sep 3 08:01:30.568: ICMPv6-ND: DELETE -> INCMP: 2A00:801:B::10 Sep 3 08:01:30.568: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 MikaelA7200Inf3#show ipv6 neighbors IPv6 Address
[Bug 263260] Re: ipv6 stops working after a while
** Tags added: linux-2.6.27 -- ipv6 stops working after a while https://bugs.launchpad.net/bugs/263260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263260] Re: ipv6 stops working after a while
I have restarted networking (networking stop && ifconfig eth0 down && networking start && killall dhclient && networking reload) Now everything works again. I have created a cron script that is run every hour, that pings an ipv6 address. If the problem hasn't occured by tomorrow again, then it must have something to do with neighbour discovery from scratch, whether this is in the kernel or it's some application or firewall that's causing the problem. -- ipv6 stops working after a while https://bugs.launchpad.net/bugs/263260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263260] Re: ipv6 stops working after a while
MikaelA7200Inf3#show ipv6 neighbors MikaelA7200Inf3# No neighbours due to no activity for 8+ hours (I rebooted with 2.6.26-5-generic last night, tried it again this morning (4-6 hours without activity, still worked, then I tried it now after 8+ hours of inactivity and it didn't work)) and the status after trying to send pings from the linux box was the following: MikaelA7200Inf3#show ipv6 neighbors IPv6 Address Age Link-layer Addr State Interface FE80::240:63FF:FEF5:17C20 0040.63f5.17c2 REACH Gi4/0 [EMAIL PROTECTED]:~$ ip -6 n sh 2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router STALE [EMAIL PROTECTED]:~$ ping6 ipv6 PING ipv6(ipv6.swm.pp.se) 56 data bytes ^C --- ipv6 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms [EMAIL PROTECTED]:~$ ip -6 n sh 2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router DELAY [EMAIL PROTECTED]:~$ ip -6 n sh 2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router DELAY [EMAIL PROTECTED]:~$ ping6 ipv6 PING ipv6(ipv6.swm.pp.se) 56 data bytes ^C --- ipv6 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1012ms [EMAIL PROTECTED]:~$ ip -6 n sh 2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router REACHABLE [EMAIL PROTECTED]:~$ ping6 ipv6 PING ipv6(ipv6.swm.pp.se) 56 data bytes ^C --- ipv6 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms [EMAIL PROTECTED]:~$ ip -6 n sh fe80::20a:42ff:fedd:5470 dev eth0 lladdr 00:0a:42:dd:54:70 DELAY 2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router REACHABLE So this problem seems to occur after more than 6 hours of inactivity when the ns has completely timeouted, and I'm affected both by 2.6.26-5-generic and 2.6.27-2-generic. I didn't have this problem with a kernel.org 2.6.26.3 that I compiled myself and ran for 38 days on hardy. Could it be firewall related? I haven't done any configuration on anything like Apparmour or anything like that, so I'm running default settnigs in aspect to any firewall related applications. -- ipv6 stops working after a while https://bugs.launchpad.net/bugs/263260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263260] Re: ipv6 stops working after a while
I've booted 2.6.26-5-generic now and going to let it run for 24 hours and see what happens. IPv6 is working right now after reboot anyway. -- ipv6 stops working after a while https://bugs.launchpad.net/bugs/263260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263260] Re: ipv6 stops working after a while
Hi swmike, You commented that you had no issues with a custom compiled 2.6.26.3 kernel. I'm curious if you were ever able to test a 2.6.26 Ubuntu kernel from Intrepid? The reason I ask is I'm wanting to know if this is specifically a regression with the new 2.6.27 Ubuntu kernel of if it existed also with the 2.6.26 Ubuntu kernel. I know the Alpha4 releases of Intrepid contained a 2.6.26 kernel - http://www.ubuntu.com/testing if you'd be interested in testing. Thanks. -- ipv6 stops working after a while https://bugs.launchpad.net/bugs/263260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263260] Re: ipv6 stops working after a while
After I restarted networking (networking stop, ifconfig eth0 down, networking start, kill dhclient) ipv6 worked for a few hours. now it doesn't again: [EMAIL PROTECTED]:~# ping6 2a00:801:b::1 PING 2a00:801:b::1(2a00:801:b::1) 56 data bytes ^C --- 2a00:801:b::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2013ms The commands asked for: [EMAIL PROTECTED]:# ip -6 n sh 2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router REACHABLE [EMAIL PROTECTED]:# ip -6 r sh 2a00:801:b::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 default via 2a00:801:b::1 dev eth0 metric 1 mtu 1500 advmss 1440 hoplimit 4294967295 [EMAIL PROTECTED]:# ip -6 a sh 1: lo: mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3: eth0: mtu 1500 qlen 1000 inet6 2a00:801:b::10/64 scope global valid_lft forever preferred_lft forever inet6 fe80::240:63ff:fef5:17c2/64 scope link valid_lft forever preferred_lft forever On the cisco: MikaelA7200Inf3#show ipv6 neighbors IPv6 Address Age Link-layer Addr State Interface FE80::240:63FF:FEF5:17C21 0040.63f5.17c2 STALE Gi4/0 MikaelA7200Inf3#debug ipv6 icmp ICMP packet debugging is on MikaelA7200Inf3# Aug 31 23:42:34.898: ICMPv6: Received echo request from 2A00:801:B::10 Aug 31 23:42:34.898: ICMPv6: Sending echo reply to 2A00:801:B::10 Aug 31 23:42:35.914: ICMPv6: Received echo request from 2A00:801:B::10 Aug 31 23:42:35.914: ICMPv6: Sending echo reply to 2A00:801:B::10 Aug 31 23:42:36.914: ICMPv6: Received echo request from 2A00:801:B::10 Aug 31 23:42:36.914: ICMPv6: Sending echo reply to 2A00:801:B::10 Aug 31 23:42:37.914: ICMPv6: Received echo request from 2A00:801:B::10 Aug 31 23:42:37.914: ICMPv6: Sending echo reply to 2A00:801:B::10 Aug 31 23:42:39.898: ICMPv6: Received ICMPv6 packet from FE80::240:63FF:FEF5:17C2, type 135 Aug 31 23:42:44.898: ICMPv6: Received ICMPv6 packet from FE80::240:63FF:FEF5:17C2, type 136 MikaelA7200Inf3#debug ipv6 nd ICMP Neighbor Discovery events debugging is on Aug 31 23:43:47.158: ICMPv6-ND: DELETE -> INCMP: 2A00:801:B::10 Aug 31 23:43:47.158: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Aug 31 23:43:48.158: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Aug 31 23:43:48.170: ICMPv6: Received echo request from 2A00:801:B::10 Aug 31 23:43:48.170: ICMPv6: Sending echo reply to 2A00:801:B::10 Aug 31 23:43:49.158: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Aug 31 23:43:49.170: ICMPv6: Received echo request from 2A00:801:B::10 Aug 31 23:43:49.170: ICMPv6: Sending echo reply to 2A00:801:B::10 Aug 31 23:43:50.158: ICMPv6-ND: INCMP deleted: 2A00:801:B::10 Aug 31 23:43:50.158: ICMPv6-ND: INCMP -> DELETE: 2A00:801:B::10 Aug 31 23:43:50.170: ICMPv6: Received echo request from 2A00:801:B::10 Aug 31 23:43:50.170: ICMPv6: Sending echo reply to 2A00:801:B::10 Aug 31 23:43:50.170: ICMPv6-ND: DELETE -> INCMP: 2A00:801:B::10 Aug 31 23:43:50.174: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Aug 31 23:43:51.170: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Aug 31 23:43:51.170: ICMPv6: Received echo request from 2A00:801:B::10 Aug 31 23:43:51.170: ICMPv6: Sending echo reply to 2A00:801:B::10 Aug 31 23:43:52.154: ICMPv6: Received ICMPv6 packet from FE80::240:63FF:FEF5:17C2, type 135 Aug 31 23:43:52.154: ICMPv6-ND: Received NS for 2A00:801:B::1 on GigabitEthernet4/0 from FE80::240:63FF:FEF5:17C2 Aug 31 23:43:52.158: ICMPv6-ND: Sending NA for 2A00:801:B::1 on GigabitEthernet4/0 Aug 31 23:43:52.158: ICMPv6-ND: STALE -> DELAY: FE80::240:63FF:FEF5:17C2 Aug 31 23:43:52.170: ICMPv6-ND: Sending NS for 2A00:801:B::10 on GigabitEthernet4/0 Aug 31 23:43:52.170: ICMPv6: Received echo request from 2A00:801:B::10 Aug 31 23:43:52.170: ICMPv6: Sending echo reply to 2A00:801:B::10 Aug 31 23:43:53.170: ICMPv6-ND: INCMP deleted: 2A00:801:B::10 Aug 31 23:43:53.170: ICMPv6-ND: INCMP -> DELETE: 2A00:801:B::10 [EMAIL PROTECTED]:~# tcpdump -n -p not ip tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 23:44:48.300611 IP6 2a00:801:b::10 > 2a00:801:b::1: ICMP6, echo request, seq 1, length 64 23:44:49.313502 IP6 2a00:801:b::10 > 2a00:801:b::1: ICMP6, echo request, seq 2, length 64 23:44:50.313515 IP6 2a00:801:b::10 > 2a00:801:b::1: ICMP6, echo request, seq 3, length 64 23:44:51.313515 IP6 2a00:801:b::10 > 2a00:801:b::1: ICMP6, echo request, seq 4, length 64 23:44:52.313516 IP6 2a00:801:b::10 > 2a00:801:b::1: ICMP6, echo request, seq 5, length 64 23:44:53.297484 IP6 fe80::240:63ff:fef5:17c2 > 2a00:801:b::1: ICMP6, neighbor solicitation, who has 2a00:801:b::1, length 32 23:44:53.298330 IP6 2a00:801:b::1 > fe80::240:63ff:fef5:17c2: ICMP6, neighbor ad
[Bug 263260] Re: ipv6 stops working after a while
It'd deserve more info from the linux client. Maybe something interesting in logs, ip -6 n sh, ip -6 r sh, ip -6 a sh As for me, ip6 works fine with the up2date intrepid but I have stateless autoconfiguration in my network (radvd running at a router). -- ipv6 stops working after a while https://bugs.launchpad.net/bugs/263260 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
