From: Brian Haley <brian.haley@hp.com>
To: wang_jiabo <jiabwang@redhat.com>
Cc: dave jones <davej@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Fwd: [Bug 470774] New: [RFC1981-PMTU]Multicast Destination - One Router test failed
Date: Wed, 12 Nov 2008 10:12:03 -0500 [thread overview]
Message-ID: <491AF243.9040904@hp.com> (raw)
In-Reply-To: <491A7571.4020905@redhat.com>
>> So which TAHI test was this? Have they tracked down a commit that
>> caused this to break?
> I use TAHI 4-0-3 RFC1981, if you can access my website , please see
> http://10.66.65.20/self_test/ipv6-core/Self_Test_4-0-3_F10/
That looks like an internal link. Either way, I'm guessing this was
test 13 (Checking For Increase in PMTU), which passed for RHEL 5.3
recently I think.
>>> Version-Release number of selected component (if applicable):
>>> 2.6.27-0.352.rc7.git1.fc10.i686
>>
>> Hmmm, I would take a look at this commit:
>>
>> commit b5c15fc004ac83b7ad280acbe0fd4bbed7e2c8d4
>> Author: Herbert Xu <herbert@gondor.apana.org.au>
>> Date: Thu Feb 14 23:49:37 2008 -0800
>>
>> [IPV6]: Fix reversed local_df test in ip6_fragment
>>
>> I managed to reverse the local_df test when forward-porting this
>> patch so it actually makes things worse by never fragmenting at
>> all.
>>
>> Thanks to David Stevens for testing and reporting this bug.
>>
>> Bill Fink pointed out that the local_df setting is also the wrong
>> way around.
So can you verify your kernel has this fix? Or can you run a later
kernel and see if it's fixed?
> I check using the command, get the following info:
> #cat /proc/net/dev_snmp6/eth0|grep -i frag
> Ipv6FragOKs 0
> Ipv6FragFails 0
> Ip6FragCreates 0
You'll actually want to look at eth1, which is where the pings are going
out, I was just giving that as an example.
-Brian
prev parent reply other threads:[~2008-11-12 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 17:42 Fwd: [Bug 470774] New: [RFC1981-PMTU]Multicast Destination - One Router test failed Dave Jones
2008-11-11 19:50 ` Brian Haley
[not found] ` <491A7571.4020905@redhat.com>
2008-11-12 15:12 ` Brian Haley [this message]
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=491AF243.9040904@hp.com \
--to=brian.haley@hp.com \
--cc=davej@redhat.com \
--cc=jiabwang@redhat.com \
--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.