This topic is to discuss the following lesson:
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 (188.8.131.52) and basically the range 184.108.40.206/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 220.127.116.11/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?
Hi M. Bahwal,
Multicast traffic in the 18.104.22.168/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 22.214.171.124 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…
“The 126.96.36.199 – 188.8.131.52 range h…”
I think multicast address range is 184.108.40.206-220.127.116.11
The 18.104.22.168 - 22.214.171.124 is a “special” range that IANA has assigned for certain applications, these addresses are not routed outside of the subnet. For example, RIPv2, OSPF, EIGRP, etc.
for 224 range : One such example could be “ospf hello” which is not a user traffic but traffic among routers and does not require to be routed.
where-in for 239 range …it is a multicast user traffic . thats how IANA has separated both range for multicast…is that correct to say?
This is generally correct, with a couple of clarifications:
When you say “224 range” specifically, that is 126.96.36.199/24 which is the range reserved for traffic on the local segment only. Any 224 network higher, say 188.8.131.52/24 has no special significance.
The 184.108.40.206/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.
Awesome. clears the doubt now.
Hi Andrew ,
A doubt on higher level …
I was trying to understand connection between 220.127.116.11 AND 18.104.22.168 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 22.214.171.124. 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.
- So Is it always 126.96.36.199 or we can change this IP?
- where does 188.8.131.52 range comes in to scene ?
The 184.108.40.206/8 range is entirely reserved for private, organization use. This means, the range from 220.127.116.11 - 18.104.22.168 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 22.214.171.124 and 126.96.36.199 if your goal to ensure you are using the “private” multicast range.
For 188.8.131.52, 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 “184.108.40.206/24.” 220.127.116.11 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 18.104.22.168