Bugzilla – Bug 11518
A couple of fab4 PB2 units refuse to get dhcp most of the time
Last modified: 2012-02-27 17:33:01 UTC
Created attachment 4983 [details] Set of fab4 and wireshark logs I have two PB2 fab4 units that have issues getting dhcp most of the time. This is with wifi or ethernet. The thing is if a try enough times it will eventually work. I have only seen this issue with these two units out of about 40 or so I have worked with. The macs of the units that fail are 22:01:24 and 22:00:A7. I also made logs of a unit that works and its mac is 22:01:28 To reproduce all I do is walk through setup with either ethernet or wifi and after attempting to connect to the network it will fail with a "DHCP Address Can't Be Found" error. 1 thing I have noticed in the log is if the messages coming from fab4 when first powered up are asking "Who has 169.254.144.43" it will fail. If it is looking for a different address it will be successful. Not sure why it would be looking for a self assigned ip after a factory reset?
That "who has 169..." arp request is a normal part of the autoip functionality. Felix: this should be addressed as part of your new busybox work, i suspect.
Steven, please retest with > r5011. This has a new version of busybox (eg new DHCP) code in.
Steven can this be closed now?
Tested these units with r5022 and they got on the network without issue both over wifi and ethernet. Went back to r4875 and the issue came back. Looks like the new busybox did the trick! I will hold onto these units to test against busybox changes in the future.
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.