> Multicast by nature will "flood" to every port on a LAN/WAN, till the
> TTL reaches 0 or until it reaches a multicast aware router that will
> route the traffic or drop it.
The information above is not quite correct.
Multicast packets will flood all hosts within a LAN unless the
infrastructure is both multicast aware (supports one of IGMP snooping, GMRP,
CGMP or has static Mac filters) and is properly configured, then in theory
multicast packets will only reach interested hosts, multicast router
interfaces and other ports configured by admin to receive all multicast
traffic. Multicast will chew wireless capacity and affect all wireless
hosts.
Multicast packets will not leave your LAN unless you have a multicast
router and there is forwarding state in the multicast routing table for the
groups concerned. ie packets will not reach the WAN or other routed LANs.
If there is forwarding state in the network the packet will be forwarded hop
by hop decrementing the ttl until they reach a receiver or the ttl reaches
0.
> If you are not wishing to flood your
> stream to your ISP you can set the TTL of your stream in the broadcast
> program to 1.
If you have a routed network, traffic should not reach your ISP unless you
have a correctly configured multicast router. You probably don't. However a
home gateway may be acting as a bridge that's a different story.
Here's a very good place to find out if you have multicast connectivity to
the outside world.
http://www.multicasttech.com/mt/http://www.multicast-isp-list.com/
A.
ftp://ftp.rfc-editor.org/in-notes/rfc1112.txt
_______________________________________________
streaming-server-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/streaming-server-users
Do not post admin requests to the list. They will be ignored.
