cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
390
Views
2
Helpful
2
Replies

Multicast and IGPs

tidjes
Level 1
Level 1

Hi,

Most IGP (OSPF, EIGRP,..) we know rely on the hello packets to establish neiborships. Knowing that the hello packets are multicast packets, how do those routers establish neiborship when multicast routing protocols are disabled? Most routers have multicast routing disable by default but when we enable  an IGP on two routers, we still get neiborship even though multicast routing is disabled.

1 Accepted Solution

Accepted Solutions

M02@rt37
VIP
VIP

Hello @tidjes 

IGP protocols like OSPF and EIGRP use multicast addresses to send hello packets (and other control messages), but this does not require multicast routing to be enabled. This is because these protocols rely on link-local multicast, which operates within the same L2 broadcast domain and does not require the router to forward multicast packets between interfaces. Multicast routing, such as PIM, is only necessary for routing multicast traffic across subnets, not for processing or sending multicast traffic on a local interface. 

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

View solution in original post

2 Replies 2

M02@rt37
VIP
VIP

Hello @tidjes 

IGP protocols like OSPF and EIGRP use multicast addresses to send hello packets (and other control messages), but this does not require multicast routing to be enabled. This is because these protocols rely on link-local multicast, which operates within the same L2 broadcast domain and does not require the router to forward multicast packets between interfaces. Multicast routing, such as PIM, is only necessary for routing multicast traffic across subnets, not for processing or sending multicast traffic on a local interface. 

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

Joseph W. Doherty
Hall of Fame
Hall of Fame

Although M02@rt37 correctly describes why multicast routing isn't needed, I also wanted to mention multicast, operating within a L2:broadcast domain is much like broadcasts operating within the same L2 broadcast domain, which aren't routed either. However, hosts that "see" a multicast frame/packet can by examination of just the multicast address, can exclude multicast of no interest.

Also, keep in mind, again like broadcast, hosts can be in different unicast subnets, but as you can have multiple unicast subnets in the same L2 broadcast domain, routers might physically accept routing frames/packets from undesired unicast subnets which would be logically ignored.