TP-Link TL-WR1043ND (Router) + Fritz!Box 2170 (Modem)

Report wireless and/or network connectivity problems in this forum.

Moderator: Moderators

Post Reply
basti92
Posts: 4
Joined: Mon Nov 12, 2012 7:20 pm

TP-Link TL-WR1043ND (Router) + Fritz!Box 2170 (Modem)

Post by basti92 »

Hello!

I already tried to get online for severall hours now..

My situation:

I want to use my TP-Link TL-WR1043ND as a router and my Fritz!Box 2170 as an adsl modem. I have to mention that the FB ran for severall years without problems and same ISP-Login details like now. My ISP uses PPPoE.

I bought an TP-Link TL-WR1043ND and installed the newest Gargoyle firmware by following this guide: Install Gargoyle on TP-Link TL-WR1043ND

Very easy, very successfull.

I reseted my Fritz!Box 2170 and installed the newest AVM firmware (51.04.57). I tried for severall hours and searched this forum: I wasnt able to establish an internet/WAN connection.

I found this guide: Accessing your adsl modem in bridge mode. So I changed to bridge mode, enabled dhcp on the FB gave a static ip 192.168.2.1 to it (router uses 192.168.1.1). Both in 255.255.255.0 subnets.

I wasnt able to understand why I have to enable DHCP on the FB? I'd like to use the TL DHCP if possible.

Hardware and cables are connected like this:

INTERNET -> Fritz!Box (ADSL Modem) -> LAN -> TL-WR1043ND (WAN Port).

This is the config of my TP-Link TL-WR1043ND:

Image
Image
Image
Image

pbix
Developer
Posts: 1373
Joined: Fri Aug 21, 2009 5:09 pm

Re: TP-Link TL-WR1043ND (Router) + Fritz!Box 2170 (Modem)

Post by pbix »

What version of Gargoyle are you using?

v1.5.7 has a bug which causes this.

Please use v1.5.8.
Linksys WRT1900ACv2
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM

basti92
Posts: 4
Joined: Mon Nov 12, 2012 7:20 pm

Re: TP-Link TL-WR1043ND (Router) + Fritz!Box 2170 (Modem)

Post by basti92 »

I am using 1.5.8 as shown in the configuration menu.

First I tried with 1.4.x because this was labeled "stable". Then I changed to 1.5.8 because of my connection problem - which exists also with the new version.

Post Reply