Need to run dhclient before running webboot

[rjoleary]

Describe the bug
If you do not drop down to the shell and run "dhclient" before running "webboot", you will not be able to connect to the network.

To Reproduce
Reproducible in QEMU with the RR script.

Expected behavior
The webboot command should automatically acquire a DHCP lease.

[orangecms]

Maybe default to IPv4 only. When I run u-root's dhclient without ipv6=false, it takes quite a while until it times out.

[rjoleary]

Would it work if we run webboot and dhclient in parallel?

[orangecms]

I feel like the webboot UI could actually include network configuration. Ethernet is the happy path anyway. Wi-fi is much more involved.
However, it would also stretch the scope of the project very much. It has already grown quite a bit with the shift from CLI to GUI.
It's now more about user interface design. My gut feeling is that just calling dhclient programmatically and asynchronously in the background (is that what Goroutines are good for?) is good enough, and printing the network config state in a status bar of some sort would be simple feedback to the user. That's the little downside of networked applications - having to deal with said network. 🙃 Anyway, users would be able to exit and just do their custom setup. So webboot should check whether ethernet or wi-fi adapters have an IP address configured on launch already. WDYT?

[rjoleary]

It looks like webboot calls dhclient for wifi networks. It is just ethernet and qemu where you need to manually run dhclient.

I like your idea of running dhclient in a separate go routine with a status bar!