We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 637 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

354 New Members signed up the last 30 days!

satisfaction-guaranteed

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!


Forum Replies

  1. Awesome post we’ve got here…

    But a couple of things that didn’t quite sync in my mind.

    First; When you mention that RIPv2 (224.0.0.9) and basically the range 224.0.0.0/24 is NOT routed between subnets, so my question is how RIPv2-aware routers advertise RIPv2 routes?

    Second; Can you give an example of a work with 239.0.0.0/8, cos I fear that if I applied it on a typical LAN (where I’m restricted to use only private IP addresses) that is connected to the Internet, it cause a conflict… Ain’t that right?

  2. Hi M. Bahwal,

    Multicast traffic in the 224.0.0.0/24 range is processed by routers but it won’t be “routed” to another subnet. Imagine a couple of routers connected to each other to a switch. They’ll use 224.0.0.9 to communicate with each on this segment. These routers won’t forward these multicast packets to other interfaces.

    What kind of multicast example are you looking for? There are many different configurations…

    Best Regards,

    Rene

  3. Abhishek,
    This is generally correct, with a couple of clarifications:

    1. When you say “224 range” specifically, that is 224.0.0.0/24 which is the range reserved for traffic on the local segment only. Any 224 network higher, say 224.0.1.0/24 has no special significance.

    2. The 239.0.0.0/8 is not really defined as user traffic vs router traffic. Its significance is that it is available for private organizational use. Think of this as being the same thing as 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16 for private IPv4 spaces.

  4. Hi Andrew ,
    A doubt on higher level …
    I was trying to understand connection between 239.0.0.0 AND 224.0.1.0 in MULTICAST concept.
    So any video server, once connects to router (so there must be some app that pump video traffic towards router) and router once configured “with respective config” , start sending traffic towards IP 239.1.1.1. And then hosts (typically equipped with an application such as VLC ) that are configured with “related host config” get this feed via that multicast router.

    1. So Is it always 239.1.1.1 or we can change this IP?
    2. where does 224.
    ... Continue reading in our forum

  5. Abhishek,

    1. The 239.0.0.0/8 range is entirely reserved for private, organization use. This means, the range from 239.0.0.0 - 239.255.255.255 can be used anyway you like–so long as the traffic stays within the bounds of a private address of a company. This means your video server could be configured to use any address between 239.0.0.1 and 239.255.255.254 if your goal to ensure you are using the “private” multicast range.

    2. For 224.0.1.0, I was just trying to make the point that when you originally said “224 range” that in order for your statement to be accura

    ... Continue reading in our forum

4 more replies! Ask a question or join the discussion by visiting our Community Forum