SpeedFusion Event logging is a complete mess. All of the TLS / cipher negotiation events are of no value to me.
Can we add a button that just shows the events where tunnels and subtunnels connect and disconnect? That’s all I care about when fault finding.
+1 From here.
At least add more filters to Speedfusion then so we can get exactly what we need, and not as Martin points out all the negotiation events.
Additionally uncheck the speedfusion event log as default.
@MartinLangmaid Thanks for bringing up this issue , I don’t know why we let them get away with this for so long.
@Steve Any comments on how this can be simplified.
The biggest issue we want to see in the logs is “Why was the tunnel not established?” Most of the time, for our customers, it is due to a subnet clash, though you don’t get that in the logs; you have to go digging through all the devices in that SpeedFusion setup.
So a plus one (+1) for improving the logging, please 
+1 for me as well, would be very helpful if event logging was more simplified or at least the connect/disconnect event descriptions more user friendly.
This is definitely a painful thing for me too. I’ll work on it soon.
Would be cool in general if there is kind of a sanity check done automatically by the router.
Like:
We use PepLink Router with our mobile event setup. Most of the time the Speedfusion connection is not working via local WAN/LAN connections is that IPs must be whitlisted from the local admin or that for example UDP connections are blocked in general. Or, that the IP ranges are somehow clashing with each other.
So kind of a simple Status output / logging would be cool to quickly identify the most common issues.