[Openswan Users] Road Warrior behind NAT - Aggressive Mode: wrong NAT-T decision

[hiren joshi]

Is there any known issue in 2.4.9 related to wrong NAT-T detection in
the following type of setup:

RW behind NAT using aggressive mode

openswan --- gw --- router --- NATbox --- RW

openswan detects NAT-Traversal as "both are NATed" instead of "peer is NATed".

Later on I receive,
DPD: Serious: could not find newest phase 1 state
DPD: Warning: received old or duplicate R_U_THERE

After some time client breaks the connection due of not getting
DPD_R_U_THERE_ACK

Thanks for your time.

-hiren