Linux Routing Configuration: Difference between revisions
Jump to navigation
Jump to search
Line 46: | Line 46: | ||
TODO | TODO | ||
Route changes operated with ip are not saved. See [[ | Route changes operated with ip are not saved. See [[#Routing_Configuration_that_Survives_Reboot|Routing configuration that survives reboot]]. | ||
</font> | </font> | ||
Revision as of 17:30, 22 May 2017
External
Internal
Listing Routes
ip route
Adding a Static Route via a Specific Interface
TODO
Route changes operated with ip are not saved. See Routing configuration that survives reboot.
ip route add ...
Adding Multicast Routing to a Specific Network Interface
ip route add 224.0.0.0/4 dev <device-name>
More details about ip can be found here
The equivalent "route" command is:
route add 224.0.0.0 netmask 240.0.0.0 dev <device-name>
More information:
Deleting a Route
TODO
Route changes operated with ip are not saved. See Routing configuration that survives reboot.
ip route delete ...
Routing Configuration that Survives Reboot
Add the static routing configuration to /etc/sysconfig/network-scripts/route-<device-name>:
... # default multicast route 224.0.0.0/4 via 172.20.1.12
where "172.20.1.12" is the IP address of the interface we want to route the multicast traffic over. It is sufficient to add static routing configuration only to the file route-* corresponding to the interface that will service the route.
After reboot, we'll get this:
[eap@app01 ~]$ ip route ... 224.0.0.0/4 via 172.20.1.12 dev eth1