HI Peplink Support Team
When building SpeedFusionVPN from InControl2, there is no problem, but when configuring Send All Traffic from WebAdmin>Advanced>SpeedFusionVPN, the button is grayed out even though the VPN is already built. This is not a problem when building a VPN.
This has been a frequent query in Community, tickets, etc., but has been left unaddressed since FW8.3.0 was released.
Recently, your engineers told us that Send All Traffic is deprecated, but if that is the case, why is it left in place?
I think there needs to be a way to do away with the setting item itself, or recommend that it be set in the OutBound Policy.
BR
Sato
2 Likes
Agree
Would be nice to have this part moved to outbound policies, and ideally have a feature that says forward all traffic to <SFC / VPN Profile Name>
Or if you wish to keep this button under SFC, then it should create an outbound policy as to make it more transparrent.
What would be very useful to is to have each VLAN / Subnet as a preconfigured device in outbound policy creation.
3 Likes
@CASO.Corp, if the SpeedFusion is managed by InControl2, please enable “Send All Traffic” from InControl2 too. Below is the setting from InControl2.
It is expected the SpeedFusion feature is greyed out from local web admin as they are managed by InControl2. This is not a bug or “Send All Traffic” has been deprecated.
Hope this helps.
1 Like
Some customers can build SF VPNs from WebAdmin or, if the router is not PrimeCare, from WebAdmin without renewing the license.
Even then, I thought “Send All Traffic” was grayed out in WebAdmin>Advance>SpeedFusionVPN.
Am I correct in thinking that the “Send All Traffic” in the above section is grayed out unless InControl2 management is turned off on IC2?
As long as SpeedFusion is managed by InControl2, the SpeedFusion settings at Advanced > SpeedFusion will be greyed out or not configurable.
You have ticket #23120008 and ask a similar question. I suggest you follow up in the ticket as we have more visibility there.
Thanks.
1 Like
