Ticket #605 (Duplicate)Wed Jun 14 22:47:40 UTC 2023
Contacting DHCP server on startup doesn’t time out if no USB adapter is connected.
| Reported by: | Cameron Cawley (3514) | Severity: | Normal |
| Part: | RISC OS: Boot sequence | Release: | |
| Milestone: | Status | Duplicate |
Details by Cameron Cawley (3514):
If a USB interface is configured and connected to the computer, but no Ethernet cable is plugged in, contacting the DHCP server will time out after a while. If the adapter is not connected, it won’t time out until it is plugged in, or if the user cancels the boot sequence by pressing escape.
Changelog:
Modified by Sprow (202) Sat, June 17 2023 - 08:31:41 GMT
- Status changed from Open to Duplicate
It is intentional that DHCP first blocks for the interface to be available and then starts any time out. That’s what the -b switch does in the DHCPExecute command is for (in your Choices.Internet.Startup).
What’s not handled gracefully is if the NIC vanishes after those choices are written, but that’s captured in Ticket #358.
