Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I have router 192.168.1.1 and machines connected through wire to it. I have also TP-Link connected with IP 192.168.1.2 and machines connected to it with IP 192.168.0.2 0.3 etc, some of them wireless some not. I still have problems with dhcp. When host is down internet will be lost and I have no IP or I get IP in subnet 192.168.1.1 (of router) or 169... I think I deleted all requests for IP 192.168.1.3 but as we can see in syslog my machine suddenly wants IP 192.168.1.3 instead of renewing old IP 192.168.0.2

May 4 00:40:09 myhost dhclient: DHCPREQUEST of 192.168.1.3 on eth0 to 192.168.1.1 port 67

May 4 01:07:53 myhost dhclient: DHCPREQUEST of 192.168.1.3 on eth0 to 192.168.1.1 port 67

May 4 01:09:05 dhclient: last message repeated 5 times
May 4 01:10:05 dhclient: last message repeated 3 times
May 4 01:11:05 dhclient: last message repeated 4 times
May 4 01:12:05 dhclient: last message repeated 4 times
May 4 01:13:06 dhclient: last message repeated 5 times

but it didn't get 192.168.1.3, this time I have still 192.168.0.2 however it writes to log new requests failed for 1.3. What can I do, what can I check, what can be the reason for this behavior?

result of grep is also unattractive:

root@myhost:/etc/mail# grep -R "192.168.1.3" /

grep: /tmp/ssh-EYovB4GIlDD8/agent.1894: No such device or address

grep: /tmp/.ICE-unix/1894: No such device or address

grep: /tmp/.X11-unix/X0: No such device or address

grep: /tmp/pulse-uG4wtwIe3W9m/native: No such device or address

grep: /tmp/.com.google.Chrome.gOVEEg/SingletonSocket: No such device or address

grep: /tmp/.com.google.Chrome.gOVEEg/SingletonCookie: No such file or directory

grep: /etc/dhcpc/resolv.conf: No such file or directory

grep: /etc/blkid.tab: No such file or directory

grep: /proc/sysrq-trigger: Input/output error

I have seen [here]

When dhclient, the DHCP client, is executed on the client machine, it begins broadcasting requests for configuration information. By default, these requests are on UDP port 68. The server replies on UDP 67

but my machine connects on port 67??? so it is treated as server? sorry, I can't get this clear.

moreover: /var/lib/dhcp/dhclient.leases is always empty. There are also two other files dhclient-66757614185someCRAZYNUMBER-eth0.lease and similar, one extremely old, the newer one is from yesterday and contains this:

lease {
  interface "eth0";
  fixed-address 192.168.0.02;
  option subnet-mask 255.255.255.0;
  option routers 192.168.0.1;
  option dhcp-lease-time 4294967295;
  option dhcp-message-type 5;
  option domain-name-servers 192.168.0.1;
  option dhcp-server-identifier 192.168.0.1;
  renew 4 1970/01/01 00:00:00;
  rebind 4 1996/04/25 19:17:01;
  expire 2 2013/04/30 14:05:39;
}
lease {
  interface "eth0";
  fixed-address 192.168.1.3;
  option subnet-mask 255.255.255.0;
  option routers 192.168.1.1;
  option dhcp-lease-time 86400;
  option dhcp-message-type 5;
  option domain-name-servers 192.168.1.1;
  option dhcp-server-identifier 192.168.1.1;
  option domain-name "cf16"; //"cf16" is what I put in Netgear router
  renew 5 2013/05/03 19:32:40;
  rebind 6 2013/05/04 07:01:18;
  expire 6 2013/05/04 10:01:18;
}

or is this maybe TP-Link issue? Maybe it forwards my machine's dhcp request to NetGear and it is why I am able to get 192.168.1.3? I can't understand how my machine can request this IP if DHCP server is TP-Link 192.168.0.1, and how I can work with IP 192.168.1.3 on network with mask 192.168.0.0?

share|improve this question
    
Stop the networkmanager. Delete all the lease files and then try –  thefourtheye May 4 '13 at 4:13
add comment

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.