From: Stephen Hemminger <shemminger@vyatta.com>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 16483] New: linux 2.6.30 kernel update to 2.6.34 appear networking's bug
Date: Wed, 4 Aug 2010 09:59:32 -0700 [thread overview]
Message-ID: <20100804095932.19a31d41@nehalam> (raw)
Cryptic bug report, more info in bugzilla comments.
Begin forwarded message:
Date: Fri, 30 Jul 2010 07:57:46 GMT
From: bugzilla-daemon@bugzilla.kernel.org
To: shemminger@linux-foundation.org
Subject: [Bug 16483] New: linux 2.6.30 kernel update to 2.6.34 appear networking's bug
https://bugzilla.kernel.org/show_bug.cgi?id=16483
Summary: linux 2.6.30 kernel update to 2.6.34 appear
networking's bug
Product: Networking
Version: 2.5
Kernel Version: 2.6.34
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: IPV4
AssignedTo: shemminger@linux-foundation.org
ReportedBy: lys0212@qq.com
Regression: No
linux 2.6.30 kernel update to 2.6.34 appear networking's bug
my server machine install linux 5.5 and 2.6.30 kernel,it has two NIC:eth0 and
eth1.
eth0 and eth1 have different's ip and gateway .all configuration is normal.i
can ping both the eth0 and eth1 .but,when i update to kernel 2.6.34,i can't
ping both the eth0 and eth1,only can ping the eth0 when the default gw is
eth0's gw.when i change the default gw to eth1's gw ,i can ping the eth1
only,eth0 can't ping .Very strange!
when i use the kernel 2.6.30 to boot the system ,all is normal ,i can ping both
eth0 and eth1 .but when i use the kernel 2.6.34,one of the ethX is normal only.
the follows show how i update 2.6.30 to 2.6.34:
mv linux-2.6.34.tar.bz2 /usr/src
cd /usr/src/
tar -xvf linux-2.6.34.tar.bz2
ln -s /usr/src/linux-2.6.34 /usr/src/linux
cd linux
make menuconfig
#cp the boot initilization configuration to /usr/src/linux/.config
cp /boot/config-2.6.18-194.el5 /usr/src/linux/.config
make menuconfig
# choose ip range network -> Netfilter > Core NetFilter >iprange
select:
（1）General setup ---> Prompt for development and/or incomplete code/drivers。
（2） Networking ---> Networking options ---> Network packet filtering framework
(Netfilter) ---> Core Netfilter Configuration ---> 和 IP: Netfilter
Configuration ---> (select all)
vi .config
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_SYSFS_DEPRECATED_V2=y
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
--
reply other threads:[~2010-08-04 16:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100804095932.19a31d41@nehalam \
--to=shemminger@vyatta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).