Hello All,
Noticed that (at least with our newest batch of 1.2.2 AEPs) that before the “first time setup”, the debug port lists ETH0 in some sort of “Auto” mode during first boot. It seems that in this mode, if ETH0 is attached to a network with a DHCP client, then the conduit will assign an IP from the remote DHCP server.
If however, you direct connect a PC to ETH0, then the conduit will use its DHCP server to provide a valid IP to that PC.
It seems that the admin console does not support this “Automatic” state. This state is ideal for our pre-shipping process, where our configuration team configures and tests the conduits (while they are attached to a corporate network), but require direct connection once out in the field.
Our work instructions currently have the configuration team manually changing the mode for ETH0 before repackaging, but if there is any way to keep the Conduit in this automatic mode, that would be very beneficial.
Does anyone have any insight into this?
Thank you very much!
Chris