Out of your description of the state of affairs, your ISP has supplied you one community (seemingly 10.11.206.36/30) with 10.11.206.38 as your router (host) IP deal with, 10.11.206.37 as gateway, and subnet masks 255.255.255.252 and that’s the entire usable community.
They’ve then routed a further community of IP addresses (10.11.223.193 – 10.11.223.206 which is more likely to really be 10.11.223.192/28) to your assigned host IP deal with (10.11.206.38). This implies their community is configured to ship any visitors on your second community of IP addresses to your host IP and to imagine that your gadget will know what to do with visitors destined to any IP within the second community.
This implies your main router must be configured to ‘route’ visitors for these IP addresses to a different gadget or units. You possibly can configure your networks between your main router and extra routers as you need. You should use small transit networks on hyperlinks between the routers (a /31 or /30 community to accommodate a single point-to-point hyperlink between the routers) or just subnet the given secondary community to immediately join the extra routers (as described beneath). The way you do that on a client/small workplace router like that TP-Hyperlink is as much as you to find, it is probably not doable.
The ISP was seemingly assuming that by telling you that you just want a ‘Twin WAN’ router, you’ll get one thing extra succesful that may not solely do Twin WAN but in addition the required routing or firewalling wanted to make use of these extra IP addresses. With the precise tools, your setup is pretty trivial however I am undecided it’s doable with the tools you’ve got.
It’s essential to make your fundamental router act as a form of ‘hub’ router to attach and route visitors to the extra routers you point out. The primary WAN configuration of the first router would stay unchanged however it is advisable disable NAT for visitors being forwareded to the opposite routers, in any other case they may have their visitors mangled/modified by the first router. You additionally have to setup the ‘transit’ hyperlinks between the first router and the extra ones. Because you solely have the small secondary community, we are able to assume that the extra routers will carry out NAT for his or her LAN units so there is no such thing as a have to do any extra static or dynamic route configuration past the configuration of the interfaces on the first router.
The first router wants a WAN interface linked to the ISP as you’ve got now (10.11.206.38).
The first router then must have NAT disabled, not less than for the interfaces and/or visitors for the community you need to setup.
You then have to configure 4 extra interfaces on the first router, every with a /30 community. The primary extra interface would have 10.11.223.193 and subnet masks 255.255.255.252, second interface would have IP deal with 10.11.223.197 and subnet masks 255.255.255.252, third interface would have IP deal with 10.11.223.201 and subnet masks 255.255.255.252, interface would have IP deal with 10.11.223.205 and subnet masks 255.255.255.252.
The 4 secondary routers would use IP addresses 10.11.223.194, 10.11.223.198, 10.11.223.202, and 10.11.223.206 for his or her WAN interfaces.
If the primary router can not present 4 extra routed interfaces, you might want to easily configure the LAN interface as 10.11.223.193 with subnet masks 255.255.255.240 and join all of the 4 routers as LAN units. Disable the firewall and NAT options on the primary router and hope that issues work. The 4 secondary routers might use IP addresses 10.11.223.194-206 with the identical 255.255.255.240 subnet masks. The draw back to this design is much less segmentation of the networks which can or is probably not desireable relying in your wants.