📜 ⬆️ ⬇️

We revive the DSL-G604T router

I got a wonderful unit, I was told that he knows how to do a lot, but he works with errors (for this reason he got it). Turning in my hands, I decided to look at what this device is capable of.

image

Overview


Since I was given only the router itself, I decided to first see what it is. Of course, the internet helped me.
Brief characteristics:
Type ofWi-Fi ADSL access point (802.11g)
VPN pass through supportthere is
Protection of informationWEP, WPA
Routerthere is
Switch4xLAN

On the manufacturer’s website there is nothing about this device. Therefore, we had to look for reviews and articles in other places (dated 2005):
[IXBT.COM] D-Link DSL-G604T Wireless ADSL Router
[IXBT.COM] Performance Testing
These articles were enough for me to understand what I was holding.

purpose


Purpose: Set up a wi-fi hotspot for internet access
')

Used appliances


I have available:
Asus eee pc 901 green
Toshiba Portege SS S4 / 275PNHW
Nokia 5800 XpressMusic

All devices work with wi-fi and have different OS: Ubuntu Linux , Windows XP , Symbian OS

Setting up wi-fi on the router was not difficult, the web interface is not the most convenient, but this is not a hindrance. Initially, inside the network we set up a router on the Internet, and our router will connect to it. DHCP is extremely clumsy and refused to work normally, so I had to prescribe statically IP addresses on devices.

Problems


The access point is working normally, but the wi-fi connection periodically hangs or disappears. The signal is good only within the room, already 40% of the signal is through the supporting wall. When the Nokia 5800 connects to WPA, after 1 minute, the wi-fi access point simply rebooted and recovered within 2 minutes, although at those settings the laptops work fine. So it was decided to reflash the point.

Flashing


All sites say that everything runs smoothly and beautifully, we download the firmware through the web interface and everything is ok. In my case, the web interface gave an error, and the dot died during the firmware. So I had to conjure.

I tried to install an alternative firmware from healthlife , in the archive with the firmware there was the firmware itself in the form of an img file, the tiupgrade utility and its cofigs.

After an unsuccessful operation through the web, the point stopped responding to all external signals, no lights flashed except for the network status. The search gave me three ways to revive her:
1) ADAM2 FTP server
2) Corrupted-image mode in tiupgrade utility
3) Via EJTAG cable

ADAM2 FTP


In the first case, the developer offered to solve the problem like this:

B D-Link FTP ADAM2 ip 10.8.8.8,
DSL-G604T, ip 10.48.88.66,
eth0:1, :
[root@mcmcc root]# ifconfig eth0:1 10.8.8.7 up
ftp ip 10.8.8.8,
[igor@mcmcc igor]$ ftp 10.8.8.8 ( DSL-G604T - 10.48.88.66)
2
, .. ftp ,
, :
Connected to 10.8.8.8.
220 ADAM2 FTP Server ready.
530 Please login with USER and PASS.
530 Please login with USER and PASS.
KERBEROS_V4 rejected as an authentication type
Name (10.8.8.8:igor): adam2
331 Password required for adam2.
Password: adam2
230 User adam2 successfully logged in.
Remote system type is UNIX.
ftp> debug
Debugging on (debug=1).
ftp> bin
---> TYPE I
200 Type set to I.
ftp> quote MEDIA FLSH
---> MEDIA FLSH
200 Media set to FLSH.
ftp> put fs.img "fs.img mtd0" ( : put kernel.img "kernel.img mtd1")
local: fs.img remote: fs.img mtd0
---> PASV
227 Entering Passive Mode (10,8,8,8,162,0).
---> STOR fs.img mtd0
150 Opening BINARY mode data connection for file transfer.
226 Transfer complete.
1318920 bytes sent in 30.3 seconds (54 Kbytes/s)
ftp> quote REBOOT
---> REBOOT
221-Thank you for using the FTP service on ADAM2.
221 Goodbye.
ftp> quit
---> QUIT
:
debug , quote MEDIA FLSH,
BINARY , .. bin, MTD, ..
:
mtd0: fs ( fs.img, )
mtd1: kernel
mtd2: ftp ADAM2
mtd3: Environment + config.xml


Since the firmware is based on the writings of McMCC , his method helped a lot in this situation. Half an hour of games with a power point, I could not find the ftp server from ADAM2, as well as the point itself at addresses 10.8.8.8, 10.48.88.66, 192.168.1.1

TIUPGRADE Corrupted-image mode


The developer proposes to solve it this way:
GUI tiupgrade.exe Windows/Wine Unix:
1) tiupgrade.exe.
2) ip .
3) "" .
4) ,
"Corrupted-image mode".
!!! tiupgrade.exe ip ADAM2, , , 10.48.88.66,
, 199, ..
192.168.1.0, ip 192.168.1.199...


Having connected the laptop with the patch and the dot, I ticked Corrupted-image mode in the program and followed all its instructions several times without success, the program crashed several times with a memory access error. I was already thinking of switching to the third method, but just in case I pulled out a switch and stuck a point and a laptop into it. Again, I checked the different options for turning off the power and turning it on, but I saw a new Script error at different stages of the flashing.

Everything was decided only by setting the address on the laptop 192.168.1.2 and shutting down all programs except the tiupgrade utility, in general, if a script error occurs, then you can safely try again, the firmware got up 5 times and the router started.

Conclusion


Flashing solved all the problems that arose with the old firmware from D-Link, wi-fi began to work stably and the point from the connection with the mobile phone did not restart. The router stopped hanging and it became much more pleasant to work with it. The web interface is taken from the Accorp firmware (the McMCC developer wrote the Accorp firmware) and is much nicer than the native one from D-Link.

PS


As for the third option, I was ready to try it, but the program method saved me from this method.
Successful to you experiments!

Source: https://habr.com/ru/post/48095/


All Articles