From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: mmotm 2010-03-23 - IPv6 warnings...
Date: Thu, 25 Mar 2010 12:45:30 -0400 [thread overview]
Message-ID: <4788.1269535530@localhost> (raw)
In-Reply-To: Your message of "Wed, 24 Mar 2010 18:42:26 EDT." <20100324184226.3bf42d8f.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
On Wed, 24 Mar 2010 18:42:26 EDT, Andrew Morton said:
> On Wed, 24 Mar 2010 21:36:41 -0400 Valdis.Kletnieks@vt.edu wrote:
>
> > On Tue, 23 Mar 2010 15:34:59 PDT, akpm@linux-foundation.org said:
> > > The mm-of-the-moment snapshot 2010-03-23-15-34 has been uploaded to
> > >
> > > http://userweb.kernel.org/~akpm/mmotm/
> >
> > Seen in my dmesg. It may be relevant that I'm at home, and my IPv6
> > prefix arrives via a PPP VPN connection. This happened about 20-25 seconds
> > after I launched pppd.
>
> Yes, thanks, I get the same - it doesn't seem to break anything. It
> also happens some time after boot has completed.
Just doing an 'ifup eth0' on a network with IPv6 on it is sufficient.
And it does break stuff:
% ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:24:E8:C6:AD:17
inet addr:128.173.14.107 Bcast:128.173.15.255 Mask:255.255.252.0
inet6 addr: fe80::224:e8ff:fec6:ad17/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
With 2.6.34-rc1-mmotm0309, I see:
% ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:24:E8:C6:AD:17
inet addr:128.173.14.107 Bcast:128.173.15.255 Mask:255.255.252.0
inet6 addr: 2001:468:c80:2103:224:e8ff:fec6:ad17/64 Scope:Global
inet6 addr: fe80::224:e8ff:fec6:ad17/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Something ate my IPv6 address. We run a lot of IPv6 in production, so stuff
is acting wonky.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-03-25 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 22:34 mmotm 2010-03-23-15-34 uploaded akpm
2010-03-24 16:58 ` mmotm 2010-03-23-15-34 uploaded (staging vs. media) Randy Dunlap
2010-03-24 18:21 ` Mauro Carvalho Chehab
2010-03-24 19:18 ` [PATCH -mmotm] leds-input: depends on INPUT Randy Dunlap
2010-03-24 21:02 ` Pavel Machek
2010-03-24 23:06 ` Samuel Thibault
2010-03-25 1:36 ` mmotm 2010-03-23 - IPv6 warnings Valdis.Kletnieks
2010-03-24 22:42 ` Andrew Morton
2010-03-25 16:45 ` Valdis.Kletnieks [this message]
2010-03-25 20:25 ` David Miller
2010-03-26 4:40 ` David Miller
2010-03-26 6:18 ` Valdis.Kletnieks
2010-03-26 6:23 ` David Miller
2010-03-28 3:32 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4788.1269535530@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.