Can't access router GUI after changing DNS

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Author Message
Carbon13
DD-WRT Novice


Joined: 18 Oct 2015
Posts: 6

PostPosted: Wed Feb 24, 2016 0:20    Post subject: Can't access router GUI after changing DNS Reply with quote
Hi,

I've been running dd-wrt (kong) on a R7000 router for several months now. Using PIA VPN and I decided tonight to change DNS servers and now I can't access the router at all. Have I bricked my R7000?? Please help!
Sponsor
Carbon13
DD-WRT Novice


Joined: 18 Oct 2015
Posts: 6

PostPosted: Wed Feb 24, 2016 14:10    Post subject: Reply with quote
A bit more background.



I'm running through my ISP's router in bridge mode, I've rebooted it all (disconnecting all connections etc, waiting, rebooting). Checked connections to make sure they are working (they are, which is how I'm online now).

I then had this connected to the R7000 with DD-WRT, with a VPN (PIA) running. When I changed the DNS servers everything went to hell. I cannot connect at all to the router now (via wireless or ethernet). I keep getting an unidentified network and limited connection and cannot access the GUI through browser (yes I have cleared the cache). I also tried running ipconfig but there is no default gateway listed.

I'm really stuck. Help me ObiWan!!
Carbon13
DD-WRT Novice


Joined: 18 Oct 2015
Posts: 6

PostPosted: Wed Feb 24, 2016 17:27    Post subject: Reply with quote
Sorry for originally posting in the wrong location.

I did go back read the announcements. Sorry, I do not recall what version of kong I'm running (but it was installed last Oct. and would have been most current then).

I did try a hard reset 30-30-30 (timed it) and it did not help.

Not sure where to go from here so PLEASE HELP!
Carbon13
DD-WRT Novice


Joined: 18 Oct 2015
Posts: 6

PostPosted: Fri Feb 26, 2016 1:40    Post subject: Peacock question Reply with quote
Well after the overwhelming response of zero I'm guessing I've not followed some forum etiquette and I'm on my own.

I'm trying my best to follow the peacock thread to see if my router is bricked.

It says to:

Quote:
d. Set your computer ip address to 192.168.1.10 (if that is the same subnet as the router is supposed to be at).
e. Try to ping the router using the command "ping -t 192.168.1.1" (presuming that 192.168.1.1 is the address your router was set to.) See if there are ANY responses. (There WILL be A response...you are looking for a ttl= response)



Is step "d" really 192.168.1.10 or is supposed to be the same IP as the router at 192.168.1.10.

Also, I don't know the subnet but I used the default of 255.255.255.0 or something like that.

I've tried it exactly as written and I get no response. If I set both to the same IP I get a ttl=128.

So now what? Please someone help, I'm trying my best here.
Carbon13
DD-WRT Novice


Joined: 18 Oct 2015
Posts: 6

PostPosted: Fri Feb 26, 2016 2:37    Post subject: Reply with quote
I connected to the router and ran ipconfig from command line and got an IP 169.254.205.103 and subnet 255.255.0.0

Tried changing my computer to IP 169.254.205.100 and same subnet and tried to ping ...103 and got nothing again. I also tried https:// that IP in a browser but no dice either. I have no idea how the router got this IP address and why the 30-30-30 reset isn't taking it back to default. ARRRGH!!


I feel like I'm talking to myself but I'm still holding out hope that there is someone kind enough to assist me.
muckerphuck
DD-WRT User


Joined: 08 May 2008
Posts: 65
Location: 3rd Rock

PostPosted: Fri Feb 26, 2016 4:06    Post subject: Reply with quote
You might have to tftp flash if nothing responds. See Peacock note 11.

You also might have to use a factory firmware recovery utility from netgear.

One way for netgear also Involves tftp.
http://kb.netgear.com/app/answers/detail/a_id/19841/~/reinstall-the-firmware-on-a-router-without-the-setup-cd-recovery-tool

http://www.myopenrouter.com/article/how-debrick-or-recover-netgear-r7000-r6300v2-or-r6250-wi-fi-routers

I found both of these in the R7000 sticky at the top of the broadcom section.

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=264152

_________________
[Charter] E31U2V1 DOCSIS 3.1 - Cable Modem
[Broadcom] Netgear R6300v2 - Main Router - Netgear Stock Firmware
[Broadcom] Linksys WRT54GL -Access points x 2 - DD-WRT v2.4-r37932 mini generic (12/08/18 ) K2.4
[Broadcom] Asus RT-AC66U - Bridges x 2 - DD-WRT v3.0-r29193 giga (03/02/16 ) K3X
[Broadcom] Asus RT-N16 - Access Point - DD-WRT v3.0-r37442 big ( 10/19/18 ) K3X
[Mikrotik] Wap60g - Bridges x 2 - RouterOS v6
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum