Bug#678519: general: after about 1 month of uptime, routing of IPv6 packets is no longer possible, and IPv4 routing becomes slow and unpredictable. Rebooting brings all functionality back, and back to speed. so far the best way for me to discover is to try a ping6, and reboot the firewall (this machine), when ping6 from the inner network fails.

[Jonathan Nieder <jrnieder@gmail.com>]

retitle 678519 after about a month, routing gets wedged
# not a general problem affecting a large portion of the archive
reassign 678519 base
tags 678519 + squeeze
quit

Hi Henrique,

Henrique de Moraes Holschuh wrote:
> On Fri, 22 Jun 2012, Rudy Zijlstra wrote:

>> let system run with IPv4 & IPv6 routing for about 1 month
>>> IPv6 routing will start to fail
>>> IPv4 routing becomes slow and unpredictable
>>
>> no obvious causes visible in the system. top and friends do not show a cpu hog
>>
>> a reboot will bring the system back to normal behaviour. 
>
> Please use (as root) "ip neigh show", and "ip route list cache" to try to
> track down any weird differences between the box when it is behaving
> normally, and the box when wedged.  You may want to compare it to a healthy
> box on the same network segment.

Thanks for starting to track this down.  Any idea which package might
be responsible?

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?

Thanks,
Jonathan