Skip to main content
Super User

Return to Answer

added 101 characters in body
Source Link
OtherDevOpsGene
OtherDevOpsGene
  • 2.3k
  • 1
  • 16
  • 7

I ran into the same thing in Ubuntu. Just because you edit the interface file to hardcode the IP doesn't stop the DHCP client from leasing a new IP.

sudo /etc/init.d/dhcp stop

Once you see that is working, you can remove the DHCP client for good so it doesn't come back:

sudo apt-get remove dhcp3-client

I ran into the same thing in Ubuntu. Just because you edit the interface file to hardcode the IP doesn't stop the DHCP client from leasing a new IP.

sudo /etc/init.d/dhcp stop
sudo apt-get remove dhcp3-client

I ran into the same thing in Ubuntu. Just because you edit the interface file to hardcode the IP doesn't stop the DHCP client from leasing a new IP.

sudo /etc/init.d/dhcp stop

Once you see that is working, you can remove the DHCP client for good so it doesn't come back:

sudo apt-get remove dhcp3-client
Source Link
OtherDevOpsGene
OtherDevOpsGene
  • 2.3k
  • 1
  • 16
  • 7

I ran into the same thing in Ubuntu. Just because you edit the interface file to hardcode the IP doesn't stop the DHCP client from leasing a new IP.

sudo /etc/init.d/dhcp stop
sudo apt-get remove dhcp3-client