Forum Discussion
IPSec protocol 50 unreachable
IPSec protocol 50 unreachable
anyone see this before?
13:18:12.263595 IP 166.130.153.10.500 > 134.186.111.134.500: isakmp: phase 1 I ident 13:18:13.492500 IP 166.130.152.195 > 134.186.111.134: ESP(spi=0xdaae26d3,seq=0xe5), length 100 13:18:13.493080 IP 134.186.111.131 > 166.130.152.195: ICMP 134.186.111.131 protocol 50 unreachable, length 128
2 Replies
- Victor_Oshiots1
Nimbostratus
Hi,
Please were you able to resolve this.
Thanks
- Rob_Stonham
Cirrus
Hi,
You don't say which end is which so I'm assuming that 134.186.11.134 is your local end and 166.130.152.195 is the remote end. This looks like the remote end is blocking ESP traffic. Myself and Victor recently come across a similar issue, but it was our local F5 BIG-IP that was generating the ICMP protocol 50 unreachable response.
I found that in our case the BIG-IP had wrong setting:
tmsh list sys db ipsec.lookupspi sys db ipsec.lookupspi { value "disable" }As in our case the BIG-IP was the IPSEC endpoint we needed to change the setting to:
tmsh list sys db ipsec.lookupspi sys db ipsec.lookupspi { value "enable" }using the command:
tmsh modify sys db ipsec.lookupspi value enable tmsh save sys configThe KB article SOL14169 shows that the setting may need disabling if the BIG-IP is NOT terminating the IPSEC traffic, but this implies that if the BIG-IP IS terminating IPSEC traffic the setting needs to be enabled.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com