aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/keyid2sql.c
diff options
context:
space:
mode:
authorTobias Brunner <tobias@strongswan.org>2014-10-10 12:55:39 +0200
committerTobias Brunner <tobias@strongswan.org>2014-10-13 15:20:17 +0200
commit472156eea5ce67d9769ed2f3f9ff24e48460d4e9 (patch)
treefc0c06382df34fafcbc4d3325de56bd4e31b024e /scripts/keyid2sql.c
parentf8a565fbccbe077583f556d2148041d3b1de5580 (diff)
downloadstrongswan-472156eea5ce67d9769ed2f3f9ff24e48460d4e9.tar.bz2
strongswan-472156eea5ce67d9769ed2f3f9ff24e48460d4e9.tar.xz
ike: Do remote address updates also when behind static NATs
We assume that a responder is behind a static NAT (e.g. port forwarding) and allow remote address updates in such situations. The problem described in RFC 5996 is only an issue if the NAT mapping can expire.
Diffstat (limited to 'scripts/keyid2sql.c')
0 files changed, 0 insertions, 0 deletions