RedBoot Telnet IP address
elektra
I have noted that Atcom has configured a different bootloader (RedBoot) IP
address on the beta production MPs - outsch!
RedBoot> ip_addr
IP: 192.168.1.124/255.255.255.0, Gateway: 192.168.1.1
Default server: 192.168.1.180
RedBoot>
I don't know if Atcom has set these parameters for all the beta production
MPs.
If you need to find out the RedBoot IP I suggest you install "nmap" on your
computer and use the following script:
while (true); do nmap -sP 192.168.1.2-254 | grep "is up" ; done
Configure your workstation to use 192.168.1.1 IP, netmask 255.255.255.0.
Start the script and power-cycle the MP. (You can stop the script with Ctrl+C
when you are done.)
Scanning the full IP range takes > 5 seconds on my machine. The RedBoot
timeout might be configured to 3 or 5 seconds, so you may need more than one
try. (i.e. power-cycle the MP, wait a while, if no host is found, power-cyle
it again) If you wait for too long the script will detect 192.168.1.20. This
response will come from the OpenWrt firmware which if it is already up and
running.
You might want to fix this problem once you are connected to RedBoot.
Perform:
RedBoot> fconfig
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7
.. exec
Enter script, terminate with empty line
>> fis load -l vmlinux.bin.l7
>> exec
>>
Boot script timeout (1000ms resolution): 5
Use BOOTP for network configuration: false
Gateway IP address: 192.168.1.1
Local IP address: 192.168.1.20
Local IP address mask: 255.255.255.0
Default server IP address: 192.168.1.1
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xa83d0000-0xa83e0000: .
... Program from 0x80ff0000-0x81000000 at 0xa83d0000: .
RedBoot>
This will set the RedBoot IP to 192.168.1.20. The TFTP server (your
workstation) that RedBoot is trying to connect to if you flash the firmware via
RedBoot is now 192.168.1.1
Cheers,
Elektra