
(Re-sending now that I'm subscribed to the list)
Hi all,
I am running U-Boot on an embedded device that is connected via Ethernet to my workstation. The workstation is running dhcpd and U-Boot is able to successfully obtain an IP address via DHCP from the server. However, the `serverip` environment variable is not being set which prevents U-Boot from continuing to boot over the network. I have to manually enter `setenv serverip 10.0.10.1` each time.
How do I get the DHCP server to set the serverip variable? My dhcpd.conf file is quite simple:
subnet 10.0.10.0 netmask 255.255.255.0 { option routers 10.0.10.1; range 10.0.10.2; }
I would have thought the 'option routers' line would do the trick, but apparently not. I've done a bit of searching online but haven't yet found anything helpful.
Thanks,
Greg

Hi,
On Thu, 2021-07-01 at 15:56 +0000, Gregory Anders wrote:
(Re-sending now that I'm subscribed to the list)
Hi all,
I am running U-Boot on an embedded device that is connected via Ethernet to my workstation. The workstation is running dhcpd and U-Boot is able to successfully obtain an IP address via DHCP from the server. However, the `serverip` environment variable is not being set which prevents U-Boot from continuing to boot over the network. I have to manually enter `setenv serverip 10.0.10.1` each time.
How do I get the DHCP server to set the serverip variable? My dhcpd.conf file is quite simple:
subnet 10.0.10.0 netmask 255.255.255.0 { option routers 10.0.10.1; range 10.0.10.2; }
I would have thought the 'option routers' line would do the trick, but apparently not. I've done a bit of searching online but haven't yet found anything helpful.
This is just a guess because I don't have a dhcpd server running, but with dnsmasq we have this working without problems. From a quick search, maybe adding
next-server 10.0.10.1;
might do the trick?

On Jul 2, 2021, at 7:39 AM, Harald Seiler hws@denx.de wrote:
This is just a guess because I don't have a dhcpd server running, but with dnsmasq we have this working without problems. From a quick search, maybe adding
next-server 10.0.10.1;
m
I know this is two months later, but I *finally* got around to trying this and it does work! Thanks Harald! I’m not sure why I’ve never had to use this in the past, but now I know.
Greg
participants (2)
-
Gregory Anders
-
Harald Seiler