multicast_route
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
multicast_route [2017/10/18 16:17] – [1. Create a routing file] walkeradmin | multicast_route [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 17: | Line 17: | ||
---- | ---- | ||
- | ==== 1. Create a routing file ==== | + | ===== 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. | In this example, we will define that all multicast traffic in the range 239.X.Y.Z will be listened on the eth2 interface. | ||
Line 52: | Line 52: | ||
---- | ---- | ||
- | ==== Add the route from the command line ==== | + | - |
+ | ===== 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.1508339876.txt.gz · Last modified: 2023/03/09 22:35 (external edit)