netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Clark <sclark46@earthlink.net>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Trouble Shooting ipsec
Date: Tue, 08 Feb 2011 14:33:17 -0500	[thread overview]
Message-ID: <4D519A7D.5010405@earthlink.net> (raw)
In-Reply-To: <20110208183527.GA7450@hmsreliant.think-freely.org>

On 02/08/2011 01:35 PM, Neil Horman wrote:
> On Mon, Feb 07, 2011 at 02:17:55PM -0500, Stephen Clark wrote:
>    
>> Hello,
>>
>> How do I find out what is happening to my packets thru my ipsec tunnel.
>> They just seem to disappear on the remote side.
>>
>> I have successfully got the pings thru
>> when everything has an ipv6 address, but am not successful when trying
>> to connect two ipv4 lans across an ipv6 ipsec tunnel. All fw chains
>> both 4 and 6
>> are set to ACCEPT. NAT is turned off.
>>
>>       eth0               eth1
>> eth1                 eth0
>> 10.1.254.254/17  2001:xxxx:1628::254<----ipv6 internet ----->
>> 2001:xxxx:e334::254  10.0.254.254/17
>>
>> 12:00:02.296972 IP6 2001:xxxx:1628::254>  2001:xxxx:e334::254:
>> ESP(spi=0x07454bc3,seq=0x28b), length 132
>> 12:00:03.308751 IP6 2001:xxxx:1628::254>  2001:xxxx:e334::254:
>> ESP(spi=0x07454bc3,seq=0x28c), length 132
>> 12:00:04.296857 IP6 2001:xxxx:1628::254>  2001:xxxx:e334::254:
>> ESP(spi=0x07454bc3,seq=0x28d), length 132
>> 12:00:05.293748 IP6 2001:xxxx:1628::254>  2001:xxxx:e334::254:
>> ESP(spi=0x07454bc3,seq=0x28e), length 132
>> 12:00:06.296623 IP6 2001:xxxx:1628::254>  2001:xxxx:e334::254:
>> ESP(spi=0x07454bc3,seq=0x28f), length 132
>>
>> I have posted to the ipsec-devel list and haven't gotten any
>> responses. Also I have spent 2 days googling with
>> no results about the above setup. Is it even possible to tunnel ipv4
>> packet thru an ipv6 ipsec tunnel?
>>
>> Thanks,
>> Steve
>>
>>      
> I'd start by looking at your stats counters to see if you're dropping anything
> significat.  It appears from what you have above that you're receiving end is
> getting encapsulated packets, so at least your tunnel is functional.  Take a
> look at proc/net/snmp and see if any counters get bumped as you send data.  I
> expect you're loosing them somewhere during decode (which would show up in
> /proc/net/xfrm_stat), or you're loosing them after you decode them and try to
> receive/forward them (which would likely show up in /proc/net/snmp).  That
> should give you a clue as to where to look next
>
> Neil
>
>    
>>      
>    
Thanks for the tip. I wasn't aware of /proc/net/xfrm_stat

I was able to work around by creating an ipv6 to ipv6 ipsec tunnel
and then creating an ipip6 tunnel inside of ipv6-ipv6 ipsec tunnel.

I'll continue investigating. It just so frustrating when the ipsec packets
just get dropped and you have no idea why. I wish there were some hooks
in the kernel so you could at least get some debug information about what is
happening.



-- 

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)




  reply	other threads:[~2011-02-08 19:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 19:17 Trouble Shooting ipsec Stephen Clark
2011-02-08 18:35 ` Neil Horman
2011-02-08 19:33   ` Stephen Clark [this message]
2011-02-08 19:37     ` David Miller
2011-02-08 21:37       ` Neil Horman

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=4D519A7D.5010405@earthlink.net \
    --to=sclark46@earthlink.net \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    /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).