Android Devices (4.4 or newer it seems) get wrong address and disconnect

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Pair any android device with router
2.wait
3.The phone/tablet will stay connected but no date will be transferred 

What is the expected output? What do you see instead?
DHCPNAK(br0) 192.168.137.245 xx:xx:xx:xx:xx:xx wrong network

What version of the product are you using? On what operating system?
3.0.3.7-079 RT-n56u; Android

Please describe the problem as detailed as it's possible.
If you have connection problem, then syslog file is required. (please do
attach it as a file)
Note that if there will be a poor problem description the issue status will
be changed to 'Invalid'!

Original issue reported on code.google.com by lifehack...@gmail.com on 13 Mar 2014 at 1:02

[GoogleCodeExporter]

https://docs.google.com/file/d/0B0oFVQPGy6B7UGpDaXB0ckRVV2M/edit?pli=1

Original comment by lifehack...@gmail.com on 13 Mar 2014 at 1:04

[GoogleCodeExporter]

Same issue is here as well.

Original comment by vhal...@gmail.com on 13 Mar 2014 at 8:44

[GoogleCodeExporter]

I am using several android devices, running both samsung 4.0.x but also 3 
handsets running my own cyanogenmod (4.0 - 4.4).

I do not face this issue.

There is, however, a common issue among certain android-devices which requires 
you to set the IP of the device manually before you connect via wifi. That is 
an issue within the andoid os.

Original comment by kitch2400 on 14 Mar 2014 at 7:00

[GoogleCodeExporter]

You can prob. verify this yourself in the log-file. You should see something 
like a request for 192.xxx.xxx.xxx <- Outside your range.

DHCPNAK(br0) 192.168.137.245 <- NAK = denied. This is the ipv4-address your 
device specifically asked for.

/Kitch

Original comment by kitch2400 on 14 Mar 2014 at 8:57

[GoogleCodeExporter]

http://www.stanford.edu/services/lnaguide/dhcp-log-explanation.html

Original comment by kitch2400 on 14 Mar 2014 at 8:58

[GoogleCodeExporter]

Yup, no problem here as well (Galaxy S4 on 4.4, probably a leak, but worked 
fine with 4.3 and 4.2). Install a custom ROM and it will probably go away.

Original comment by moonman...@gmail.com on 15 Mar 2014 at 8:21

[GoogleCodeExporter]

No issues here.. I have 3 Android devices all running KitKat (4.4.2) connected 
without any issue.. I did however assign IP addresses to each of them from the 
Router itself..

Original comment by Arijit.R...@gmail.com on 19 Mar 2014 at 5:26

[GoogleCodeExporter]

I have tried that and the error persists. The work around i though would work 
was manually assigning an ip from the phone and at the same time setting up a 
static ip from the router to the phone. Although sometimes it hangs (i dont 
know why) I is usually able to re-establish a connection rather quick.

Original comment by lifehack...@gmail.com on 19 Mar 2014 at 6:28