BB-xM && dhcp assigned ip

GoogleGroups
1

Hi all,
I have a BB xM with angstrom downloaded from Narcissus.
I configured network intervace to get ip form a dhcp server.
The ip is assigned but if I reboot the BB it get a new IP different
from the last. In the same network it doesn't happens to my linux PC
(it always get the same IP).
It seems like if BB doesn't stop correctly network interface while
rebooting so the DHCP assign a new IP because of the old one results
occupied.

Is this possible?

2

this is due to the fact that the ethernet interface does not have a
statically assigned mac address. each time you boot, a new mac address
is assigned.

you can patch you kernel with something like this:

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-natty.git;a=commitdiff;h=f4e8ab7cc4e819011ca6325e54383b3da7a5d130

Dave

3

Thanks prpplague.

Why hasn't BB a static mac address?

PS. the link you posted is wrong.

4

Thanks prpplague.

Why hasn’t BB a static mac address?

PS. the link you posted is wrong.

I believe the correct patches are at:
https://patchwork.kernel.org/patch/660541/
https://patchwork.kernel.org/patch/660571/

It would be great if someone would add these to the Angstrom recipes for the linux-omap kernels for 2.6.32 and 2.6.37 at least for the BeagleBoard. It would be a bit redundant, but you could put the exact same entries in the BeagleBoard platform board file.

5

Thanks prpplague.

Why hasn’t BB a static mac address?

I forgot to answer this question, though I’ve answered it in other places it is good to have the answer on all the various threads. The reason is that we wanted to save some cost by not adding any non-volatile memory exclusively for the purpose of holding the MAC address, knowing that the device already has uniquely identifying information and that you could put code to initialize it on the non-volatile storage containing your boot image. Ultimately, it was probably the wrong choice.