@GRL 

Hi, have you tested SD-WAN now? I'm still waiting for the firmware for the ER707-M2 to test, but I'm very excited about how it will works. :-)

Hi @GRL 

Thanks for posting in our business forum.

Regarding the materials like FAQ and any guides, or datasheets, please send the request to the support team.

I am not responsible for writing like guides or datasheets.

All the guides I wrote are from my experience and point of view. Or I copied one and modified it for ease of understanding. The writing team is responsible for all the guides on the official website and new features. The User Guide, Installation Guide, and the product introduction.

Forum team which I belong to does not play a key role in this process. I only submit a request like yours and do not have a schedule on the guides for when to come.

Hi @GRL 

Thanks for posting in our business forum.

GRL wrote

  @Clive_A 

 

I wasnt asking you to write a guide.  I was requesting a guide form whomever makes them.  Then i added some more questions - sensible ones - on what is currently a completely undocumented feature.

 

Its not up to us end users to necessarily experiment, or break our networks - especially with a feature like this that could potentially break connectivity with our remote networks (that may be in hard to get access to places)

I appreciate that there is a timescale, and that you have submitted the request.

Dont read my extra questions as any sort of "demand" that the information be given now.....

 

HOWEVER

 

According to the Controller firmware update feature - the fully adapted ER7206 v2 firmware is now in "stable" general release channel.  This means that as far as TP-Link is concerned, this feature is now "ready".  The controller is sure to be very close behind.  This means you have features out there, on general release, that are completely undocumented - even to the point that the "help icon" is still missing in the controller setup for these......

I know. Don't worry. Just let you know that my writing and the writing team are different. I am just doing way more than I am supposed to do to release a guide before them.

Sometimes, I don't have an idea of what scenario people might use a feature. Or my environment, the test bench I built cannot produce a proper guide for them.

TBH, most guides I have written so far are based on the frequent topics on what people feedback to me.

And explain the current status of how things get done. The doc update and the guide are always lagging behind the new features.

I have sent this to the dev and see if they can get a simple guide before the writing team begins to do it. Not sure if I can give you a promising answer. And the writing team finishes and audits their work by order. It would be more convenient to send the request to the support team. Just FYI.