netdev - Re: Fwd: [Bug 470774] New: [RFC1981-PMTU]Multicast Destination

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 12 Nov 2008 10:12:03 -0500
From:	Brian Haley <brian.haley@...com>
To:	wang_jiabo <jiabwang@...hat.com>
Cc:	dave jones <davej@...hat.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Fwd: [Bug 470774] New: [RFC1981-PMTU]Multicast Destination -
 One	Router test failed

>> 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@...dor.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html