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.

To: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>, 678519@bugs.debian.org
Subject: 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.
From: Roberto C. Sánchez <roberto@connexer.com>
Date: Fri, 22 Jun 2012 09:04:56 -0400
Message-id: <[🔎] 20120622130456.GA7336@connexer.com>
Mail-followup-to: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>, 678519@bugs.debian.org
Reply-to: Roberto C. Sánchez <roberto@connexer.com>, 678519@bugs.debian.org
In-reply-to: <[🔎] 20120622115937.1905.22529.reportbug@janus.office.romunt.nl>
References: <[🔎] 20120622115937.1905.22529.reportbug@janus.office.romunt.nl>

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
-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com

Attachment: signature.asc
Description: Digital signature

Reply to:

Follow-Ups:
- 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.
  - From: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>

References:
- 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.
  - From: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>