Replacements for Linux Commands : Part 3
Do you like this story?
Click Here to go to Previous part : Part 2
Route
Deprecated route commands
|
Replacement |
---|---|
route . Displays the host’s routing tables. |
ip route |
route -A [family] [add] or route –[family] [add] . Uses the specified address family with add or del. Valid families are inet (DARPA Internet), inet6 (IPv6), ax25 (AMPR AX.25), netrom (AMPR NET/ROM), ipx (Novell IPX), ddp (Appletalk DDP), and x25 (CCITT X.25). |
ip -f [family] route . [family] can be inet (IP), inet6 (IPv6), or link. Additionally, -4 = -f inet and -6 = -f inet6. |
route -C or –cache . Operates on the kernel’s routing cache instead of the forwarding information base (FIB) routing table. |
Not apparent; ip route show cache dumps the routing cache. |
route -e or -ee . Uses the netstat-r format to display the routing table. -ee will generate a very long line with all parameters from the routing table. |
ip route show |
route -F or –fib . Operates on the kernel’s Forwarding Information Base (FIB) routing table (default behavior). |
Not apparent |
route -h or –help . Prints the help message. |
ip route help |
route -n . Shows numerical IP addresses and bypass host name resolution. |
Not apparent |
route -v or –verbose . Enables verbose command output. |
ip -s route |
route -V or –version . Dispays the version of net-tools and the route command. |
ip -V |
route add or del . Adds or delete a route in the routing table. |
ip route [add | chg | repl | del] [ip_addr] via [ip_addr] |
route [add or del] dev [interface] . Associates a route with a specific device. If dev [interface] is the last option on the command line, the word dev may be omitted. |
ip route [add | chg | repl | del] dev [interface] |
route [add or del] [default] gw [gw] . Routes packets through the specified gateway IP address. |
ip route add default via [gw] |
route [add or del] -host . Specifies that the target is a host (not a network). |
Not apparent |
route [add or del] -irtt [I] . Sets the initial round trip time (IRTT) for TCP connections over this route to [I] milliseconds (1-12000). This is typically only used on AX.25 networks. If omitted the RFC 1122 default of 300ms is used. |
Not apparent; ip route [add | chg | repl | del] rtt [number] sets the RTT estimate; rttvar [number] sets the initial RTT variance estimate. |
route [add or del] -net . Specifies that the target is a network (not a host). |
Not apparent |
route [add or del] [-host or -net] netmask [mask] . Sets the subnet [mask]. |
Not apparent |
route [add or del] metric [n] . Sets the metric field in the routing table (used by routing daemons) to the value of [n]. |
ip route [add | chg | repl | del] metric [number] or preference [number] |
route [add or del] mod, dyn, or reinstate . Install a dynamic or modified route. These flags are for diagnostic purposes, and are generally only set by routing daemons. |
Not apparent |
route [add or del] mss [bytes] . Sets the TCP Maximum Segment Size (MSS) for connections over this route to the number of [bytes] specified. |
ip route [add | chg | repl | del] advmss [number] (the MSS to advertise to these destinations when establishing TCP connections). |
route [add or del] reject . Installs a blocking route, which will force a route lookup to fail. This is used to mask out networks before using the default route. This is not intended to provide firewall functionality. |
ip route add prohibit [network_addr] |
route [add or del] window [W] . Set the TCP window size for connections over this route to the value of [W] bytes. This is typically only used on AX.25 networks and with drivers unable to handle back-to-back frames. |
ip route [add | chg | repl | del] window [W] |
Some examples of ip route command syntax are as follows.
# ip route add 10.23.30.0/24 via 192.168.8.50
# ip route del 10.28.0.0/16 via 192.168.10.50 dev eth0
# ip route chg default via 192.168.25.110 dev eth1
# ip route get [ip_address] (shows the interface and gateway that would be used to reach a remote host. This command would be especially useful for troubleshooting routing issues on hosts with large routing tables and/or with multiple network interfaces).
So here i guess the articles was understanble to you. Sorry for the formatting mistakes, Have fun.
Subscribe to:
Post Comments (Atom)
2 Responses to “Replacements for Linux Commands : Part 3”
January 12, 2012 at 2:15 AM
This is my first visit to your site. Today I have got a new site. I am really happy to be here. I am stay tuned here for your next blog...
January 18, 2012 at 12:21 PM
Great share of information.
Post a Comment