Feature #12807
closedClear Active Secondary WAN Connections
0%
Description
Hello There,
There are many people who may have a secondary WAN connection that is utilized on a wireless pay as go service Turbo stick.
That means when the primary WAN connection goes down and the secondary WAN connection now becomes active, the data being used is billed accordingly for the secondary WAN connection. The issue comes when the primary WAN now becomes active and the secondary WAN then becomes as a standby state.
Most often than not, there are still active sessions on the secondary WAN which means customers like myself are still being billed for data being used on the line. This issue happens if you are using an application that uses persistence TCP and or UDP connections and the failover WAN connections occurred.
To ensure, that the data used on the line is actually needed and billed accurately, I have compiled and tested the bash script which checks to see if the primary WAN is online and then checks to see if there are active sessions on the secondary WAN. If it finds active sessions, it kills the sessions and outputs an entry to the log file. It also sends an E-Mail notification of the event to the admin.
It would be nice to see if this feature can be used in the GUI as well as viewing the event log here as well. The total number of active sessions on the secondary WAN should in my opinion be available in the GUI for the admin to see.
Kindly note, you will need to find a way to capture what the secondary WAN Interface IP address is as in my example, I entered the local IP address of the secondary WAN in my script in order for this proof of concept (POC) to work.
Files
Related issues