Bug#678519: after about a month, routing gets wedged
On 08-07-12 03:02, Jonathan Nieder wrote: Rudy Zijlstra wrote: Still using it. Its my firewall. Sorry for missing the questions. Yes, sorry about the clutter in my message. [...] 1/ always behaved this way Not certain. [...] 2/ how many times? at least twice. Its well possible that earlier cases were masked by reboots from other reasons. And it has taken me some time before i linked particular slow network behaviour to a firewall problem 3/ how stable is the 1 month gestation time? no certainty on this one. OK, problem is back. About 3 days more then 1 month. IPv4 browsing is very slow, IPv6 routing is down. I can no longer ping6 ipv6.google.com. It gets the record, but no responses. Not even when doing it on the firewall itself. output on June 25: == IPv6 == ip -f inet6 neigh show 2001:610:73e:0:f53f:5d0e:28cc:3479 dev eth2 lladdr f0:4d:a2:fa:5c:67 REACHABLE 2001:610:73e:0:225:64ff:fea4:928e dev eth2 lladdr 00:25:64:a4:92:8e REACHABLE 2001:610:73e:0:d6be:d9ff:fe12:73f0 dev eth2 lladdr d4:be:d9:12:73:f0 REACHABLE 2001:610:73e:0:206:5bff:fef7:45e5 dev eth2 lladdr 00:06:5b:f7:45:e5 REACHABLE fe80::208:2ff:fea3:d56b dev eth2 lladdr 00:08:02:a3:d5:6b router STALE ip -f inet6 route list cache 2001:610:73e:0:206:5bff:fef7:45e5 via 2001:610:73e:0:206:5bff:fef7:45e5 dev eth2 metric 0 cache mtu 1500 advmss 1440 hoplimit 0 2001:610:73e:0:225:64ff:fea4:928e via 2001:610:73e:0:225:64ff:fea4:928e dev eth2 metric 0 cache mtu 1500 advmss 1440 hoplimit 0 2001:610:73e:0:d6be:d9ff:fe12:73f0 via 2001:610:73e:0:d6be:d9ff:fe12:73f0 dev eth2 metric 0 cache mtu 1500 advmss 1440 hoplimit 0 2001:610:73e:0:f53f:5d0e:28cc:3479 via 2001:610:73e:0:f53f:5d0e:28cc:3479 dev eth2 metric 0 cache mtu 1500 advmss 1440 hoplimit 0 Current output: # ip -f inet6 neigh show 2001:610:73e:0:21b:21ff:fe22:b647 dev eth2 lladdr 00:1b:21:22:b6:47 STALE 2001:610:73e::15 dev eth2 lladdr 00:25:64:a4:92:8e REACHABLE fe80::208:2ff:fea3:d56b dev eth2 lladdr 00:08:02:a3:d5:6b router STALE fe80::21b:21ff:fe22:b647 dev eth2 lladdr 00:1b:21:22:b6:47 DELAY # ip -f inet6 route list cache 2001:610:73e::15 via 2001:610:73e::15 dev eth2 metric 0 cache mtu 1500 advmss 1440 hoplimit 0 2001:610:73e:0:21b:21ff:fe22:b647 via 2001:610:73e:0:21b:21ff:fe22:b647 dev eth2 metric 0 cache mtu 1500 advmss 1440 hoplimit 0 ip -f inet6 route flush makes no difference. Neither flushing the neighbor cache ifdown / ifup of the external ethernet port makes no difference rmmod tg3 removed both interfaces (so the driver does indeed handle those ports) followed by modprobe tg3 made no difference either. package firmware-linux-nonfree is current. stopping aiccu, rmmod sit and tunnel4 and then reloading and restarting aiccu did solve it Next time i will start with restarting aiccu, and not rmmoding the related modules Cheers, Rudy -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/501453d6.2060...@grumpydevil.homelinux.org
Bug#678519: after about a month, routing gets wedged
On Sat, 28 Jul 2012, Rudy Zijlstra wrote: stopping aiccu, rmmod sit and tunnel4 and then reloading and restarting aiccu did solve it Next time i will start with restarting aiccu, and not rmmoding the related modules Hmm, okay. That should help narrow it down a lot. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120729023827.gb3...@khazad-dum.debian.net
Bug#678519: after about a month, routing gets wedged
Jonathan Nieder wrote: Rudy, is this a regression, or has this system always behaved this way? How many times has it happened? How reliable is the 1 month gestation time? When did it start? Ping. Do you still have access to this machine? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120707195752.GA4957@burratino
Bug#678519: after about a month, routing gets wedged
On 07-07-12 21:57, Jonathan Nieder wrote: Jonathan Nieder wrote: Rudy, is this a regression, or has this system always behaved this way? How many times has it happened? How reliable is the 1 month gestation time? When did it start? Ping. Do you still have access to this machine? Still using it. Its my firewall. Sorry for missing the questions. With the combination of top/bottom posting i had missed the bottom part. Your questions: 1/ always behaved this way Not certain. I installed it, then there were a number of changes that also had impact on the firewall, which caused some reboots (like changing to new version of squid3 iso squid2). Strictly not needed to reboot, but after major changes i always test whether the sytem comes back correctly from reboot. I also had some squeeze kernel updates, which do need a reboot. 2/ how many times? at least twice. Its well possible that earlier cases were masked by reboots from other reasons. And it has taken me some time before i linked particular slow network behaviour to a firewall problem 3/ how stable is the 1 month gestation time? no certainty on this one. After the last time i had confirmation this was a firewall problem, and had confirmation for 2x. thinking back the timespan between the 2 certain occasions is 3 - 4 weeks. But i did not keep a record. 4/ When did it start Do not know. See above cheers, Rudy -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff8d82f.2090...@grumpydevil.homelinux.org
Bug#678519: after about a month, routing gets wedged
Rudy Zijlstra wrote: Still using it. Its my firewall. Sorry for missing the questions. Yes, sorry about the clutter in my message. [...] 1/ always behaved this way Not certain. [...] 2/ how many times? at least twice. Its well possible that earlier cases were masked by reboots from other reasons. And it has taken me some time before i linked particular slow network behaviour to a firewall problem 3/ how stable is the 1 month gestation time? no certainty on this one. Ok. In case you're wondering where these questions come from: it is an attempt to find what variable changed to introduce the bug. If your system always behaved this way, it would mean something very different than if it started happening when upgrading from lenny to squeeze, for example. I'll leave the rest of the investigation to people more knowledgeable about networking. For now, please attach - full output from dmesg after a normal boot - output from reportbug --template linux-image-$(uname -r), so we can get to know your hardware. Thanks again and sorry for the trouble, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120708010239.GA10915@burratino
