Getting a TP-Link 8817 and Asus RT-N66U talking

Hi guys I need some help. I have the above modem and router combo which is my first foray into separates. Previously I have just gone with the DG834G line of routers which have served well over the years and I wanted something more powerful and up to date.

My problem is I can't seem to get the 8817 talking with the RT-N66U. I had read glowing recommendations from people about this pairing so I went with them.

As I understand it, the 8817 has to be put in bridging mode once it's been set up to connect to the internet, but once I do that the internet light goes out! I have connected it's LAN port to the WAN port on the Asus, the best I've managed so far is the Asus gets an IP from the 8817 (not my actual internet static IP), it says it's connected but there's no throughput and all pages fail.

I'm on Be* Unlimited if that helps, please I'm tearing my hair out

Edited by Cheule (Mon 18-Mar-13 16:04:04)

Did you set the RT-N66U up to provide the authentication details via a PPPoE session on its WAN port?

You are not alone it seems.

http://forum.tp-link.com/showthread.php?2504-Td-8817...

In reply to a post by Cheule:

Hi guys I need someAs I understand it, the 8817 has to be put in bridging mode once it's been set up to connect to the internet, but once I do that the internet light goes out!

Normally the internet light indicates that the modem/router has obtained an IP address, putting it into modem only mode drops the internet light because it drops the IP address (which the connecting router then should then obtain).

In reply to a post by MrSaffron:

Did you set the RT-N66U up to provide the authentication details via a PPPoE session on its WAN port?

BE would require Ethernet over ATM.

And how many routers with Ethernet WAN ports have you seen with Ethernet over ATM?

Modems that other bridge mode can do various tricks sometimes, so while it may get the auth details via PPPoE, it does not always mean it is establishing a PPPoE connection out over the Internet.

Some bridge modems do the authentication still, and simple hand the Internet IP address to the first device on its LAN side that requests a DHCP based IP address.

Personally don't like the bridge modes because the router manufacturers seem to leave lots of bugs in that option.

I think you're referring to half-bridge mode, and DHCP spoofing.

In reply to a post by MrSaffron:

And how many routers with Ethernet WAN ports have you seen with Ethernet over ATM?

More technically, it's RFC2684, which is what BE use, and has nothing to do with PPPoE. A router in this mode will happily connect to BE over a bridged modem (in fact, the router is just acting as a standard DHCP client).

Edited by Oliver341 (Mon 18-Mar-13 14:34:56)

In reply to a post by MrSaffron:

Did you set the RT-N66U up to provide the authentication details via a PPPoE session on its WAN port?

You are not alone it seems.

http://forum.tp-link.com/showthread.php?2504-Td-8817...

Well I have tried, but there's a problem in that the RT-N66U requires a username and password for the ADSL connection, however Be* users do not require one.

Other people have claimed success so either they are big fibbers or I'm missing something simple.

In reply to a post by Cheule:

Other people have claimed success so either they are big fibbers or I'm missing something simple.

Router specs say:

WAN Connection Type
Internet connection type : Automatic IP, Static IP, PPPoE(MPPE supported), PPTP, L2TP
Multicast Proxy support

"Automatic IP, Static IP" would cover BE.

In reply to a post by Oliver341:

In reply to a post by Cheule:

Other people have claimed success so either they are big fibbers or I'm missing something simple.

Router specs say:

WAN Connection Type
Internet connection type : Automatic IP, Static IP, PPPoE(MPPE supported), PPTP, L2TP
Multicast Proxy support

"Automatic IP, Static IP" would cover BE.

Static IP is the only option I have got the 8817 to connect to the internet with and route traffic. I cannot seem to replicate this on the RT-N66U however. It says connected with an IP of 192.168.1.101 (given by the 8817) but no traffic.