Excitedly connected the nas network cable to the network port on the wall, but there was no response. I went to the weak electric well box to check and found that there was no wiring. Net, so there is such a journal, for reference for everyone in a similar situation.
Home network environment:
Telecom optical modem (192.168.1.1) - electric well box router (192.168.8.1)
Tplink router (192.168.1.1) - lan port - NAS
Now it is the combination of the above two, the requirement is to bridge the Tplink router (secondary router) into the local area network of the electric well box router (primary router), and access the NAS through the electric well box router network.
First turn on the Tplink router and connect the computer to the background, modify the lan port ip to 192.168.2.1. The reason for this modification is that the bridge router cannot be in the same network segment as the main router during the WDS wireless bridging process, so it cannot be changed to 192.168.8.2 in one step. But if you still keep 192.168.1.1, it is easy to coincide with the background address of Telecom Optical Modem in the switching network environment test.
Next, click Advanced Settings > Wireless Settings > WDS Wireless Bridge, click Next in WDS Wireless Bridge to start the setup, and set a name for the secondary router that is different from the main router. After the operation is completed, observe the WDS status in the upper right corner. If it is connected, it means that the WDS bridge is successful.
Go to the lan port, set the ip to the address under the network segment of the main router, here use 192.168.8.2
and turn off the DHCP service.
Go to the main router, narrow down the DHCP start and end address range, and the start address must include the secondary router address.
At this point, you can directly access the background of the secondary router through the primary router.
Obtain the nas address and enter the secondary router to fix the nas address.
At this time, the nas can be accessed normally
. Modify the local ip address in the frp configuration file, start docker, and successfully start intranet penetration
