Gateworks Avila GW234x
From DD-WRT Wiki
Revision as of 22:19, 14 January 2008 (edit) Samueldg (Talk | contribs) (→RedHat 5 or similar) ← Previous diff |
Revision as of 22:26, 14 January 2008 (edit) (undo) Samueldg (Talk | contribs) (→Using TELNET) Next diff → |
||
Line 52: | Line 52: | ||
$ telnet 192.168.3.2 9000 | $ telnet 192.168.3.2 9000 | ||
Where '''192.168.3.2''' is the default GW234X ip for access RedBoot and '''9000''' is the default port where RedBoot has a telnet daemon listening. | Where '''192.168.3.2''' is the default GW234X ip for access RedBoot and '''9000''' is the default port where RedBoot has a telnet daemon listening. | ||
+ | 4) Go to the TELNET terminal and prepare de RETURN key and the CTRL+C combination. | ||
+ | 5) Take in view the 2 terminal windows to see when the GW234X is answering the pings and plug-off/plug-on the power to the GW234X. | ||
+ | 6) When the ping has the first answer pres RETURN and '''very quickly''' the CTRL+C keys. | ||
+ | 7) If you were lucked, you can see the RedBoot Prompt: | ||
+ | $ telnet 192.168.3.2 9000 | ||
+ | Trying 192.168.3.2... | ||
+ | Connected to 192.168.3.2 (192.168.3.2). | ||
+ | Escape character is '^]'. | ||
+ | == Executing boot script in 2.490 seconds - enter ^C to abort | ||
+ | ^C | ||
+ | RedBoot> | ||
+ | 8) If you were too slow hitting CTRL+C or hitting RETURN you will not have the RedBoot prompt and will need to go to step 3. |
Revision as of 22:26, 14 January 2008
Contents |
Avila Gateworks
Prerequisites
RedHat 5 or similar
I'm using CentOS 5 to write this.
I have been installed minicom, tftp-server and telnet packages (and their dependences) previously and copied zImage and root.fs to /tftpboot/.
Then I configure /etc/xinetd.d/tftp file as this:
$ cat /etc/xinetd.d/tftp # default: off # description: The tftp server serves files using the trivial file transfer \ # protocol. The tftp protocol is often used to boot diskless \ # workstations, download configuration files to network-aware printers, \ # and to start the installation process for some operating systems. service tftp { socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -s /tftpboot disable = no per_source = 11 cps = 100 2 flags = IPv4 }
And verified that xinetd daemon is runing after the configuration:
$ service xinetd restart Parando xinetd: [ OK ] Iniciando xinetd: [ OK ] $ service xinetd status Se está ejecutando xinetd (pid 10353)...
Windows
See: Intall into GW2348
Accesing via telnet
By default you can access the device using a serial port cable (not null-modem) or using telnet.
Using TELNET
1) Configure your ethernet to have the 192.168.3.1/24 ip address
$ ip addr add 192.168.3.1/24 brd 192.168.3.255 dev eth0 label eth0:3
Where eth0 is your ethernet interface and eth0:3 is the alias (used if you have more than one IP assigned to the interface).
If you have an address assigned to the 192.168.3.0/24 subnetwork, delete it previously:
$ ip addr del 192.168.3.1/24 brd 192.168.3.255 dev eth0 label eth0:3
2) Open a terminal window (a window better than a tab in some terminals programs) and send a ping to the GW234X.
$ ping 192.168.3.2 PING 192.168.3.2 (192.168.3.2) 56(84) bytes of data.
3) Open a new terminal window and prepare to do the telnet to the GW234X. Very important is that you don't hit RETURN yet.
$ telnet 192.168.3.2 9000
Where 192.168.3.2 is the default GW234X ip for access RedBoot and 9000 is the default port where RedBoot has a telnet daemon listening. 4) Go to the TELNET terminal and prepare de RETURN key and the CTRL+C combination. 5) Take in view the 2 terminal windows to see when the GW234X is answering the pings and plug-off/plug-on the power to the GW234X. 6) When the ping has the first answer pres RETURN and very quickly the CTRL+C keys. 7) If you were lucked, you can see the RedBoot Prompt:
$ telnet 192.168.3.2 9000 Trying 192.168.3.2... Connected to 192.168.3.2 (192.168.3.2). Escape character is '^]'. == Executing boot script in 2.490 seconds - enter ^C to abort ^C RedBoot>
8) If you were too slow hitting CTRL+C or hitting RETURN you will not have the RedBoot prompt and will need to go to step 3.