Prev: [PATCH] Staging: comedi: Altered the way printk is used in 8255.c
Next: [ANNOUNCE] GSoC project: Improving kconfig using a SAT solver
From: krunal on 17 May 2010 08:00
I have seen this bug in many threads also checked
"http://www.mailinglistarchive.com/xen-users(a)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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH] Staging: comedi: Altered the way printk is used in 8255.c
Next: [ANNOUNCE] GSoC project: Improving kconfig using a SAT solver