LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   DHCP Deactivated but requests for lease fill logs and eventually succeed (https://www.linuxquestions.org/questions/linux-networking-3/dhcp-deactivated-but-requests-for-lease-fill-logs-and-eventually-succeed-489876/)

FishFoot 10-05-2006 10:45 PM
DHCP Deactivated but requests for lease fill logs and eventually succeed
 
I have a new server running Ubuntu Dapper 6.06. I had the system connected to a LAN with a network address of 192.168.1.1/24 where it had a DHCP assigned IP address of 192.168.1.145.

I have a second network with the address 192.168.2.1/24. I moved the system onto this network but assigned it the static IP addressd 192.168.2.200 by modifying the /etc/network/interfaces file. It now reads:
Code:
# 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 eth0

#DHCP setup for 192.168.1.1/24
#iface eth0 inet dhcp

#Network 2 192.168.2.1/24
iface eth0 inet static
        address 192.168.2.200
        netmask 255.255.255.0
        network 192.168.2.0
        broadcast 192.168.2.255
        gateway 192.168.2.1
Everything was chugging along nicely until about 3pm today when the machine disappeared from the network. When I went looking for it I found it at 192.168.2.2, a DHCP assigned address.

This lead me into the /var/log/syslog where I found a continual stream of messages about DHCP:
Code:

Oct  5 06:25:33 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:27:18 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:27:38 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:27:46 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:27:59 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:28:42 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:31:25 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:32:12 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:32:26 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:33:48 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:34:28 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:34:49 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:35:00 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:35:15 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:38:54 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:39:07 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:40:41 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:43:06 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:45:29 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:46:16 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:46:28 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:48:25 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:49:09 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:51:30 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:51:47 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:52:47 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:52:58 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Oct  5 06:54:08 computer1 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
...
This obviously fails because there is no 192.168.1.1. Then strangly and seemingly randomly the requests start calling 255.255.255.255 and again, at a seemingly random point, it succeeds.
Code:
Oct  5 15:01:16 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:01:31 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:02:13 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:02:22 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:02:35 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:02:43 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:02:52 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:03:02 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:03:17 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:05:35 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:05:43 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:06:02 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:06:48 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:08:06 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:08:17 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:08:34 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:09:04 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:09:16 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:09:32 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:09:43 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:10:01 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:10:19 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:11:58 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:12:16 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:12:21 computer1 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Oct  5 15:12:23 computer1 dhclient: DHCPOFFER from 192.168.2.1
Oct  5 15:12:23 computer1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Oct  5 15:12:23 computer1 dhclient: DHCPACK from 192.168.2.1

I thought I had disabled DHCP in the /etc/network/interfaces but...

Does anybody know what gives?

Thanks
-FishFoot

ghost45 11-26-2006 10:34 AM
DHCP Deactivated but requests for lease fill logs and eventually succeed
 
Your Network address has the same (root) IP address as my Wireless Router
(192.168.2.1) which is my router's "Internet Access" with my ISP. My security software recently alerted me that my computer was being attacked and the attempt was blocked (from 192.168.2.1/67). I searched Google.com and your message/notes came up with this 'strange' coincidence. I would recommend you change your IP address(es) and port(s) addresses to avoid this conflict in the future.

elmr007 11-26-2006 10:11 PM
Crap!!what am I going to do!?! my LAN is on 192.168.2.1 lol just kidding :) Ghost45, Fishfoot's address has nothing to do with your problem. There are thousands of computers in the world with that address. port /67 is for dhcp, tcp, and udp protocals.

Fishfoot, on the machine that is running dhcp, you can edit the dhcp.conf file so that it always passes out the address 192.*.*.200 to the second linux box. Look in the Dhcp.conf file I believe it actually says something about printers "apearing at a static address" but it works for both. I use it so my wireless routers stay at a specific address (so i can find them).

elmr007 11-26-2006 10:18 PM
sorry that was /etc/dhcpd.conf not /etc/dhcp.conf


All times are GMT -5. The time now is 01:06 PM.