From 2a4ec066046a5953527e496226f10171e229ae3e Mon Sep 17 00:00:00 2001
From: Anders Svensson
Date: Sat, 19 Aug 2017 14:56:15 +0200
Subject: Handle loopback/any as local address in diameter_tcp/sctp
The support is implied by documentation, but wasn't handled in code. Be
consistent in retrieving the address from the sock rather than the
configuration, and in accepting both ip and ifaddr for a local address.
---
lib/diameter/doc/src/diameter_tcp.xml | 13 +++++--------
1 file changed, 5 insertions(+), 8 deletions(-)
(limited to 'lib/diameter/doc/src/diameter_tcp.xml')
diff --git a/lib/diameter/doc/src/diameter_tcp.xml b/lib/diameter/doc/src/diameter_tcp.xml
index 6ca280c52b..1d65d14257 100644
--- a/lib/diameter/doc/src/diameter_tcp.xml
+++ b/lib/diameter/doc/src/diameter_tcp.xml
@@ -170,14 +170,11 @@ that will not be forthcoming, which will eventually cause the RFC 3539
watchdog to take down the connection.
-If an ip option is not specified then the first element of a
-non-empty Host-IP-Address list in Svc provides the local
-IP address.
-If neither is specified then the default address selected by &gen_tcp;
-is used.
-In all cases, the selected address is either returned from
-&start; or passed in a connected message over the transport
-interface.
+The first element of a non-empty Host-IP-Address list in
+Svc provides the local IP address if an ip option is not
+specified.
+The local address is either returned from&start; or passed in a
+connected message over the transport interface.
--
cgit v1.2.3