Why dhclient is still running when I choose static IP?Is there a safe way to disable DHCP from command line?How to add an IP alias on a bridged interface?Not able to connect to local networkConnecting Two Computers Together: Assigning IP doesnt workSetting Internet GatewayUbuntu server can access internet but cannot ping systems in the LANUnable to run 2 ethernet connections at the same timeConflict between two network interfaces eth0 and eth114.04 no internet connection when I up the bridge interface (for LXC container)Multiple network on the same cardReconfiguring the network interface on Ubuntu Server 16.04

How to explain that I do not want to visit a country due to personal safety concern?

Interplanetary conflict, some disease destroys the ability to understand or appreciate music

Opacity of an object in 2.8

A sequence that has integer values for prime indexes only:

How to use of "the" before known matrices

How to write cleanly even if my character uses expletive language?

Can I use USB data pins as power source

Instead of Universal Basic Income, why not Universal Basic NEEDS?

What approach do we need to follow for projects without a test environment?

Why one should not leave fingerprints on bulbs and plugs?

The difference between「N分で」and「後N分で」

How can I track script which gives me "command not found" right after the login?

Who is flying the vertibirds?

How to read the value of this capacitor?

Min function accepting varying number of arguments in C++17

Existence of subset with given Hausdorff dimension

Why doesn't the EU now just force the UK to choose between referendum and no-deal?

Is it normal that my co-workers at a fitness company criticize my food choices?

How could a scammer know the apps on my phone / iTunes account?

What do Xenomorphs eat in the Alien series?

Brexit - No Deal Rejection

My Graph Theory Students

how to write formula in word in latex

A limit with limit zero everywhere must be zero somewhere



Why dhclient is still running when I choose static IP?


Is there a safe way to disable DHCP from command line?How to add an IP alias on a bridged interface?Not able to connect to local networkConnecting Two Computers Together: Assigning IP doesnt workSetting Internet GatewayUbuntu server can access internet but cannot ping systems in the LANUnable to run 2 ethernet connections at the same timeConflict between two network interfaces eth0 and eth114.04 no internet connection when I up the bridge interface (for LXC container)Multiple network on the same cardReconfiguring the network interface on Ubuntu Server 16.04













13















I modify dhcp to static in /etc/network/interfaces (like below).



# The primary network interface
auto eth0
iface eth0 inet static
netmask 255.255.0.0
address 10.10.130.128
gateway 10.10.1.1


Then restart the interface.



$ sudo ifdown eth0; sudo ifup eth0
...
$ ifconfig
eth0 Link encap:Ethernet
inet addr:10.10.130.128 Bcast:10.10.255.255 Mask:255.255.0.0


So the new address kicks in.



But DHCP is still there?



$ ps aux | grep dhc
root ... dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -1 eth0


Is that normal? If not, how to restart interface in static IP while stop DHCP at the same time?



Thanks a lot.










share|improve this question

















  • 2





    Possible duplicate of Is there a safe way to disable DHCP from command line?

    – Videonauth
    Nov 15 '17 at 16:07















13















I modify dhcp to static in /etc/network/interfaces (like below).



# The primary network interface
auto eth0
iface eth0 inet static
netmask 255.255.0.0
address 10.10.130.128
gateway 10.10.1.1


Then restart the interface.



$ sudo ifdown eth0; sudo ifup eth0
...
$ ifconfig
eth0 Link encap:Ethernet
inet addr:10.10.130.128 Bcast:10.10.255.255 Mask:255.255.0.0


So the new address kicks in.



But DHCP is still there?



$ ps aux | grep dhc
root ... dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -1 eth0


Is that normal? If not, how to restart interface in static IP while stop DHCP at the same time?



Thanks a lot.










share|improve this question

















  • 2





    Possible duplicate of Is there a safe way to disable DHCP from command line?

    – Videonauth
    Nov 15 '17 at 16:07













13












13








13


6






I modify dhcp to static in /etc/network/interfaces (like below).



# The primary network interface
auto eth0
iface eth0 inet static
netmask 255.255.0.0
address 10.10.130.128
gateway 10.10.1.1


Then restart the interface.



$ sudo ifdown eth0; sudo ifup eth0
...
$ ifconfig
eth0 Link encap:Ethernet
inet addr:10.10.130.128 Bcast:10.10.255.255 Mask:255.255.0.0


So the new address kicks in.



But DHCP is still there?



$ ps aux | grep dhc
root ... dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -1 eth0


Is that normal? If not, how to restart interface in static IP while stop DHCP at the same time?



Thanks a lot.










share|improve this question














I modify dhcp to static in /etc/network/interfaces (like below).



# The primary network interface
auto eth0
iface eth0 inet static
netmask 255.255.0.0
address 10.10.130.128
gateway 10.10.1.1


Then restart the interface.



$ sudo ifdown eth0; sudo ifup eth0
...
$ ifconfig
eth0 Link encap:Ethernet
inet addr:10.10.130.128 Bcast:10.10.255.255 Mask:255.255.0.0


So the new address kicks in.



But DHCP is still there?



$ ps aux | grep dhc
root ... dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -1 eth0


Is that normal? If not, how to restart interface in static IP while stop DHCP at the same time?



Thanks a lot.







networking dhcp






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 1 '14 at 20:09









user276851user276851

2872515




2872515







  • 2





    Possible duplicate of Is there a safe way to disable DHCP from command line?

    – Videonauth
    Nov 15 '17 at 16:07












  • 2





    Possible duplicate of Is there a safe way to disable DHCP from command line?

    – Videonauth
    Nov 15 '17 at 16:07







2




2





Possible duplicate of Is there a safe way to disable DHCP from command line?

– Videonauth
Nov 15 '17 at 16:07





Possible duplicate of Is there a safe way to disable DHCP from command line?

– Videonauth
Nov 15 '17 at 16:07










3 Answers
3






active

oldest

votes


















21














  1. You first have to shutdown the interface (in dhcp mode) sudo ifdown eth0


  2. Then edit the config nano /etc/network/interfaces



    # The primary network interface
    auto eth0
    iface eth0 inet static
    netmask 255.255.0.0
    address 10.10.130.128
    gateway 10.10.1.1


  3. Bring the interface back up sudo ifup eth0


Otherwise dhclient doesn't correctly shuts down,






share|improve this answer

























  • Sorry, but can someone elaborate on exactly how this differs from what is done in the OP here? I've read this three times and I can't seem to tell the difference.

    – fostandy
    Aug 16 '14 at 10:37











  • Is it about modifying ('touch') the file so the date changes? Am I supposed to only edit the file AFTER I've brought down the interface? If so, how can I 'undo' the fact that I've edited it before?

    – fostandy
    Aug 16 '14 at 10:43






  • 1





    @fostandy "ifupdown doesn't support the modifying of interface definitions in /etc/network/interfaces while the related interfaces are up". Here, the interface is stopped before the file is modified.

    – Bruno
    Nov 15 '14 at 0:14







  • 1





    @Bruno - thanks for clarifying. Out of curiousity what do you do if you've already irrevocably edited the /etc/network/interfaces file? Is there a way to force a reset to defaults and and start again?

    – fostandy
    Dec 1 '14 at 8:22






  • 7





    I was baffled as to why it should make a difference but then a clever friend of mine explained it very nicely. The problem is if the file is edited and then ifdown is run, network manager does not know that it needs to stop dhclient, since all it sees in the interfaces file is a static entry. After, the interface is down, issuing ifup correctly reads and applies the static settings, but it also doesn't know that dhclient had been started.

    – paracycle
    Oct 23 '15 at 18:48


















2














I had the same issue (Ubuntu 16.04). However, this was a cloud instance and I could not ifdown the interface that easily.



Short answer: I removed the file /etc/network/interfaces.d/50-cloud-init.cfg ifup was triggered by that specific file.



Long answer:
I configured the interface using the /etc/network/interfaces with a static IP address, but I still found in the daemon.log that dhclient was still requesting IP's from the DHCP and dhclient was started through systemd.
Specifically, systemd called the networking.service unit, which called ifup, which read both the interfaces file and the 50-cloud-init.cfg file. Resulting in some conflicts, but still a functional network.






share|improve this answer

























  • I had the exact same issue, and learned the hard way, that a later file (like 99-eth0.cfg) was indeed NOT overriding previous statements! So, thanks for your input ;)

    – Daywalker
    Mar 20 '18 at 18:17


















1














I found for me, this was due to gnome's NetworkManager still running and thinking it was in charge of the device. In hindsight this should have been obvious as ps showed dhclient was being launched by NetworkManager.



Once I restarted my system the device went to "unmanaged" in NetworkManager and it stopped trying to configure it. Perhaps I could have achieved the same thing just by stopping/restarting NetworkManager, I'm not sure.






share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f459140%2fwhy-dhclient-is-still-running-when-i-choose-static-ip%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    21














    1. You first have to shutdown the interface (in dhcp mode) sudo ifdown eth0


    2. Then edit the config nano /etc/network/interfaces



      # The primary network interface
      auto eth0
      iface eth0 inet static
      netmask 255.255.0.0
      address 10.10.130.128
      gateway 10.10.1.1


    3. Bring the interface back up sudo ifup eth0


    Otherwise dhclient doesn't correctly shuts down,






    share|improve this answer

























    • Sorry, but can someone elaborate on exactly how this differs from what is done in the OP here? I've read this three times and I can't seem to tell the difference.

      – fostandy
      Aug 16 '14 at 10:37











    • Is it about modifying ('touch') the file so the date changes? Am I supposed to only edit the file AFTER I've brought down the interface? If so, how can I 'undo' the fact that I've edited it before?

      – fostandy
      Aug 16 '14 at 10:43






    • 1





      @fostandy "ifupdown doesn't support the modifying of interface definitions in /etc/network/interfaces while the related interfaces are up". Here, the interface is stopped before the file is modified.

      – Bruno
      Nov 15 '14 at 0:14







    • 1





      @Bruno - thanks for clarifying. Out of curiousity what do you do if you've already irrevocably edited the /etc/network/interfaces file? Is there a way to force a reset to defaults and and start again?

      – fostandy
      Dec 1 '14 at 8:22






    • 7





      I was baffled as to why it should make a difference but then a clever friend of mine explained it very nicely. The problem is if the file is edited and then ifdown is run, network manager does not know that it needs to stop dhclient, since all it sees in the interfaces file is a static entry. After, the interface is down, issuing ifup correctly reads and applies the static settings, but it also doesn't know that dhclient had been started.

      – paracycle
      Oct 23 '15 at 18:48















    21














    1. You first have to shutdown the interface (in dhcp mode) sudo ifdown eth0


    2. Then edit the config nano /etc/network/interfaces



      # The primary network interface
      auto eth0
      iface eth0 inet static
      netmask 255.255.0.0
      address 10.10.130.128
      gateway 10.10.1.1


    3. Bring the interface back up sudo ifup eth0


    Otherwise dhclient doesn't correctly shuts down,






    share|improve this answer

























    • Sorry, but can someone elaborate on exactly how this differs from what is done in the OP here? I've read this three times and I can't seem to tell the difference.

      – fostandy
      Aug 16 '14 at 10:37











    • Is it about modifying ('touch') the file so the date changes? Am I supposed to only edit the file AFTER I've brought down the interface? If so, how can I 'undo' the fact that I've edited it before?

      – fostandy
      Aug 16 '14 at 10:43






    • 1





      @fostandy "ifupdown doesn't support the modifying of interface definitions in /etc/network/interfaces while the related interfaces are up". Here, the interface is stopped before the file is modified.

      – Bruno
      Nov 15 '14 at 0:14







    • 1





      @Bruno - thanks for clarifying. Out of curiousity what do you do if you've already irrevocably edited the /etc/network/interfaces file? Is there a way to force a reset to defaults and and start again?

      – fostandy
      Dec 1 '14 at 8:22






    • 7





      I was baffled as to why it should make a difference but then a clever friend of mine explained it very nicely. The problem is if the file is edited and then ifdown is run, network manager does not know that it needs to stop dhclient, since all it sees in the interfaces file is a static entry. After, the interface is down, issuing ifup correctly reads and applies the static settings, but it also doesn't know that dhclient had been started.

      – paracycle
      Oct 23 '15 at 18:48













    21












    21








    21







    1. You first have to shutdown the interface (in dhcp mode) sudo ifdown eth0


    2. Then edit the config nano /etc/network/interfaces



      # The primary network interface
      auto eth0
      iface eth0 inet static
      netmask 255.255.0.0
      address 10.10.130.128
      gateway 10.10.1.1


    3. Bring the interface back up sudo ifup eth0


    Otherwise dhclient doesn't correctly shuts down,






    share|improve this answer















    1. You first have to shutdown the interface (in dhcp mode) sudo ifdown eth0


    2. Then edit the config nano /etc/network/interfaces



      # The primary network interface
      auto eth0
      iface eth0 inet static
      netmask 255.255.0.0
      address 10.10.130.128
      gateway 10.10.1.1


    3. Bring the interface back up sudo ifup eth0


    Otherwise dhclient doesn't correctly shuts down,







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited May 1 '14 at 21:27

























    answered May 1 '14 at 20:24









    pvcpvc

    32625




    32625












    • Sorry, but can someone elaborate on exactly how this differs from what is done in the OP here? I've read this three times and I can't seem to tell the difference.

      – fostandy
      Aug 16 '14 at 10:37











    • Is it about modifying ('touch') the file so the date changes? Am I supposed to only edit the file AFTER I've brought down the interface? If so, how can I 'undo' the fact that I've edited it before?

      – fostandy
      Aug 16 '14 at 10:43






    • 1





      @fostandy "ifupdown doesn't support the modifying of interface definitions in /etc/network/interfaces while the related interfaces are up". Here, the interface is stopped before the file is modified.

      – Bruno
      Nov 15 '14 at 0:14







    • 1





      @Bruno - thanks for clarifying. Out of curiousity what do you do if you've already irrevocably edited the /etc/network/interfaces file? Is there a way to force a reset to defaults and and start again?

      – fostandy
      Dec 1 '14 at 8:22






    • 7





      I was baffled as to why it should make a difference but then a clever friend of mine explained it very nicely. The problem is if the file is edited and then ifdown is run, network manager does not know that it needs to stop dhclient, since all it sees in the interfaces file is a static entry. After, the interface is down, issuing ifup correctly reads and applies the static settings, but it also doesn't know that dhclient had been started.

      – paracycle
      Oct 23 '15 at 18:48

















    • Sorry, but can someone elaborate on exactly how this differs from what is done in the OP here? I've read this three times and I can't seem to tell the difference.

      – fostandy
      Aug 16 '14 at 10:37











    • Is it about modifying ('touch') the file so the date changes? Am I supposed to only edit the file AFTER I've brought down the interface? If so, how can I 'undo' the fact that I've edited it before?

      – fostandy
      Aug 16 '14 at 10:43






    • 1





      @fostandy "ifupdown doesn't support the modifying of interface definitions in /etc/network/interfaces while the related interfaces are up". Here, the interface is stopped before the file is modified.

      – Bruno
      Nov 15 '14 at 0:14







    • 1





      @Bruno - thanks for clarifying. Out of curiousity what do you do if you've already irrevocably edited the /etc/network/interfaces file? Is there a way to force a reset to defaults and and start again?

      – fostandy
      Dec 1 '14 at 8:22






    • 7





      I was baffled as to why it should make a difference but then a clever friend of mine explained it very nicely. The problem is if the file is edited and then ifdown is run, network manager does not know that it needs to stop dhclient, since all it sees in the interfaces file is a static entry. After, the interface is down, issuing ifup correctly reads and applies the static settings, but it also doesn't know that dhclient had been started.

      – paracycle
      Oct 23 '15 at 18:48
















    Sorry, but can someone elaborate on exactly how this differs from what is done in the OP here? I've read this three times and I can't seem to tell the difference.

    – fostandy
    Aug 16 '14 at 10:37





    Sorry, but can someone elaborate on exactly how this differs from what is done in the OP here? I've read this three times and I can't seem to tell the difference.

    – fostandy
    Aug 16 '14 at 10:37













    Is it about modifying ('touch') the file so the date changes? Am I supposed to only edit the file AFTER I've brought down the interface? If so, how can I 'undo' the fact that I've edited it before?

    – fostandy
    Aug 16 '14 at 10:43





    Is it about modifying ('touch') the file so the date changes? Am I supposed to only edit the file AFTER I've brought down the interface? If so, how can I 'undo' the fact that I've edited it before?

    – fostandy
    Aug 16 '14 at 10:43




    1




    1





    @fostandy "ifupdown doesn't support the modifying of interface definitions in /etc/network/interfaces while the related interfaces are up". Here, the interface is stopped before the file is modified.

    – Bruno
    Nov 15 '14 at 0:14






    @fostandy "ifupdown doesn't support the modifying of interface definitions in /etc/network/interfaces while the related interfaces are up". Here, the interface is stopped before the file is modified.

    – Bruno
    Nov 15 '14 at 0:14





    1




    1





    @Bruno - thanks for clarifying. Out of curiousity what do you do if you've already irrevocably edited the /etc/network/interfaces file? Is there a way to force a reset to defaults and and start again?

    – fostandy
    Dec 1 '14 at 8:22





    @Bruno - thanks for clarifying. Out of curiousity what do you do if you've already irrevocably edited the /etc/network/interfaces file? Is there a way to force a reset to defaults and and start again?

    – fostandy
    Dec 1 '14 at 8:22




    7




    7





    I was baffled as to why it should make a difference but then a clever friend of mine explained it very nicely. The problem is if the file is edited and then ifdown is run, network manager does not know that it needs to stop dhclient, since all it sees in the interfaces file is a static entry. After, the interface is down, issuing ifup correctly reads and applies the static settings, but it also doesn't know that dhclient had been started.

    – paracycle
    Oct 23 '15 at 18:48





    I was baffled as to why it should make a difference but then a clever friend of mine explained it very nicely. The problem is if the file is edited and then ifdown is run, network manager does not know that it needs to stop dhclient, since all it sees in the interfaces file is a static entry. After, the interface is down, issuing ifup correctly reads and applies the static settings, but it also doesn't know that dhclient had been started.

    – paracycle
    Oct 23 '15 at 18:48













    2














    I had the same issue (Ubuntu 16.04). However, this was a cloud instance and I could not ifdown the interface that easily.



    Short answer: I removed the file /etc/network/interfaces.d/50-cloud-init.cfg ifup was triggered by that specific file.



    Long answer:
    I configured the interface using the /etc/network/interfaces with a static IP address, but I still found in the daemon.log that dhclient was still requesting IP's from the DHCP and dhclient was started through systemd.
    Specifically, systemd called the networking.service unit, which called ifup, which read both the interfaces file and the 50-cloud-init.cfg file. Resulting in some conflicts, but still a functional network.






    share|improve this answer

























    • I had the exact same issue, and learned the hard way, that a later file (like 99-eth0.cfg) was indeed NOT overriding previous statements! So, thanks for your input ;)

      – Daywalker
      Mar 20 '18 at 18:17















    2














    I had the same issue (Ubuntu 16.04). However, this was a cloud instance and I could not ifdown the interface that easily.



    Short answer: I removed the file /etc/network/interfaces.d/50-cloud-init.cfg ifup was triggered by that specific file.



    Long answer:
    I configured the interface using the /etc/network/interfaces with a static IP address, but I still found in the daemon.log that dhclient was still requesting IP's from the DHCP and dhclient was started through systemd.
    Specifically, systemd called the networking.service unit, which called ifup, which read both the interfaces file and the 50-cloud-init.cfg file. Resulting in some conflicts, but still a functional network.






    share|improve this answer

























    • I had the exact same issue, and learned the hard way, that a later file (like 99-eth0.cfg) was indeed NOT overriding previous statements! So, thanks for your input ;)

      – Daywalker
      Mar 20 '18 at 18:17













    2












    2








    2







    I had the same issue (Ubuntu 16.04). However, this was a cloud instance and I could not ifdown the interface that easily.



    Short answer: I removed the file /etc/network/interfaces.d/50-cloud-init.cfg ifup was triggered by that specific file.



    Long answer:
    I configured the interface using the /etc/network/interfaces with a static IP address, but I still found in the daemon.log that dhclient was still requesting IP's from the DHCP and dhclient was started through systemd.
    Specifically, systemd called the networking.service unit, which called ifup, which read both the interfaces file and the 50-cloud-init.cfg file. Resulting in some conflicts, but still a functional network.






    share|improve this answer















    I had the same issue (Ubuntu 16.04). However, this was a cloud instance and I could not ifdown the interface that easily.



    Short answer: I removed the file /etc/network/interfaces.d/50-cloud-init.cfg ifup was triggered by that specific file.



    Long answer:
    I configured the interface using the /etc/network/interfaces with a static IP address, but I still found in the daemon.log that dhclient was still requesting IP's from the DHCP and dhclient was started through systemd.
    Specifically, systemd called the networking.service unit, which called ifup, which read both the interfaces file and the 50-cloud-init.cfg file. Resulting in some conflicts, but still a functional network.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 6 mins ago









    Kevin Bowen

    14.6k155970




    14.6k155970










    answered Apr 20 '17 at 17:36









    Patrick DeelmanPatrick Deelman

    211




    211












    • I had the exact same issue, and learned the hard way, that a later file (like 99-eth0.cfg) was indeed NOT overriding previous statements! So, thanks for your input ;)

      – Daywalker
      Mar 20 '18 at 18:17

















    • I had the exact same issue, and learned the hard way, that a later file (like 99-eth0.cfg) was indeed NOT overriding previous statements! So, thanks for your input ;)

      – Daywalker
      Mar 20 '18 at 18:17
















    I had the exact same issue, and learned the hard way, that a later file (like 99-eth0.cfg) was indeed NOT overriding previous statements! So, thanks for your input ;)

    – Daywalker
    Mar 20 '18 at 18:17





    I had the exact same issue, and learned the hard way, that a later file (like 99-eth0.cfg) was indeed NOT overriding previous statements! So, thanks for your input ;)

    – Daywalker
    Mar 20 '18 at 18:17











    1














    I found for me, this was due to gnome's NetworkManager still running and thinking it was in charge of the device. In hindsight this should have been obvious as ps showed dhclient was being launched by NetworkManager.



    Once I restarted my system the device went to "unmanaged" in NetworkManager and it stopped trying to configure it. Perhaps I could have achieved the same thing just by stopping/restarting NetworkManager, I'm not sure.






    share|improve this answer



























      1














      I found for me, this was due to gnome's NetworkManager still running and thinking it was in charge of the device. In hindsight this should have been obvious as ps showed dhclient was being launched by NetworkManager.



      Once I restarted my system the device went to "unmanaged" in NetworkManager and it stopped trying to configure it. Perhaps I could have achieved the same thing just by stopping/restarting NetworkManager, I'm not sure.






      share|improve this answer

























        1












        1








        1







        I found for me, this was due to gnome's NetworkManager still running and thinking it was in charge of the device. In hindsight this should have been obvious as ps showed dhclient was being launched by NetworkManager.



        Once I restarted my system the device went to "unmanaged" in NetworkManager and it stopped trying to configure it. Perhaps I could have achieved the same thing just by stopping/restarting NetworkManager, I'm not sure.






        share|improve this answer













        I found for me, this was due to gnome's NetworkManager still running and thinking it was in charge of the device. In hindsight this should have been obvious as ps showed dhclient was being launched by NetworkManager.



        Once I restarted my system the device went to "unmanaged" in NetworkManager and it stopped trying to configure it. Perhaps I could have achieved the same thing just by stopping/restarting NetworkManager, I'm not sure.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 19 '14 at 2:54









        fostandyfostandy

        1111




        1111



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f459140%2fwhy-dhclient-is-still-running-when-i-choose-static-ip%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

            Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

            Torre de la Isleta Índice Véase también Referencias Bibliografía Enlaces externos Menú de navegación38°25′58″N 0°23′02″O / 38.43277778, -0.3838888938°25′58″N 0°23′02″O / 38.43277778, -0.38388889Torre de la Illeta de l’Horta o Torre Saleta. Base de datos de bienes inmuebles. Patrimonio Cultural. Secretaría de Estado de CulturaFicha BIC Torre de la Illeta de l’Horta. Dirección General de Patrimonio Cultural. Generalitat ValencianaLugares de interés. Ayuntamiento del CampelloTorre de la Isleta en CastillosNet.org