Skip to contentSkip to conversation

Trouble Shooting ipsec

DISCUSSION Stephen Clark 3 participants 5 messages Feb 7, 2011 – Feb 8, 2011

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

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

Signature · 5 lines
"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)
#1 lore raw
Quoted 27 lines · Stephen Clark

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

Quoted 8 lines

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

Quoted 15 lines
Signature · 12 lines
"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)



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw
Quoted 47 lines · Neil Horman
Quoted 27 lines · Stephen Clark

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

Quoted 9 lines

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

Quoted 5 lines

Neil

Quoted 1 line

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.

Signature · 5 lines
"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)
maintainer
#3 lore raw

From: Stephen Clark <[email protected]>
Date: Tue, 08 Feb 2011 14:33:17 -0500

Quoted 4 lines

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.

There is a tracepoint (which you can monitor using perf) which tracks all packet drops.

#4 lore raw
Quoted 11 lines · David Miller

From: Stephen Clark <[email protected]>
Date: Tue, 08 Feb 2011 14:33:17 -0500

Quoted 4 lines

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.

There is a tracepoint (which you can monitor using perf) which tracks all packet drops.

+1, you can also use dropwatch to monitor that tracepoint if the drop volume is high.
Neil