multicast_route
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| multicast_route [2017/10/18 15:57] – created walkeradmin | multicast_route [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Multicast Route ====== | ====== Multicast Route ====== | ||
| - | <color #db5f0b>Jan 2017 (Updated MApr 2017)</ | + | <color #db5f0b>Oct 2017</ |
| \\ | \\ | ||
| \\ | \\ | ||
| ---- | ---- | ||
| - | tcpdump | + | Multicast routes are a similar concept to IP Routes, but as the name implies they are for Multicast addresses (which are class D), rather than standard IP Addresses (which are class A, B and C). For Unicast I would surmise you still use IP Routes. |
| + | \\ | ||
| + | \\ | ||
| + | There are two main ways to add a Multicast Route. | ||
| + | \\ | ||
| + | 1. Create a routing file in (CentOS) / | ||
| + | 2. Add the route from the command line. | ||
| + | \\ | ||
| + | \\ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== 1. Create a routing file ===== | ||
| + | \\ | ||
| + | In this example, we will define that all multicast traffic in the range 239.X.Y.Z will be listened on the eth2 interface. | ||
| + | \\ | ||
| + | \\ | ||
| + | To do this, navigate to the location where all the interface configuration files are held. On CentOS this is / | ||
| + | \\ | ||
| + | cd / | ||
| + | \\ | ||
| + | Create a <color # | ||
| + | \\ | ||
| + | vi / | ||
| + | \\ | ||
| + | Note, the filename is the word " | ||
| + | \\ | ||
| + | \\ | ||
| + | Now add your routing parameters. | ||
| + | \\ | ||
| + | < | ||
| + | GATEWAY0=11.0.100.1 | ||
| + | NETMASK0=255.0.0.0 | ||
| + | ADDRESS0=239.0.0.0 | ||
| + | </ | ||
| + | \\ | ||
| + | The above routing information routes all traffic that has a multicast address of 239.x.x.x and a subnet of 255.0.0.0 to interface eth2 (as dictated by the name of the file " | ||
| + | \\ | ||
| + | \\ | ||
| + | This will route all multicast traffic requests on 239.X.Y.Z scope to interface Eth2, which has the IP address 11.0.100.1. The ' | ||
| + | \\ | ||
| + | \\ | ||
| + | Save and close the file. Restart networking or restart the server. | ||
| + | \\ | ||
| + | \\ | ||
| + | |||
| + | ---- | ||
| + | - | ||
| + | ===== 2. Add the route from the command line ===== | ||
| + | \\ | ||
| + | We can add the route from the command line, this does not create a file for us in the / | ||
| + | \\ | ||
| + | \\ | ||
| + | In this example we are going to add a multicast route 224.0.0.0/4 (/4 = 240.0.0.0) to an interface called eno33559296. 224.0.0.0/4 basically means everything from 239.0.0.0 to 224.255.255.255, | ||
| + | \\ | ||
| + | \\ | ||
| + | From the command line, enter the following: | ||
| + | \\ | ||
| + | ip route add 224.0.0.0/4 dev eno33559296 | ||
| + | \\ | ||
| + | You can check to see if the route has taken by using the following: | ||
| + | \\ | ||
| + | ip route | ||
| + | \\ | ||
| + | you will see a table of routes, with the new route added. | ||
| + | \\ | ||
| + | < | ||
| + | Destination | ||
| + | default | ||
| + | 10.0.0.0 | ||
| + | 10.0.3.0 | ||
| + | 10.43.0.0 | ||
| + | 224.0.0.0 | ||
| + | </ | ||
| + | \\ | ||
| + | The last line <color # | ||
| + | \\ | ||
| + | \\ | ||
| + | |||
multicast_route.1508338662.txt.gz · Last modified: 2023/03/09 22:35 (external edit)