OK, you confused me by talking about ‘private’ and ‘public’ addresses. That actually turns out to be irrelevant.
The real issue is that your server is multi-homed (i.e., has more than one IP address), and is currently choosing (for LIVE555) an address that you don’t want. The best way to fix this is to make sure that IP multicast routing is enabled on the network that you want the server to use (i.e., the ‘public’ network, in your case). In particular, you should make sure that this network (and not your ‘private’ network) has a route for 224.0.0.0/4 on your server machine. Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
