TD-W8980 -- Error creating Static Routes

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

TD-W8980 -- Error creating Static Routes

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TD-W8980 -- Error creating Static Routes
TD-W8980 -- Error creating Static Routes
2018-07-25 02:51:39
Model :

Hardware Version :

Firmware Version :

ISP :

Firmware Version:0.6.0 0.6 v000e.0 Build 130304 Rel.38108n
[B]Hardware Version:TD-W8980 v1 00000000

Problem is really basic: My 8980 is connected to an L3 switch that is serving multiple networks. The link between the L3 switch and the 8980 is a single, L3 link: 8980(192.168.2.1) <-> Switch port (192.168.2.2).

The problem is I need to set a static route on the 8980 that basically says "To get to network 10.63.2.0 you need to forward all traffic to 192.168.2.1". According to the 8980 manual, this is the proper setup. Here is the manual:




[/B]
[B]Here is mine:
[/B] [B]





What I get is this error:

[/B]Error code: 5108
Gateway must be in the same subnet with interface IP address. Please input another one.

Anyone on the forum have an idea as to why the 8980 does not appear to work according to the manual?

Thanks

<<<<>>>>>

The issue is the 8980 cannot create a static route for anything other than the DEFAULT LAN interface, even if you have another LAN interface created in a separate group. Any TP person know about this limitation -- and why in the world a static route would be tied this way? Makes no sense from a router standpoint.
  0      
  0      
#1
Options
2 Reply
Re:TD-W8980 -- Error creating Static Routes
2018-07-27 08:07:31
It seems odd. Will it be a firmware limitation? Have you tried configuring it directly to the WAN interface?
  0  
  0  
#2
Options
Re:TD-W8980 -- Error creating Static Routes
2018-07-29 17:52:21
Since the static route needs to point to the LAN side -- no, I have not tried the WAN. And I suspect it is a firmware issue -- and since there is no other response from TP-Link I assume its not really an issue they care about.
  0  
  0  
#3
Options