OpenWrt Forum Archive

Topic: TPLink WDR3600 + ADSL modem - cannot connect to internet => SOLVED

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

I'm trying to configure OpenWRT on my TPLink 3600, where has been installed OK after en earlier bricking!
However I cannot connect to the internet. I'm pretty sure that this is an error on my part rather than a system failure....here are the details

modem (DLink DSL 300T)
-  IP set to 192.168.1.254 (to avoid clash with router IP)
-  ISP user/pass data entered, This is correct, tested by connecting Laptop - modem - internet successfully
-  set to Bridged Mode
--DHCP set to disabled

Router
--stil using default IP 192.168.1.1
-- attempting to connect as follows; laptop via Wifi to router (which works OK), router via ethernet cable to modem, modem to internet

key router settings are as follows
- network> DHCP & DNS - authoritative - this is the only DHCP server on the network
- network > interfaces > WAN > edit > general setup > protocol = DHCP client. (Should I change this, and if so to what? I think an ill-advised switch here was what soft bricked the router, requiring a rescue through failsafe mode)

- in network > interface > WAN > physical settings, I tried ticking the Bridge Interface box to create a bridge to VLAN interface eth0.1 (wan) but this did not work  so I unchecked it.

All other settings are the Openwrt default

- status > overview shows IPv4 and 6 WAN status as Not Connected. Hitting Connect in interfaces > overview has no effect.

There is clearly something silly I have done/not done - can any one point to what it is? Many thanks if you can!!

(Last edited by wayne1958 on 7 Aug 2015, 12:55)

a) Set the modem IP to something not even in the range of the router. I.e. 192.168.2.x instead of using the same range as the router
b) Set the modem to bridge mode, then connect it to WAN on the router, but have the router do the dialing. I.e., PPPoE protocol on the WAN. That's what the bridge mode in a modem is intended for.

metai wrote:

a) Set the modem IP to something not even in the range of the router. I.e. 192.168.2.x instead of using the same range as the router
b) Set the modem to bridge mode, then connect it to WAN on the router, but have the router do the dialing. I.e., PPPoE protocol on the WAN. That's what the bridge mode in a modem is intended for.

Thanks for quick reply.
I've set the ads modem to 192.168.2.254 and left dhcp enabled.
On the router  five changed protocol to PPPOE.  It asks me for pap/chap user/pass combo which I guess if my ads user/pass.
Tried to teconnect but this doesn't work either. .....

PS ive reflashed with the sysupgrade file but that made no difference. f I to try to change to PPPOA which my ISP use, I'm prompted to install package ppp-mod-pppia

(Last edited by wayne1958 on 31 Jul 2015, 18:38)

Update - I've tried disabling DHCP in the modem so it is
completely dumb but still no difference.  The router regards the pppoe WAN interface as down

Sorry for the late reply. I wrongly (and arrogantly) assumed you would connect via PPPoE. Of course, if your provider requires PPPoA, this will not help yet.

You have two options:
a) Try to get internet to the new router temporarily (i.e., connecting it to another router or whatever you are using right now to get internet access, just to download the necessary packages). Effectively turning it into a "regularly connected machine" to install the required packages for PPPoA.
b) Download the necessary packages yourself, transfer the file to the router and install them manually. Which is a bit of a hassle because the PPPoA packages have a few dependencies (i.e., require other packages in turn), but is doable.

hi
use DSL standalone(make the usal DSL connection) and output a lan(192.168.1.1...) with DHCP enabled
put DSLs lan to WDR3600 wan(wan configured DHCP), output WDR3600 lan(192.168.2.1) with DHCP
connect WDR3600 lan to PC(it will get IPs in the range ....2.2 - ....2.254)

in this configuration you can access DSL by 192.168.1.1 and WDR by 192.168.2.1

you can also connect straight to DSLs lan

metai wrote:

Sorry for the late reply. I wrongly (and arrogantly) assumed you would connect via PPPoE. Of course, if your provider requires PPPoA, this will not help yet.

You have two options:
a) Try to get internet to the new router temporarily (i.e., connecting it to another router or whatever you are using right now to get internet access, just to download the necessary packages). Effectively turning it into a "regularly connected machine" to install the required packages for PPPoA.
b) Download the necessary packages yourself, transfer the file to the router and install them manually. Which is a bit of a hassle because the PPPoA packages have a few dependencies (i.e., require other packages in turn), but is doable.

Hi there - thanks for the reply!! I tried option a but filed as I could see a way to change the IP on the TPlink router to avoid it clashing with my ISP-supplied router. Somehow soft bricked it again, and had to restore via failsafe.
That was it for me and so returned to stock firmware.
Thanks a lot for your support anyway

The interesting thing is that your stock firmware probably doesn't do anything different than OpenWrt in its stock configuration, aside from the fact that it comes without PPPoA support out of the box. It shouldn't be the stumbling stone to run OpenWrt, but I can see that it is probably a bit much for a beginner.

For posterity, there are two ways to get PPPoA support:
a) Hook up the OpenWrt device to an existing router and make it download the packages
b) Download the packages manually, transfer them to the OpenWrt device (e.g. via SCP), and install them from an SSH command line

(Last edited by metai on 4 Aug 2015, 00:47)

metai wrote:

The interesting thing is that your stock firmware probably doesn't do anything different than OpenWrt in its stock configuration, aside from the fact that it comes without PPPoA support out of the box. It shouldn't be the stumbling stone to run OpenWrt, but I can see that it is probably a bit much for a beginner.

For posterity, there are two ways to get PPPoA support:
a) Hook up the OpenWrt device to an existing router and make it download the packages
b) Download the packages manually, transfer them to the OpenWrt device (e.g. via SCP), and install them from an SSH command line

Hi there again!!! You are quite correct. I ended up
1) reverting to stock
2) configuring the ADSL modem as DHCP and handling the authentication from there
3) configuring the router as DHCP
4) and I could then connect.  Not really what I wanted but the setup now works
5) I then reflashed back to openWRT duplicated this set up and again, back in business.

So I have achieved the main objective - to get onto open source software on my router. Ive now dowloaded the PPPoA packages for openWRT and will experiment again in due course.....

You should. At the moment, you are doing "Double NAT", which means that everything from outside and inside will get "translated" between networks twice -- once in the "modem", and once in the OpenWrt router. It's by no means the end of the world, but it's not really ideal and a step that can be eliminated. In your case, by using the modem as just a modem through PPPoA, of course.

wayne1958 wrote:
metai wrote:

The interesting thing is that your stock firmware probably doesn't do anything different than OpenWrt in its stock configuration, aside from the fact that it comes without PPPoA support out of the box. It shouldn't be the stumbling stone to run OpenWrt, but I can see that it is probably a bit much for a beginner.

For posterity, there are two ways to get PPPoA support:
a) Hook up the OpenWrt device to an existing router and make it download the packages
b) Download the packages manually, transfer them to the OpenWrt device (e.g. via SCP), and install them from an SSH command line

Hi there again!!! You are quite correct. I ended up
1) reverting to stock
2) configuring the ADSL modem as DHCP and handling the authentication from there
3) configuring the router as DHCP
4) and I could then connect.  Not really what I wanted but the setup now works
5) I then reflashed back to openWRT duplicated this set up and again, back in business.

So I have achieved the main objective - to get onto open source software on my router. Ive now dowloaded the PPPoA packages for openWRT and will experiment again in due course.....


Just a quick note; PPPoA means PPP over ATM, this requires that the device running the PPPoA client software id directly connected to an ATM net. So PPPoA on your modem will work, but PPPoA on the router connected via ethernet to the modem will NOT. Some UK ISPs will allow you to use either PPPoA or PPPoE and auto detect which on their end, and some ADSL modems will allow you to use PPPtP to connect to the modem and will translate this into PPPoA but I doubt your modem offers this.


Best Regards
        M.

The discussion might have continued from here.