Find Your Device:
Or Continue to Thread: no route by dhcp - flock dhcpc…
6th March 2014, 10:42 AM |#1  
41.kretschi's Avatar
OP Member
Thanks Meter: 10
Hi guys,
I have a problem with my wifi connection:
it's connecting and receiving the ip address by dhcp but no route is beeing set. It happens with different routers and wifi networks, so its not a router problem. also with my notebook I can connect to it regularly and everything works fine.
On my phone I have to set the route by hand afterwards - it's the only fix I found so far.
I do it by redoing the dhcp process and I have to do it twice. I don't really understand the problem dhcpcd has the first time but maybe that's the problem why no route is being set in the first place.

root@serranolte:/ # dhcpcd wlan0
dhcpcd[12685]: flock `/data/misc/dhcp/': Try again
1|root@serranolte:/ # dhcpcd wlan0
dhcpcd[12706]: version 5.5.6 starting
dhcpcd[12706]: wlan0: rebinding lease of
dhcpcd[12706]: wlan0: NAK: requested address not available from
dhcpcd[12706]: wlan0: broadcasting for a lease
dhcpcd[12706]: wlan0: offered from
dhcpcd[12706]: wlan0: acknowledged from[12706]: wlan0: checking for
dhcpcd[12706]: wlan0: leased for 14400 seconds
dhcpcd[12706]: forked to background, child pid 12749
root@serranolte:/ #
I also took a look at the dhcpcd.conf and the hooks files. the properties are not being set. is this an issue? maybe you guys know how to fix this.

root@serranolte:/ # getprop | grep dhcp
[dhcp.wlan0.dns1]: []
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[dhcp.wlan0.domain]: []
[dhcp.wlan0.gateway]: []
[dhcp.wlan0.ipaddress]: []
[dhcp.wlan0.leasetime]: []
[dhcp.wlan0.mask]: []
[dhcp.wlan0.mtu]: []
[]: [30155]
[dhcp.wlan0.reason]: [BOUND]
[dhcp.wlan0.result]: [ok]
[dhcp.wlan0.server]: []
[dhcp.wlan0.vendorInfo]: []
[init.svc.dhcpcd_wlan0]: [running]
root@serranolte:/ #
I don't know if this is an CM issue? I didn't have problems with other devices running CM connecting to the same AP at the same location.
I already read a lot about similar problems at other phones but nobody ever had a fix for it.
Is it a radio problem or maybe a kernel issue?

I hope this is the right forum for it.

I'm running the latest CM11 nightly on a Samsung Galaxy S4 mini LTE (GT-I9195)
The problem also occurred with the stable builds of cm10.2 and cm10.1

any help will be appreciated

Thanks and cheers 41

Gesendet von meinem GT-I9195 mit Tapatalk
Last edited by 41.kretschi; 6th March 2014 at 12:39 PM.