From: Alexey Dobriyan <adobriyan@gmail.com>
To: netdev@vger.kernel.org
Subject: more info on ipsec-related invalid trusize
Date: Tue, 25 Nov 2008 07:28:57 +0300 [thread overview]
Message-ID: <20081125042752.GA4085@x200.localdomain> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=10996
http://marc.info/?l=linux-netdev&m=122641698504902&w=2
SKB BUG: Invalid truesize (344) len=134, sizeof(sk_buff)=216
This correlates with ping6 the box to death with the following IPsec
configuration and entering/leaving tcpdumping on the other end.
Numbers are always the same.
It _looks_like_ IPv4 ping is fine, but I haven't experimented much.
#!/usr/sbin/setkey -f
flush;
spdflush;
add 192.168.0.1 192.168.0.42 ah 15700 -A hmac-md5 "1234567890123456";
add 192.168.0.1 192.168.0.42 esp 15701 -E 3des-cbc "123456789012123456789012";
add 192.168.0.42 192.168.0.1 ah 24500 -A hmac-md5 "1234567890123456";
add 192.168.0.42 192.168.0.1 esp 24501 -E 3des-cbc "123456789012123456789012";
spdadd 192.168.0.42 192.168.0.1 any -P out ipsec
esp/transport//require
ah/transport//require;
spdadd 192.168.0.1 192.168.0.42 any -P in ipsec
esp/transport//require
ah/transport//require;
# ipv6
add -6 fe80::218:f3ff:fea2:9f90 fe80::21b:38ff:feaf:2249 ah 4242 -A hmac-md5 "1234567890123457";
add -6 fe80::218:f3ff:fea2:9f90 fe80::21b:38ff:feaf:2249 esp 4243 -E 3des-cbc "123456789012123456789012";
add -6 fe80::21b:38ff:feaf:2249 fe80::218:f3ff:fea2:9f90 ah 4244 -A hmac-md5 "1234567890123457";
add -6 fe80::21b:38ff:feaf:2249 fe80::218:f3ff:fea2:9f90 esp 4245 -E 3des-cbc "123456789012123456789012";
spdadd fe80::21b:38ff:feaf:2249 fe80::218:f3ff:fea2:9f90 any -P out ipsec
esp/transport//require
ah/transport//require;
spdadd fe80::218:f3ff:fea2:9f90 fe80::21b:38ff:feaf:2249 any -P in ipsec
esp/transport//require
ah/transport//require;
next reply other threads:[~2008-11-25 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 4:28 Alexey Dobriyan [this message]
2008-11-25 10:52 ` more info on ipsec-related invalid trusize Herbert Xu
2008-11-26 5:50 ` David Miller
2008-11-26 5:57 ` Herbert Xu
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=20081125042752.GA4085@x200.localdomain \
--to=adobriyan@gmail.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