Notable 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. 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.

  3. Awesome. clears the doubt now.

  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.0.1.0 range comes in to scene ?

    thanks.

  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 accurate, you need to make sure you are saying “224.0.0.0/24.” 224.0.1.0 was an example I gave of something that could be considered within the “224 range” but is NOT actually reserved for local segment multicast traffic. There is nothing special at all about 224.0.1.0

Continue the discussion forum.networklessons.com

4 more replies!

Participants