Differences between version 5 and revision by previous author of SourceSpecificMulticastExample.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Tuesday, November 29, 2005 12:34:05 am | by PerryLorier | Revert |
| Older page: | version 3 | Last edited on Thursday, February 24, 2005 6:31:47 am | by AristotlePagaltzis | Revert |
@@ -1,9 +1,11 @@
-Here are some trivial examples of working [SSM] code. They certainly work under [LinuxKernel2.6], and have been tested on [amd64] in [Gentoo] and on [ia32] DebianLinux. It's possible that [SSM] is not supported in [Linux] 2.4. The examples join the [SSM] group ''ip-of-sender, 232.1.1.1''. In a real application you should randomly select the 232.../8 address to avoid conflicts (AddToMe: randomly per invocation, or once for each particular application?)
.
+Here are some trivial examples of working [SSM] code. They certainly work under [LinuxKernel2.6], and have been tested on [amd64] in [Gentoo] and on [ia32] DebianLinux. It's possible that [SSM] is not supported in [Linux] 2.4. The examples join the [SSM] group ''ip-of-sender, 232.1.1.1''. In a real application you should randomly select the 232.../8 address at runtime
to avoid conflicts.
Note that some information is included in <tt>#ifndef</tt>s since many LinuxDistribution~s don't install the required header files yet.
I had one major problem while trying to debug this. My mistake was that the reciever wasn't binding to <tt>INADDR_ANY</tt> for the listening socket, but instead to an [IP] address on the machine. This caused all the multicast packets to be ignored. Oops.
+
+Another bug was due to the server using the SSM source of the unassigned address. Oops.
Sender::
<verbatim>
