Client router - can't get to internet, can do DNS lookups

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


Joined: 29 Jun 2019
Posts: 4

PostPosted: Sat Jun 29, 2019 13:39    Post subject: Client router - can't get to internet, can do DNS lookups Reply with quote
I have a LinkSys E1000 v1. I've been using it for two years with DD-WRT v24 bridged (in some way that I forget) to my previous ISP's router.

I got a new ISP.

I factory reset the router, set up password. I initially set up client mode to connect to my new ISP's wifi router.

In client mode I can get a WAN IP. The client router shows up on the ISP's wifi router's device list. I can connect to the ISP router from a computer wired to the client router. I can do DNS lookups from the computer. HOWEVER, I cannot connect to any (other) internet services - either by name or by IP.

I reset it again and tried setting up in client bridge mode. In client bridge mode WAN is disabled (per wiki); otherwise the exact same set of information as above applies (shows up, can do DNS lookup, cannot connect to (other) internet services).

Have tried other devices plugged into the client router.

What's next for debugging? Any help is appreciated.
Sponsor
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6870
Location: Romerike, Norway

PostPosted: Sat Jun 29, 2019 14:37    Post subject: Reply with quote
Does it have it's own ip sub-net?

Is it different from the one used by the ISP router?

Is NAT enabled?
bridgingfail
DD-WRT Novice


Joined: 29 Jun 2019
Posts: 4

PostPosted: Sat Jun 29, 2019 15:09    Post subject: Reply with quote
Per Yngve Berg wrote:
Does it have it's own ip sub-net?

Is it different from the one used by the ISP router?

Is NAT enabled?


I've had it set up both in its own subnet and same subnet in Client mode. In Client Bridge mode it only "works" to the point of DNS lookup when it's in the same subnet.

I don't have any port fowarding rules enabled, but I tried a couple as an experiment before I replied, and didn't help. Also tried turning on UPnP, and that didn't help.
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12915
Location: Netherlands

PostPosted: Sat Jun 29, 2019 16:30    Post subject: Reply with quote
If you did not found it already: https://wiki.dd-wrt.com/wiki/index.php/Linking_Routers

What build are you using (the buildnumber)?

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
bridgingfail
DD-WRT Novice


Joined: 29 Jun 2019
Posts: 4

PostPosted: Sat Jun 29, 2019 17:08    Post subject: Reply with quote
egc wrote:
If you did not found it already: https://wiki.dd-wrt.com/wiki/index.php/Linking_Routers

What build are you using (the buildnumber)?


Yep.

Debugging further I don't think this is a DD-WRT issue. I get the exact same behavior when a client router (whether or not it runs DD-WRT) is plugged into the ISP's router via ethernet. OTOH when a computer is plugged into the ISP's router it works fine.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14246
Location: Texas, USA

PostPosted: Sat Jun 29, 2019 17:50    Post subject: Reply with quote
I have a feeling they locked your ISP-provided router somehow. That just doesn't make any sense.
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