reverse NAT

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

reverse NAT

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
reverse NAT
reverse NAT
2020-09-21 11:45:57 - last edited 2021-04-18 10:55:26
Model: TL-R600VPN  
Hardware Version: V4
Firmware Version: 4.0.4 Build 20200313 Rel.41831

I have a new R600VPN and two Netgear cable modems. The management ports of the cable modems are hard coded to the ip address of 192.168.0.100. Each are connected to a WAN port and all normal outbound and inbound traffic works as expected. The issue is access to the modem management port. If I only have one of the ports open, or create a static route to the address via one of the WAN ports, the mangement site opens and works works fine. Since I only need access to it intermitantly, this is an ok solution, but I was hoping to do better. My only idea so far is to setup up a "reverse" NAT to publish a local LAN address for the port in question. Unfortunatly I cant figure out how to do that, or how to determine if it actually would work. 

 

any ideas would be appreciated

  0      
  0      
#1
Options
1 Reply
Re:reverse NAT
2020-09-23 08:01:24 - last edited 2021-04-18 10:55:26

@robertg 

 

I have a new R600VPN and two Netgear cable modems. The management ports of the cable modems are hard coded to the ip address of 192.168.0.100. Each are connected to a WAN port and all normal outbound and inbound traffic works as expected. The issue is access to the modem management port. If I only have one of the ports open, or create a static route to the address via one of the WAN ports, the mangement site opens and works works fine.

 

Perhaps the Policy Routing function could help, set policy routing rule to make the IP 192.168.0.100 go to WAN1 or WAN2 based on the management ports.

 

https://www.tp-link.com/en/support/faq/2134/

  0  
  0  
#2
Options