Accessing router from another router/modem

[Abhishek_8R]

I have a wifi router connected to my wifi modem through a LAN cable.I have designated a static ip to the router inside the modem configuration.Therefore the IPs are: Modem:192.168.1.1 Router:192.168.1.2(external IP as assigned by modem),192.168.0.1(Internal IP) Both have the same subnet mask as 255.255.255.0

DHCP is enabled both on router and modem but with different subnets.

The main PC is connected to my modem and the rest of the home network connected to my router.

->The problem is I can't access my router(i.e configuration window & router's clients) through my main PC,neither by 192.168.1.2 or nor 192.168.0.1 or any router's client address.

I can access access my modem's config window from the clients of router but not the other way around.

The following may help you understand my setup:

To be exact,I am using an ADSL modem but it can be configured to 3 modes:
1.ADSL Modem Router Mode
2.3G Router Mode
3.Wireless Router Mode i.e One of the LAN port can be configured to be used as WAN port
I am using it in the Wireless Router Mode.
The main task I am trying to accomplish is to access config window of router from modem's clients and share files b/w the main computer connected to the modem and 2nd router's clients i.e Raspberry pi,other machines etc.

P.S I can access/share my files fine in LAN to LAN configuration and disabling DHCP on second router,But still can't access config window of router through any of the clients(whether connected to modem or router).Isn't this using router as a switch?

**Please note** that I want to share files and access config windows of both modem and router in LAN to WAN configuration.

 

[joex444]

Your main PC is seen as going through the WAN port of the TP-Link so you'll need to enable external configuration access in order to open its configuration page by a non-client.

 

[joex444]

If you want to use the TP-Link router as a switch, you would disable DHCP on it, and plug the cable from the modem into one of the LAN ports not the WAN port. The clients of the TP-Link device would then acquire 192.168.1.XXX addresses.

The way that you have it set up *should* allow your Raspberry Pi to see the main PC since it is a request from a 192.168.0.XXX device to a 192.168.1.XXX device with a hop from the TP-Link to the modem.