Your message dated Thu, 30 Jul 2020 13:57:29 +0200 with message-id <[email protected]> and subject line Re: Bug#769824: base: IPv6 networking issues after assigning more that 32 addresses has caused the Debian Bug report #769824, regarding base: IPv6 networking issues after assigning more that 32 addresses 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 769824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769824 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: base Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? On a system where I like to have various individual web/mail-environments I want each individual to have differen addrsses for pop3, pop3s, imap, imaps, http, rsync, etc... So I get PREFIX::6:<port>:<uid>. * What exactly did you do (or not do) that was effective (or ineffective)? I assign the ip's with: ip -6 address add <ip6> dev eth0 preferred_lft 0 The use of preferred_lft 0 is because I want a predefined address for outgoing communication * What was the outcome of this action? After Iassigned 33rd, 34th, etc ipv6 address to eth0 the system started behaving erratically; shell connection fails/sql connection fails/icmp fails. * What outcome did you expect instead? I expected the same stable operation as for the first 32 addresses. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: x86_64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---* A.P.C. Rijnart <[email protected]> [200730 11:56]: > Debian Release: 7.7 > Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU cores) This bug affects a very old release, and it's unclear if the problem still exists on the current stable release or in unstable. If it does, please file a new bug against the package most likely causing this (might be the then-current linux kernel package). Chris
--- End Message ---
