Setting Up TP-Link TL-WR841N as AP Client with Gargoyle Firmware: Connecting to WR1043ND Router

Hello. I am trying to set up this router in Client mode, but I can not get internet connection, or even locally.
The main TP-Link TL-WR1043ND router provides internet for the whole house and I am also trying to connect to it. The IP of the main router is 192.168.0.1.
In the additional (841) I have set wireless / bridge and there Bridge IP 192.168.0.2, mask 255.255.255.0, AP / Gateway IP 192.168.0.1, wan disabled, DNS the same as gateway.
Then connect via client bridge, reapater disabled, operation mode B + G + N, channel width 20MHz, transmit power max, SSID to join , wireless channel 9, encryption WPA2-AES, password

Despite my trying, I could not connect. I am interested in a functional ethernet port for internet and one for connecting a nc + decoder in a multiroom. Can someone tell me something more? Is the router for scrap?

On trial, disable encryption on the main router and try to connect.

Adds a screenshot.

I have almost identical bridge settings on my 841, gargoyle 1.9.1
except for the IP bridge in brackets, it says "(must be outside ap subnet)"

firmware version?

Added after 4 [minutes]:

For my router: 192.168.50.1 a bridge ip 192.168.51.25
I can not get to the router after 192.168.51.25 even if I set the computer ip at 192.168.51.222

when I get IP from dhcp from 192.168.50.1 (via bridge) then I enter the bridga after IP which bridge got from dhcp 192.168.50.1 (eg 192.168.50.202)

Added after 2 [minutes]:

here he writes what is to be "insde" or "outside" in the IP bridge.

Added after 23 [minutes]:

However, I can enter the bridge after 192.168.51.25.

Added after 1 [minutes]:

tracert looks interesting, 2x IP from the same network

[code:1:306d1d3416]
$ tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

1

I returned to the TP-Link firmware wr841nv9_en_3_16_9_up (151030). Because I could not connect back to the router after changing IP from 192.168.0.2 to 192.168.1.1 (I wanted to see if it works like that). After the change I can not connect to the Connection tab, others work, for example, status, update, etc.

I connected via WDS on the main and secondary router. For now it looks like the internet is working and the local connection is, I will wait if I lose the decoder permissions or not.

Unfortunately, WDS is not a good solution because running this mode results in the inability to connect via Wi-Fi from the main router.

I wonder why I can not enter the Connection tab when others are working, even after the device reset.

Firmware version 1.7.0

upload gargoyle 1.9.1

Added after 1 [minutes]:

WDS should not exclude the AP mode, the whole idea of WDS, always with WDS is AP, otherwise the WDS idea would be different.

I've downloaded 1.9.1 but I still can not stick through 192.168.1.1, and through http://192.168.1.1/overview.sh I can check the status of the router. The attempt to go to Connection generates http://192.168.1.1:4321/ and I can not connect.

After uploading the new firmware, restore the factory settings and reconfigure.

If you have 841 downloaded Gargoyle, set it to dhcp wireless and change the LAN address to 192.168.2.1.