DCHP NAK problem upon nfs boot with beaglebone black

Hello,

First of all, thanks a lot for this excellent material for BBB. I really like it.

I’d like to update a set of BBB but I have no access to the sdcard.
Therefore I am trying to do the update by:

  • booting the bbb over nfs
  • then performing the dd operations on the flash disk

I am using the debian 8.2 image dated 25/10/2015

I have set up an additional BBB as tftp & nfs server

The BBB i am trying to update is flashed with the 8.2 version and the uEnv.txt is used in order to boot from nfs:

##Rename as: uEnv.txt to boot via nfs

##https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

##SERVER: sudo apt-get install tftpd-hpa
##SERVER:
##SERVER: zImage boot:
##SERVER: TFTP_DIRECTORY defined in /etc/default/tftpd-hpa
##SERVER: zImage/.dtb need to be located here:
##SERVER: TFTP_DIRECTORY/zImage
##SERVER: TFTP_DIRECTORY/dtbs/
.dtb
##SERVER:
##SERVER: uname_r boot:
##SERVER: TFTP_DIRECTORY defined in /etc/default/tftpd-hpa
##SERVER: Change TFTP_DIRECTORY to /NFSEXPORT/boot
##SERVER: TFTP_DIRECTORY/vmlinuz-${uname_r}
##SERVER: TFTP_DIRECTORY/dtbs/${uname_r}/*.dtb

##client_ip needs to be set for u-boot to try booting via nfs

client_ip=192.168.3.201

#u-boot defaults: uncomment and override where needed

server_ip=192.168.3.100
gw_ip=192.168.3.1
#netmask=255.255.255.0
#hostname=
#device=eth0
#autoconf=off
root_dir=/home/debian/rootfs
#nfs_options=,vers=3
#nfsrootfstype=ext4 rootwait fixrtc

##use uname_r= only if TFTP SERVER is setup for uname_r boot:
#uname_r=

All these devices are connected to a router with dhcp static IP defined:

  • for server: 192.168.3.100
  • for BBB to be updated: 192.168.3.201

It seems that for some reason (??) :

  • the BBB recorded the original IP is used before (192.168.3.124) and makes a DHCP request with this IP
  • the routeur then sends back a DHCP NAK (because it has another address in dhcp static ip table)
  • this causes the nfs server not beeing seen by the client BBB

Please see log here:

[http://pastebin.com/hkksqD6g](http://pastebin.com/hkksqD6g)

Here is a screenshot of the dhcp request and nak:
[<img src="https://lh3.googleusercontent.com/-T9t0hl9BDzM/Vkb07imnA0I/AAAAAAAAAAM/k-fMgjy-EYY/s320/bootp.png" style="" border="0" height="141" width="320">](https://lh3.googleusercontent.com/-T9t0hl9BDzM/Vkb07imnA0I/AAAAAAAAAAM/k-fMgjy-EYY/s1600/bootp.png)

The tftp process is OK but the nfs mount fails after the dhcp nak.

Furthermore, it has to be noted than when evrithing is configured with the original clien IP (192.168.3.124) then the nfs boot process completes correctly.

Plase let ne know if there is a fix to prevent the client BBB to use the original 192.168.3.124 adress

Regards,
Christophe