Please simplify SpeedFusion Event logging

Product Discussion Feature Requests
1

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.

14 Likes
2

+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.

3 Likes
3

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.

3 Likes
4

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 :slight_smile:

1 Like
5

+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.

2 Likes
6

This is definitely a painful thing for me too. I’ll work on it soon.

8 Likes
7

Would be cool in general if there is kind of a sanity check done automatically by the router.

Like:

  • Internet reachable via different methods
  • Speedfusion Remote-Host check if its pingable

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.

2 Likes
9

Would be great to see the different steps the speedfusion takes to try and establish the connection.

  • remote site can be reached by icmp
  • Incomming speedfusion connection from 43.134.21.45
  • handshake using port 32015
  • tried to establish data on port 4500 but failed etc
  • established data on port 4501
  • failed to establish connection using wan 2

These are just some suggestions. But I feel I am missing a lot of details when trying to troubleshoot a connection failure. I find myself doing a lot of try and error to get the connection setup.

2 Likes
10

Awesome! Thankyou Steve. Excited to see some updates.

1 Like
11

+1 It would be very helpful to have more detailed logs !