OpenWrt Forum Archive

Topic: oops i semi screwed up my router

The content of this topic has been archived on 30 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

like the topic suggest, i manage to semi screw up my buffalo nfinity wzr-hp-g300nh router.  what i did was disabled the dhcp server and setting the IP address of br-lan interface to 192.168.1.2.  now the kicker is that i can't access it via http, telnet, ssh.

i tried the 30/30/30 reset and no luck.
try going to failsafe, but i still can't connect
http://g300nh.blogspot.com/2010/06/firm … overy.html with openwrt-ar71xx-wzr-hp-g300nh-jffs2-tftp and openwrt-ar71xx-wzr-hp-g300nh-jffs2-sysupgrade in an attempt to reflash and well...no luck

any advice on how i can connect to the router and set it up again?

cheers.

The reset button doesn't function as reset in OpenWrt. Install Wireshark to see if you receive any broadcast udp packet while power the router on.

thanks for the tips and suggestions

i managed to fix the issue by doing a hard reset, putting the router to failsafe mode and telnet in fix it.  took a while to figure it out.

>> i managed to fix the issue by doing a hard reset, putting the router to failsafe mode and telnet in fix it.  took a while to figure it out.

How do you put a G300NH in failsafe mode ?!

It looks that I am in the same situation ! Nothing happens ont the LAN interfaces.
DHCP resquests are sent through the WAN but I can not access anything (eg ssh)
from WAN ! Reset button seems useless with OpenWrt (so 30/30/30 reset fails).

Thanks for any hint

manu wrote:

>> i managed to fix the issue by doing a hard reset, putting the router to failsafe mode and telnet in fix it.  took a while to figure it out.

How do you put a G300NH in failsafe mode ?!

It looks that I am in the same situation ! Nothing happens ont the LAN interfaces.
DHCP resquests are sent through the WAN but I can not access anything (eg ssh)
from WAN ! Reset button seems useless with OpenWrt (so 30/30/30 reset fails).

Thanks for any hint

I have no clue how to set the G300NH in failsafe mode, but I have managed to flash the openwrt-ar71xx-wzr-hp-g300nh-jffs2-tftp  binary with the instructions from http://g300nh.blogspot.com/2010/06/firm … overy.html once I made the adjustments below.

I noticed that my PC reset all ARP addresses, including the static ones, as soon as the ethernet cable became unpowered from the other end. This happened whenever I pulled the ethernet cable from the router OR when I unplugged the router (irrespective of operating system). If you have the same problem, you should be able to periodically check that the arp address you added is still in the list while you perform the steps in the instructions.
My solution to this was to add a switch between the router and the PC, which kept the cable powered.

My second problem was that I didn't manage to do it in Windows for some reason, but since I had a virtual machine running Ubuntu I didn't investigate it further.

I hope this insight can help someone.

Thank you for the link, but I am not able to flash the G300NH anymore as far as OpenWrt is already installed. The problem is that the system is "locked" : the only usable interface is the WAN one, but I can not ssh through it.

It seems that the only solution is the serial port, however I do not know where the pinouts are ...

Yes ! Sorry, I mean I do not know where are pin number 1 on the board and so on ...

Cheers

Here's a pic:
http://www.dd-wrt.com/phpBB2/files/pin4_359.jpg

But as this pictured is labeled, pin 1 is RX, whereas the OpenWrt wiki says pin 1 is VCC.  Actually the picture is labeled incorrectly in terms of numbers, because the square is pin 1... but at least it shows where the pinouts on the board are.

Per the above picture:
1--RX
2--TX
3--GND
4--VCC +3.3V(unconnect)

Just reverse the numbers to match the OpenWrt wiki (because the square is pin 1).

From this thread:
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=434920

(Last edited by LinkZ on 6 Jan 2011, 22:25)

Thank you very much !!!

i've had a very similar problem to canucks and manu on a wrt150n

i poked around in /etc/config/network and now it refuses to talk to my computer through any of the regular ethernet ports.  it sends dhcp requests through the "internet" port, but all maintainence through that port is disabled.  also, the udp packet appears to be horribly mangled.  i'll include a hex dump below.  i cannot ping the router or anything in failsafe mode; it does not respond to ARP requests.  could i have fried some hardware or something?  D:

here is the output from "hexdump -v -t x out"

0000000 a1b2c3d4 00040002 00000000 00000000
0000020 00000060 00000001 4d263aea 0005cf86
0000040 00000060 00000413 ffffffff 1d00ffff
0000060 c049d97e 00450008 00000504 11400040
0000100 a8c097b2 a8c00101 9de7ff01 f1033713
0000120 adde0571 61656c50 00006573 00000000
0000140 00000000 00000000 00000000 00000000
0000160 00000000 00000000 00000000 00000000
0000200 00000000 00000000
0000210

What do you call a "failsafe mode" ?

And where does this UDP packet come from ? Are you sure this is UDP packet ? Try to use a network
analyzer (tcpdump eg) to decode it, ...

that was the output of a hexdump'd raw capture from tcpdump.  i'm going to attach the output of tcpdump to this one.  i'm using failsafe mode as it's used on the troubleshooting pages.  all that is in the packet is "Please", followed by some nulls


tcpdump's output:

17:18:55.093936 IP 192.168.1.1.59293 > 192.168.1.255.4919: UDP, length 1001
    0x0000:  4500 0405 0000 4000 4011 b297 c0a8 0101
    0x0010:  c0a8 01ff e79d 1337 03f1 7105 dead 506c
    0x0020:  6561 7365 0000 0000 0000 0000 0000 0000
    0x0030:  0000 0000 0000 0000 0000 0000 0000 0000
    0x0040:  0000 0000 0000 0000 0000 0000 0000 0000
    0x0050:  0000

(Last edited by Styx on 6 Jan 2011, 23:42)

As for me, things are settled ! Thanks for your help. The serial port is a must !

Now, I face a new "problem". I do not understand the switch configuration options. I will open a new
discussion on  this topic.

The discussion might have continued from here.