This discussion thread has been very enlightening, it very clearly illustrates that while the support staff responding online here are well intentioned, theyre also so obviously disconnected from the product engineers and management mechanisms to make meaningful change or pass on valuable, easily actioned feedback. this "static route" feature isnt even a feature y'all. Everyone one here should be peeved right off and feel duped. I am a senior systems architect as well as a network engineer. I've worked for IBM and Microsoft as my first 2 jobs in my career and have going on 20 years of experience in this industry. Let me tell you why this is a rip off and you're all being duped. These deco devices, like pretty much every network device out there, especially ones that do routing/firewalling are all essentially Arm or mips based SBCs (single board computers) running Linux under the hood. They're not much different then a raspberry pi except that a PI could blow these puny pieces of trash out the water in performance and PIs are cheaper to buy as well . switches are a little different story then routers/firewalls/wireless access points, but many do run Linux under the hood, atleast for the management interface or if the switch is a web/smart or managed layer 3 switch it will almost certainly be running Linux under the hood to use its universally proven and secure TCP/IP stack. That stack has has IP routing capabilities since it's very first revision. The ability to define a static route DOES exist within them. Another part of the stack these devices uses is the TCP and IP protocol's to provide the user a managment interface. Usually over HTTP/HTTPS but sometimes over a text based Telnet/ssh session. All thst it woukd take in the most frequently used scenario of an HTTP admin interface, is to create a new file containing HTML and possibly CGI-BIN link or using PHP/python/Perl. It would simply need to have a few lines of copy to output to a new admin page dedicated to static routing, or add a small addition onto another admin interface page. In its most simplest form, it would need to include code similar to:

Static Routes

Existing Static Routes:

%STATICROUTES%

New IP Static Route

Please enter a new static route in the proper format:

Clicking Submit will apply this new static route to the routing table immediately.

where the scripting engine would make a native IP API call to get the current static routing table and return it in text format to the string variable mentioned above %STATICROUTES%. the default gateway specified on the wan interface of these devices is actually a form of static route. The route is: 0.0.0.0/0 gw 10.0.0.1 10.0.0.123 Where 10.0.0.123 is the WAN ip assigned by the ISP and 10.0.0.1 is the ISPs router or the same ip entered in the Default Gateway field of the WAN interface. So in conclusion, here is almost all the necessary code but a few lines to create a new Static route interface page or could be pasted into an existing interface page. The functionality of it is already built into the Linux OS so we are really just being denied access to one of the oldest, most core fundamental parts of the IP protocol that is built into every single Linux based device, without exception. TP Link... time to do better. Ive already replaced my Decos at my house with Ubiquity and my office with Mikrotik . Y'all should follow suite to . Mikrotik is probably the most innovative, affordable network hardware company ive seen in my 20 year of experience. I highly recommmend them!