It's normal behaviour for common residential routers to have NAT enabled on the "internet socket". This means that RouterB clients are NATed when crossing to "RouterA" side. This means that RouterA doesn't see the client's address, it sees the RouterB address for all the RouterB's clients. And this is why RouterA's clients can't connect to RouterB's clients: RouterA clients can't distinguish between one RouterB's client and another one.

You have 2 options here:

1. routed network (aka layer3 addressing): disable NAT on RouterB's "internet socket".

2. switched network (aka layer2 addressing): place both routers on the same network (using different addresses) and connect the routers using lan sockets instead of the internet one.

Other details will probably need to be fixed in both cases. Examples:

a) static routes in the routed network: you might have to add a static route on RouterA, in order to tell that the 192.168.0.0/24 network is at RouterB's IP address.

b) DHCP servers in the switched network: there can be one only (or can be two but you must make those two aware of the other one, and decide which one is the master and which one is the slave; usually this can't be done on consumer routers). So you must disable one of the DHCP servers on one of the routers's lan side.

In order to have a working setup, you must decide what kind of network you need (routed or switched?) and usually security plays a major role in this decision. In a routed network you can ask the router to deny some activities in order to protect some of the clients from others. In a switched network the router have less control on client-to-client communications because they are in the same collision domain... they communicate directly without using the router as a middle-man.

We can't help you more than this without having more details about your network equipment and your needs.

In the while have a look at OpenWrt's forum, if you can manage to place OpenWrt on your router, you'll be able to fully configure your device and make complex network configurations. Otherwise your chances are limited by the vendor software; in other words you probably can't make a routed network.

It's normal behaviour for common residential routers to have NAT enabled on the "internet socket". This means that RouterB clients are NATed when crossing to "RouterA" side. This means that RouterA doesn't see the client's address, it sees the RouterB address for all the RouterB's clients. And this is why RouterA's clients can't connect to RouterB's clients: RouterA clients can't distinguish between one RouterB's client and another one.

You have 2 options here:

1. routed network (aka layer3 addressing): disable NAT on RouterB's "internet socket".

2. switched network (aka layer2 addressing): place both routers on the same network (using different addresses) and connect the routers using lan sockets instead of the internet one.

Other details will probably need to be fixed in both cases. Examples:

a) static routes in the routed network: you might have to add a static route on RouterA, in order to tell that the 192.168.0.0/24 network is at RouterB's IP address.

b) DHCP servers in the switched network: there can be one only (or can be two but you must make those two aware of the other one, and decide which one is the master and which one is the slave; usually this can't be done on consumer routers). So you must disable one of the DHCP servers on one of the routers's lan side.

In order to have a working setup, you must decide what kind of network you need (routed or switched?) and usually security plays a major role in this decision. In a routed network you can ask the router to deny some activities in order to protect some of the clients from others. In a switched network the router have less control on client-to-client communications because they are in the same collision domain... they communicate directly without using the router as a middle-man.

We can't help you more than this without having more details about your network equipment and your needs.

EDIT: If you can manage to place OpenWrt on your router, you'll be able to fully configure your device and make complex network configurations. Otherwise your chances are limited by the vendor software. BTW, it looks like your TP-LINK is supported by OpenWrt.

It's normal behaviour for common residential routers to have NAT enabled on the "internet socket". This means that RouterB clients are NATed when crossing to "RouterA" side. This means that RouterA doesn't see the client's address, it sees the RouterB address for all the RouterB's clients. And this is why RouterA's clients can't connect to RouterB's clients: RouterA clients can't distinguish between one RouterB's client and another one.

You have 2 options here:

1. routed network (aka layer3 addressing): disable NAT on RouterB's "internet socket".

2. switched network (aka layer2 addressing): place both routers on the same network (using different addresses) and connect the routers using lan sockets instead of the internet one.

Other details will probably need to be fixed in both cases. Examples:

a) static routes in the routed network: you might have to add a static route on RouterA, in order to tell that the 192.168.0.0/24 network is at RouterB's IP address.

b) DHCP servers in the switched network: there can be one only (or can be two but you must make those two aware of the other one, and decide which one is the master and which one is the slave; usually this can't be done on consumer routers). So you must disable one of the DHCP servers on one of the routers's lan side.

In order to have a working setup, you must decide what kind of network you need (routed or switched?) and usually security plays a major role in this decision. In a routed network you can ask the router to deny some activities in order to protect some of the clients from others. In a switched network the router have less control on client-to-client communications because they are in the same collision domain... they communicate directly without using the router as a middle-man.

We can't help you more than this without having more details about your network equipment and your needs.

It's normal behaviour for common residential routers to have NAT enabled on the "internet socket". This means that RouterB clients are NATed when crossing to "RouterA" side. This means that RouterA doesn't see the client's address, it sees the RouterB address for all the RouterB's clients. And this is why RouterA's clients can't connect to RouterB's clients: RouterA clients can't distinguish between one RouterB's client and another one.

You have 2 options here:

1. routed network (aka layer3 addressing): disable NAT on RouterB's "internet socket".

2. switched network (aka layer2 addressing): place both routers on the same network (using different addresses) and connect the routers using lan sockets instead of the internet one.

Other details will probably need to be fixed in both cases. Examples:

a) static routes in the routed network: you might have to add a static route on RouterA, in order to tell that the 192.168.0.0/24 network is at RouterB's IP address.

b) DHCP servers in the switched network: there can be one only (or can be two but you must make those two aware of the other one, and decide which one is the master and which one is the slave; usually this can't be done on consumer routers). So you must disable one of the DHCP servers on one of the routers's lan side.

In order to have a working setup, you must decide what kind of network you need (routed or switched?) and usually security plays a major role in this decision. In a routed network you can ask the router to deny some activities in order to protect some of the clients from others. In a switched network the router have less control on client-to-client communications because they are in the same collision domain... they communicate directly without using the router as a middle-man.

We can't help you more than this without having more details about your network equipment and your needs.

In the while have a look at OpenWrt's forum, if you can manage to place OpenWrt on your router, you'll be able to fully configure your device and make complex network configurations. Otherwise your chances are limited by the vendor software; in other words you probably can't make a routed network.