Question WDS Bridging TP-LINK

[sasalakic99]

Hey guys! I am having a problem with the Router I tried to configure today. It is an TP-LINK 740N router which I had lying around and I am trying to configure WDS Bridging on it. I never thought that this cheap router is compatible with WDS bridging but today when I was at my friends house he showed me that he basically configured it as a repeater. Anyway, what I have done so far:
I changed the LAN IP from 192.168.0.1 to 192.168.1.120 so the subnet is the same as the LAN IP of the main router. (192.168.1.1)
I disabled the DHCP for the TP LINK router.
I scanned for WiFi networks and connected it to my main routers network
WDS status changes from Scan.. to Init... and freezes there.
I didn't mess with the DNS settings, I tried to restart both the main rooter and the TP Link multiple times, still no charm. I also tried multiple combinations to change LAN IP, with different and same subnet mask, and different ranges still no luck,
Does anyone have exeperience with this type of routers? And if so can anyone help me with this problem?
Thanks in advance!

 

[Ralston18]

Configuration being (edit and correct as necessary):

ISP ----->[WAN] DHCP/Main Router(Make & model?) ~~~ Wireless ~~~> TP-LINK740N

Do verify that the subnet mask on the TP-LINK740N router is indeed configured to match the main router. (Both should be 255.255.255.0)

The following link may prove helpful:

https://www.tp-link.com/lk/support/faq/615/

Double check all connections and configurations.

On a working network computer run, if necessary, "ipconfig /all" via the Command Prompt and post the results.

You should be able to copy and paste the results without needing to retype it all.

 

[sasalakic99]

Hello and thanks for the reply. Yeah the configuration is correct, the model of the main routeris ZTE VDSL2 H168 V3.1, its an ADSL modem. Unfortinately the options in the setup of 740N are not the same as 710N. And, also these two routers worked in bridge configuration before, when I had a seperate game server PC. But they were connected through network cable but I remmember having a tough time configuring it to work.
And this is the current IP config, with PC connected to main router.


Host Name . . . . . . . . . . . . : DESKTOP-MMH4TL2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : A8-A1-59-47-5F-F9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d27:e744:f6f0:696c%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : četvrtak, 06. oktobar 2022. 13:53:45
Lease Expires . . . . . . . . . . : petak, 07. oktobar 2022. 13:53:45
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 111714649
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-9E-DE-F4-A8-A1-59-47-5F-F9
DNS Servers . . . . . . . . . . . : fe80::1%9
192.168.1.1
fe80::1%9
NetBIOS over Tcpip. . . . . . . . : Enabled

 

[sasalakic99]

P.S. This is IP Config when the PC is connected to TP Link router, after I tried to configure it:

Host Name . . . . . . . . . . . . : DESKTOP-MMH4TL2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : A8-A1-59-47-5F-F9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d27:e744:f6f0:696c%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : četvrtak, 06. oktobar 2022. 18:15:51
Lease Expires . . . . . . . . . . : četvrtak, 06. oktobar 2022. 20:15:51
Default Gateway . . . . . . . . . : 192.168.1.120
DHCP Server . . . . . . . . . . . : 192.168.1.120
DHCPv6 IAID . . . . . . . . . . . : 111714649
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-9E-DE-F4-A8-A1-59-47-5F-F9
DNS Servers . . . . . . . . . . . : 192.168.1.120
NetBIOS over Tcpip. . . . . . . . : Enabled

 

[bill001g]

To start with you have the tplink configured wrong. You have the DHCP server activated.

Most times this is disabled by default when you run it as repeater. Not sure the repeater stuff on older routers was very flaky. Although every one uses WDS to do this WDS is not actually part of the official standard.

You also have to make sure that your main ZTE router also supports WDS. WDS is considered a security exposure and is disabled in many router. Many router you must also put in the mac address of the remote router you want to allow to connect. Pretty much the problem is anyone who knows the wifi password can setup a unsecured repeater using WDS.

 

[sasalakic99]

Hey guys thank you all for the reply!
I solved the problem, i had to choose proper channel for my router, it wasnt avilable to connect whet it was set on automatic.