From: zhuyj <zyjzyj2000@gmail.com>
To: sandeep.kumar@freescale.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, "Tao, Yue" <Yue.Tao@windriver.com>,
"Yang, Zhangle (Eric)" <Zhangle.Yang@windriver.com>,
guang.yang@windriver.com, zhuyj <zyjzyj2000@gmail.com>,
joe@perches.com, festevam@gmail.com,
linuxppc-dev@lists.ozlabs.org, richardcochran@gmail.com,
clarocq@gmail.com, yongjun_wei@trendmicro.com.cn
Subject: on kernel 2.6.34.15, vlan and raw packets can not be received with gfar-enet nic
Date: Tue, 25 Mar 2014 13:08:30 +0800 [thread overview]
Message-ID: <53310F4E.4080104@gmail.com> (raw)
Hi, Sandeep Gopalpet
I am a developer. Now I confronted an interesting phenomena. When I used
linux kernel 2.6.34.15 on freescale-p2020, I can not receive raw and
vlan packets on gfar-enet nic. But with e1000e nic, we can make vlan and
raw packets work well. I looked into the source code and find that maybe
it is related with hardware insert and remove vlan head. But I have no
the specifications of gfar-enet nic. Would you like to give some
document or some guides?
Thanks a lot.
Zhu Yanjun
The steps are as below.
1. I boot two freescale-p2020 boards with linux kernel 2.6.34.15, then I
connected 2 gfar-enet nic cards with a direct network line;
2. On board 1, I checked the driver of eth0
ethtool -i eth0
driver: gfar-enet
version: 1.3
firmware-version: N/A
bus-info: N/A
On board 2, I checked the driver of eth1
ethtool -i eth1
driver: gfar-enet
version: 1.3
firmware-version: N/A
bus-info: N/A
3. Then I configure the ip address on the above 2 nic cards.
On board 1,
ifconfig eth0 192.168.1.13/24 up
On board 2,
ifconfig eth1 192.168.1.196/24 up
4. We can access the other board on one board.
For example, on board 1, we can ping board 2.
root@p2020rdb:/root> ping 192.168.1.196
PING 192.168.1.196 (192.168.1.196) 56(84) bytes of data.
64 bytes from 192.168.1.196: icmp_req=1 ttl=64 time=2.92 ms
64 bytes from 192.168.1.196: icmp_req=2 ttl=64 time=0.096 ms
5. We configure vlan on these 2 boards.
On board 1,
modprobe 8021q
vconfig add eth0 4091
ifconfig eth0.4091 10.1.1.13/24 up
On board 2,
modprobe 8021q
vconfig add eth1 4091
ifconfig eth1.4091 10.1.1.196/24 up
6. We can access the other board on one board through vlan.
For example, on board 1, we can ping board 2 through vlan nic.
root@p2020rdb:/root> ping 10.1.1.196
PING 10.1.1.196 (10.1.1.196) 56(84) bytes of data.
64 bytes from 10.1.1.196: icmp_req=1 ttl=64 time=2.92 ms
64 bytes from 10.1.1.196: icmp_req=2 ttl=64 time=0.096 ms
But we can not access the other board on one board through raw nic.
For example, on board, we can not ping board 2.
root@p2020rdb:/root> ping 192.168.1.196
From 192.168.1.196 icmp_seq=1 Destination Host Unreachable
From 192.168.1.196 icmp_seq=2 Destination Host Unreachable
From 192.168.1.196 icmp_seq=3 Destination Host Unreachable
next reply other threads:[~2014-03-25 5:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 5:08 zhuyj [this message]
2014-04-03 9:11 ` on kernel 2.6.34.15, vlan and raw packets can not be received with gfar-enet nic zhuyj
2014-04-03 9:27 ` Willy Tarreau
2014-04-03 9:57 ` zhuyj
2014-04-03 10:01 ` Willy Tarreau
2014-04-03 10:18 ` zhuyj
2014-04-03 10:15 ` zhuyj
2014-04-03 10:21 ` Willy Tarreau
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=53310F4E.4080104@gmail.com \
--to=zyjzyj2000@gmail.com \
--cc=Yue.Tao@windriver.com \
--cc=Zhangle.Yang@windriver.com \
--cc=clarocq@gmail.com \
--cc=festevam@gmail.com \
--cc=guang.yang@windriver.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=sandeep.kumar@freescale.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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).