- struct sockaddr_in any;
- ::memset(&any, 0, sizeof(struct sockaddr_in));
- addrout.sin_family = AF_INET;
- addrout.sin_addr.s_addr = INADDR_ANY;
- addrout.sin_port = htons (base_port);
-
- if (::bind(sockout, (struct sockaddr *) (&any), sizeof(any)) < 0) {
- ::perror("bind");
- cout << "ipmidi bind error\n";
- return false;
- }
+ // Turn off loopback...
+ int loop = 0;
+
+#ifdef PLATFORM_WINDOWS
+
+ /* https://msdn.microsoft.com/en-us/library/windows/desktop/ms739161%28v=vs.85%29.aspx
+ *
+ * ------------------------------------------------------------------------------
+ * Note The Winsock version of the IP_MULTICAST_LOOP option is
+ * semantically different than the UNIX version of the
+ * IP_MULTICAST_LOOP option:
+ *
+ * In Winsock, the IP_MULTICAST_LOOP option applies only to the receive path.
+ * In the UNIX version, the IP_MULTICAST_LOOP option applies to the send path.
+ *
+ * For example, applications ON and OFF (which are easier to track than
+ * X and Y) join the same group on the same interface; application ON
+ * sets the IP_MULTICAST_LOOP option on, application OFF sets the
+ * IP_MULTICAST_LOOP option off. If ON and OFF are Winsock
+ * applications, OFF can send to ON, but ON cannot sent to OFF. In
+ * contrast, if ON and OFF are UNIX applications, ON can send to OFF,
+ * but OFF cannot send to ON.
+ * ------------------------------------------------------------------------------
+ *
+ * Alles klar? Gut!
+ */