3 files changed, 15 insertions, 0 deletions
diff --git a/man/man7/zmq_pgm.7 b/man/man7/zmq_pgm.7
index e432730..68af978 100644
--- a/man/man7/zmq_pgm.7
+++ b/man/man7/zmq_pgm.7
@@ -32,6 +32,11 @@ mutlicast group should be specified in the numeric representation. For example:
     pgm://192.168.0.111:224.0.0.1:5555
 .fi
 
+Note that NIC names are not standardised by POSIX. They tend to be rather
+arbitrary and platform dependent. Say, "eth0" on Linux would correspond to "en0"
+on OSX and "e1000g" on Solaris. On Windows platform, as there are no short NIC
+names available, you have to use numeric IP addresses instead.
+
 .SH WIRE FORMAT
 
 Consecutive PGM packets are interpreted as a single continuous stream of data.
diff --git a/man/man7/zmq_tcp.7 b/man/man7/zmq_tcp.7
index aa3f56e..f5504c8 100644
--- a/man/man7/zmq_tcp.7
+++ b/man/man7/zmq_tcp.7
@@ -18,6 +18,11 @@ a NIC name or a hostname (resolved by DNS):
     tcp://lo:32768
 .fi
 
+Note that NIC names are not standardised by POSIX. They tend to be rather
+arbitrary and platform dependent. Say, "eth0" on Linux would correspond to "en0"
+on OSX and "e1000g" on Solaris. On Windows platform, as there are no short NIC
+names available, you have to use numeric IP addresses instead.
+
 .SH WIRE FORMAT
 
 A message consists of a message length followed by message data.
diff --git a/man/man7/zmq_udp.7 b/man/man7/zmq_udp.7
index bfebc1c..151a6d4 100644
--- a/man/man7/zmq_udp.7
+++ b/man/man7/zmq_udp.7
@@ -24,6 +24,11 @@ mutlicast group should be specified in the numeric representation. For example:
     udp://192.168.0.111:224.0.0.1:5555
 .fi
 
+Note that NIC names are not standardised by POSIX. They tend to be rather
+arbitrary and platform dependent. Say, "eth0" on Linux would correspond to "en0"
+on OSX and "e1000g" on Solaris. On Windows platform, as there are no short NIC
+names available, you have to use numeric IP addresses instead.
+
 .SH WIRE FORMAT
 
 Same as with PGM transport except for UDP packet headers.