Hi @DaveMcDave 

Thanks for posting in our business forum.

DaveMcDave wrote

Morning!

 

Me again.

 

Thought I would come back on this as there's been a lot of discussion around this, and what staggers me at the moment is the attitude of "Well no one else does it (even though they do), so why should we?".

 

Surely the mindset of "Let's look at implementing this much requested feature for our growing base of customers, and get a step ahead of our competition and prove to them that we are serious about our business products", would work much better than "Nah, cba tbh".

 

Just a thought.........

There are many more features and RFC grows. So we'd keep every feature/protocol integrated?

This was brought to the dev's attention as the label says. We don't have specific details or an ETA for this implementation.

Not until the EdgarFonseca chimed in and shared his experience with Draytek. No one else provided a concrete and helpful competitor's move. Others' replies in a way that "I need it".

BTW, @EdgarFonseca, thanks for the information. I am convinced that this might be something the dev can try.

Pretty clear in the reply that we need some information on the use case, scenario, size of your network, and other vendors' implementation. And it is the information we need for an evaluation and a report (for the dev and PM, they need it). Getting to know the information of a feature request is a common ground I had with the dev in the last phone call discussion on some feature requests.

As mentioned above, it is clear that this should be something that needs to be done in the future and it has been brought to the dev's attention. (This is not a guarantee if there is a hardware limitation. Simply based on the use case and feedback. It is supposed to be done.)

I will wait for the message from the dev if they have a plan or a roadmap about this and notify you and others about this feature. Will not comment on this as it is enough for the moment.

Hi @seki1975 

seki1975 wrote

  @Clive_A 

 

What about here? 

Model: Vigor3910, Vigor2962, firmware version 4.3.2 or later; Other Vigor models support it from version 4.4.2

I can't put a link here to a beautiful manual that is completely simple to use.

Drytek_Vigor_manual_2FA

 

 

 

 

 

I have searched about it. Noted. Thanks for sharing this information.