I used a prebuilt tarball from Yocto to boot up an evaluation board (a brand new one with no persistent IP address configuration).

In my dmesg or messages, I don't have any DHCP logs. I also couldn't find any dhcp client in "ps" output. Instead, I got something about avahi daemon. I did some googling, and found that if an IP address was allocated by avahi, it'd be IPv4LL (local-link) with 169.x.x.x subnet. Instead, I'm getting a "proper" IP address of 10.3.x.x that is in range of my lab subnet.

While things seem to be working, I'd like to understand this, and avoid possible conflicts. Logs fragment below.

Thanks,
Raymond

root@intel-corei7-64:/var/volatile/log# grep -i 10.3 log-r2
May 4 02:22:00 intel-corei7-64 daemon.info avahi-daemon[974]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.3.116.211.
May 4 02:22:00 intel-corei7-64 daemon.info avahi-daemon[974]: Registering new address record for 10.3.116.211 on eth0.IPv4.
May 4 02:22:00 intel-corei7-64 daemon.info connmand[923]: eth0 {add} address 10.3.116.211/24 label eth0 family 2
May 4 02:22:00 intel-corei7-64 daemon.info connmand[923]: eth0 {add} route 10.3.116.0 gw 0.0.0.0 scope 253 <LINK>
May 4 02:22:00 intel-corei7-64 daemon.info connmand[923]: eth0 {add} route 10.3.116.1 gw 0.0.0.0 scope 253 <LINK>
May 4 02:22:00 intel-corei7-64 daemon.info connmand[923]: eth0 {add} route 10.3.254.200 gw 10.3.116.1 scope 0 <UNIVERSE>
May 4 02:22:00 intel-corei7-64 daemon.info connmand[923]: eth0 {add} route 10.1.11.200 gw 10.3.116.1 scope 0 <UNIVERSE>
May 4 02:22:00 intel-corei7-64 daemon.info connmand[923]: eth0 {add} route 0.0.0.0 gw 10.3.116.1 scope 0 <UNIVERSE>
May 4 02:22:01 intel-corei7-64 daemon.info connmand[923]: eth0 {add} route 212.227.81.55 gw 10.3.116.1 scope 0 <UNIVERSE>
May 4 02:22:01 intel-corei7-64 daemon.info connmand[923]: eth0 {del} route 212.227.81.55 gw 10.3.116.1 scope 0 <UNIVERSE>

It would help to know a little more about your network configuration to do more than theorize. Generally, ip address of 10.xxx.xxx.xxx are used in local networks. If you set up a virtual machine with a NAT connection, the ip address normally is within that range. My best guess is that prebuilt tarball you refer to is set up to use NAT, but that is only a guess.

You could try a whois or traceroote to find out more about this address.