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.

[Rudy Zijlstra <rudy@grumpydevil.homelinux.org>]

On 22-06-12 15:04, Roberto C. Sánchez wrote:
> On Fri, Jun 22, 2012 at 01:59:37PM +0200, Rudy Zijlstra wrote:
> > Package: general
> > Severity: important
> > Tags: ipv6
> >
> > 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.
> Could this be something to do with connection tracking?
>
> Regards,
>
> -Roberto
Both IPv4 and IPv6 are impacted, which have separate iptables. IPv6 
routing gets fully blocked, IPv4 goes slow and unpredictable.

How could i check any relation to connection tracking?

cheers,


Rudy