10 Useful “IP” Commands to Configure Network Interfaces

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.45/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Ravi Saive

I am Ravi Saive, creator of TecMint. A Computer Geek and Linux Guru who loves to share tricks and tips on Internet. Most Of My Servers runs on Open Source Platform called Linux. Follow Me: Twitter, Facebook and Google+

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

35 Responses

  1. Anuradha says:

    Very good article with simple steps

  2. xshadow yass says:

    thank you for tutorial that you & your team made they are so good
    please i have a problem i have already a public @ IP assigned to my dedicated server
    but i bought another failover @ip please how can i add it to my dedicated server
    so i can assign to it a domain name

    Best regards,

    PS: my interface file :
    # This file describes the network interfaces available on your system
    # and how to activate them. For more information, see interfaces(5).

    # The loopback network interface
    auto lo
    iface lo inet loopback

    # The primary network interface
    auto em1
    iface em1 inet dhcp

    Ubuntu 14.04.1

  3. DaveB says:

    In your instructions above, the first time you mention to restart the network services you have:

    # /etc/init.d/networking restart

    $ sudo /etc/init.d/networking restart

    This should be

    # /etc/init.d/network restart

    $ sudo /etc/init.d/network restart

    like you have near the end of the article.

  4. Pierre says:

    I noticed that these two commands behave differently:

    ip link set eth0 down
    ip link set dev eth0 down

    When dev is not used, the link state is brought down and stays down. Otherwise it will come up again soon after executing the command. The difference between the commands does not appear to be documented anywhere. Would you happen to know exactly what happens when running the commands and where the difference in behaviour stems from?

  5. Gene says:

    Hey Ravi!

    great article as always

    but quick question thou what’s the difference between ifup and ip link set ???

    • Ravi Saive says:

      Bro, ifup command is used to up network interface and ip command is used to assign IP address, Netmask, Gateway etc..

  6. prafulla nayak says:

    can we tweak keyboard keys at user level. we use Redhat 5.9 64 bit workstations. For example i want Num Lock as Tab & so on…..

    Thanks in advance

  7. Deepanjan says:

    Nice one…

    Okk if some one change my ip address ,subnet mask or try to play with it can i view the trail logs or anything simillar ????

  8. nik says:

    Superb article……

  9. Mandar says:

    Great article first of all !

    This command is very much similar to “IFCONFIG”.
    “sudo ifconfig eth1 up” replaced by “sudo ip link set eth1 up”.

    That’s really cool !

  10. manoj says:

    provide tips for gcov and lcov in linux

    • Ravi Saive says:

      Never heard about these tools, but we do try our best to provide you an how-to soon. Please stay updated..

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.