Your message dated Thu, 24 Jan 2008 22:12:34 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Problem was caused by bad init script order
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: tspc
Version: 2.1.1-6
Severity: normal

Hello,

after kernel 2.6.18 from etch was replaced by version 2.6.22 from lenny,
the IPv6 tunnel becomes unusable after some minutes of inactivity.
But the network device "sit1" still exists and it is the default route.
This breaks other programs, which depend on a correct working network/routing,
e.g. fetchmail, browser, ping6.

I have found the following workaround:
ping6 -i 240 <foreign IPv6 address>

An interval of 360 seconds is to large, so that only the first pings are
successfull.


Greetings
        Juergen

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i586)

Kernel: Linux 2.6.22-3-486
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages tspc depends on:
ii  iproute                       20071016-3 Professional tools to control the 
ii  libc6                         2.7-5      GNU C Library: Shared libraries
ii  net-tools                     1.60-19    The NET-3 networking toolkit

Versions of packages tspc recommends:
ii  radvd                         1:1.0-2    Router Advertisement Daemon

-- no debconf information

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.




--- End Message ---
--- Begin Message ---
Hello,

after rearanging the start-up scripts in /etc/rc?.d the problem seems to be solved.


Greetings
        Juergen


--- End Message ---

Reply via email to