Routing/natting for multiple subnets

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

Routing/natting for multiple subnets

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Routing/natting for multiple subnets
Routing/natting for multiple subnets
2020-07-22 15:27:10
Model: Archer A9  
Hardware Version: V6
Firmware Version: 1.0.4 Build 20190522 rel.66382(5553)

 

My home configuration.

 

Internal LAN 10.10.0.0/24 -> FortiGate -> Internal WAN/LAN 172.16.10.0/24 ->TPLink A9 AC1900-> Public IP space (Xfinity) Cable modem in bridge mode-> Intenet

 

I want to be able to route the 10.10.0.0.network to the intenet without needing to a rule that requires NAT on the Fortigate.

 

Static route exists on TPLink for 10.10.0.0/24 sending the WAN interface of Fortigate 172.16.10.2

If I enable NAT on the Fortigate and NAT to the WAN IP of the Fortigate I can ping the world and get responses

If I disable NAT on the Fortigate and do not nat (source IP remains 10.10.0.0 IP I can only ping to the Internal inteface of the TPLink 172.16.10.1

 

Can TPLink perform NAT for IPs that are not members of its own LAN?   

 

Been doing networking for a long time...what am I missing?  Is this a limitation of TPLink?

 

  0      
  0      
#1
Options
1 Reply
Re:Routing/natting for multiple subnets
2020-07-23 22:57:29

@bobgnt 

 

Sounds like you would need a business router in order to do Multi-NAT like this article: https://www.tp-link.com/us/support/faq/887/

 

Especially how if there is no gateway (No NAT) for the router to point to as far as the gateway.

  0  
  0  
#2
Options