Hello @timothyc95,
the easiest way is to modify the shell script that is sourced at boot.
This can be done as follows:
Click on the alpine node and select 'Config'.
Add the following line to the 'node.cfg' file and then click 'Save':
# get IP address on eth0 via DHCP
udhcpc -i eth0 -q
Then turn on the alpine node and it will get an IP address on eth0 via DHCP provided there is a DHCP server for this network.
Note: If the node is running already, you need to stop it and wipe the config before you can modify the shell script.
HTH!
Hi @timothyc95,
do you mean the console login? The default is cisco/cisco as shown in my previous post, unless you changed this.
As usual be careful not to add a space at the end of the password when editing the node.cfg file.
I also noticed that you might not get a login prompt if the node fails to get an IP address.
I used a simple setup for testing:
Only Rtr01, Sw01 and the alpine node are used for this test. DHCP is configured on Rtr01.
Rtr01 and Sw01 are started first to make sure that they are up and running so that the alpine node can get an ip address.
On Rtr01 debugging for DHCP is enabled when the alpine node is started:
Once the alpine node got an IP address, the console login appears shortly thereafter.
Login with the default credentials cisco/cisco:
On the alpine node you can verify the IP address received on eth0.
This IP address can now be used to SSH into the node from Sw01 using the same credentials of cisco/cisco:
Hence everything is working just fine as expected.
So double-check the username/password settings in the node.cfg file and make sure that DHCP is working correctly.
HTH!
