From: krunal <krunal.patel@elitecore.com>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: e100 driver not working when bridge and vlan configured.
Date: Mon, 17 May 2010 22:51:14 +0530 [thread overview]
Message-ID: <4BF17B0A.70309@elitecore.com> (raw)
I have seen this bug in many threads also checked
"http://www.mailinglistarchive.com/xen-users@lists.xensource.com/msg19768.html",
but nothing works for me.
I am having 4 nics, driver for 2 nics is e1000 and 2 nics is e100.
Setup
( 192.168.1.1)br0-----------eth0
|-------------eth1
traffic flows through my bridge machine and i can ping 192.168.1.1, vlan
traffic also pass through it.
I am not able to ping 192.168.1.1 using vlan interface
so i created and added vlan interfaces to bridge
( 192.168.1.1)br0-----------eth0
|-------------eth1
|-------------eth0.3
|-------------eth1.3
Still i am not able to ping 192.168.1.1.
I then removed eth0, and eth1 from br0
( 192.168.1.1)br0-----------eth0.3
|-------------eth1.3
Now I am able to ping 192.168.1.1
My kernel is linux-2.6.27.45 and e100 driver is "3.5.23-k4-NAPI" which
comes with kernel.
Same scenario works fine with e1000 driver.
This bug is already reported and i am not able to find any patch for it.
Regards,
Krunal
reply other threads:[~2010-05-17 11:58 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=4BF17B0A.70309@elitecore.com \
--to=krunal.patel@elitecore.com \
--cc=linux-kernel@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.