From: Alex <d77190@mail.ru>
To: Cong Wang <cwang@twopensource.com>
Cc: netdev@vger.kernel.org
Subject: Re: Bug 75571
Date: Fri, 06 Jun 2014 11:13:01 +0700 [thread overview]
Message-ID: <1402027981.29664.16.camel@anpws> (raw)
In-Reply-To: <CAHA+R7Mi-mBXWSytEtJhqEfjYQyrd9zae5GndYy3qmK=+_mk_g@mail.gmail.com>
> Hmm, e1000e should init dev->hard_header_len to ETH_LEN, which is 14.
> Plus IPv4 header len (20), it should be about 34. I don't understand why
> the ipip tunnel's hard_header_len is 148 in your case. It is only possible when
> there is no underlying interface, that is, LL_MAX_HEADER + sizeof(struct iphdr).
>
> What do `ip -d link show` and `ip route show` say?
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 1000
link/ether 00:15:17:28:a7:02 brd ff:ff:ff:ff:ff:ff
7: eth0.99@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP mode DEFAULT group default
link/ether 00:15:17:28:a7:02 brd ff:ff:ff:ff:ff:ff
vlan protocol 802.1q id 99 <REORDER_HDR>
84: tun4177: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc htb state
UNKNOWN mode DEFAULT group default
link/ipip 192.168.18.199 peer 192.168.18.17
192.168.18.199 is loopback address.
ip route show dev eth0.99
172.16.254.132/30 proto kernel scope link src 172.16.254.134
192.168.18.0/26 via 172.16.254.133 proto zebra
.... and about 200 networks received via BGP
ip route show dev tun4177
198.18.0.177 proto kernel scope link src 198.18.0.1
198.18.100.3 via 198.18.0.177 proto zebra metric 17
.... and about 500 routes to hosts recieved via OSPF
next prev parent reply other threads:[~2014-06-06 4:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 6:20 Bug 75571 Alex
2014-06-01 14:43 ` Emil Goode
2014-06-02 10:32 ` Alex
2014-06-02 17:38 ` Cong Wang
2014-06-02 21:19 ` Cong Wang
2014-06-04 8:31 ` Alex
2014-06-05 0:27 ` Cong Wang
2014-06-05 5:22 ` Alex
2014-06-05 19:18 ` Cong Wang
2014-06-06 4:13 ` Alex [this message]
2014-06-09 23:49 ` Cong Wang
2014-06-14 19:29 ` Alex
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=1402027981.29664.16.camel@anpws \
--to=d77190@mail.ru \
--cc=cwang@twopensource.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