goalmarketing / vigor2130

Automatically exported from code.google.com/p/vigor2130
0 stars 0 forks source link

Beta software possibly unusable. #37

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
I was running the beta, when the console stopped completing directory names 
when I pressed tab.
Then the 24-hour disconnect occured and the router didn't reconnect no matter 
how often I click dial. It also ignored the Reboot request from the 
webinterface. When I typed "reboot" in the ssh window the console stopped 
responding but the webinterface kept running (even when I refreshed). So I 
decided to do a cold restart and shut the router off via the switch, even after 
several minutes I couldn't ping it and now the LEDs are on (except those for 
LAN) but I can not ping it, access the webinterface or do anything.
It's pretty much dead

Original issue reported on code.google.com by TheEvilO...@googlemail.com on 15 Jul 2011 at 3:21

GoogleCodeExporter commented 8 years ago
I tried to reset the configuration (factory reset button for 5 seconds, until 
the ACT LED starts blinking) and I tried to force the router into TFTP mode by 
holding down factory reset during start till ACT and the neighbor LED were 
blinking simultaneously.
Neither of those has done anything to change the problem.

What is my next step?

Original comment by TheEvilO...@googlemail.com on 15 Jul 2011 at 4:02

GoogleCodeExporter commented 8 years ago
Let me assume your configuration is broken.
The only way to recover it is to do tftp upgrade by ".rst" firmware.

1. Enter tftp mode : power on with "factory reset" button pressed
2. tftp upgrade the ".rst" firmware, change firmware from .all to .rst
   also set LAN IP to 192.168.1.10
   > tftp -i 192.168.1.1 put v2130xxxx.rst  (or by draytek firmware upgrade utility)

It should recover your 2130 to factory default state.

Original comment by jht...@gmail.com on 15 Jul 2011 at 6:39

GoogleCodeExporter commented 8 years ago
Yes it did... after about 20 restarts I was finally able to reflash it.
Before that I got timeouts each time I tried to flash.

Original comment by TheEvilO...@googlemail.com on 15 Jul 2011 at 5:11

GoogleCodeExporter commented 8 years ago
did the openWRT package switched to backfire 10.03 and not kamikaze anymore? 
1.5.2_beta is running great on my machine. vpn worked immediately!

Original comment by johannes...@gmail.com on 26 Jul 2011 at 2:04

GoogleCodeExporter commented 8 years ago
We are very pleased to hear your VPN problem is solved.
Can you help to update the previous reported issues ?

Update to latest openWRT need big effort.
We will add the features which is needed and also keep the firmware quality.

Original comment by jht...@gmail.com on 26 Jul 2011 at 11:47