UTM to UTM Red Tunnel wont restart after Internet Connection loss

Question

We have two Systems with the Sophos UTM Software (Version 9.108-23) installed. These two systems are installed on different locations one is installed in our datacenter and the other one is installed in our main office. Between these two UTM we have configured a RED Tunnel which is working properly. All the traffic from the main office goes through the RED Tunnel to the UTM in the datacenter. And from there the traffic goes to the internet. The UTM on the main office initiates the RED Tunnel und everything works fine until the internet connection in the main office is going down. Then the RED Tunnel is although going down. After the internet connection in the main office is reestablished the RED Tunnel comes up again. But no traffic is flowing over the tunnel. In the RED Log of the UTM in the main office you will see the following.

2014:03:25-11:01:58 wilkenson red_client[6787]: CHILD Tunnel 2: Socket was closed
2014:03:25-11:01:58 wilkenson red_client[6787]: CHILD Tunnel 2: Unable to read PING response
2014:03:25-11:01:58 wilkenson red_client[3969]: SELF: (Re-)loading client configurations
2014:03:25-11:01:59 wilkenson red_client[3969]: Tunnel 2: Handler died, restarting
2014:03:25-11:02:04 wilkenson red_client[3969]: Tunnel 2: Forking client handler
2014:03:25-11:02:04 wilkenson red_client[7625]: CHILD Tunnel 2: performing initial keying.
2014:03:25-11:02:04 wilkenson redctl[7628]: key length: 32
2014:03:25-11:02:04 wilkenson redctl[7629]: key length: 32
2014:03:25-11:02:04 wilkenson redctl[7631]: 81.90.32.150 =
2014:03:25-11:02:04 wilkenson redctl[7631]: 81.90.32.150

On the RED Log of the Server UTM in the datacenter you will see the following:

2014:03:25-11:02:04 wilkenson red_server[9273]: SELF: New connection from 95.208.44.91 with ID cc85070bf665485 (cipher RC4-SHA), rev1
2014:03:25-11:02:04 wilkenson redctl[9277]: key length: 32
2014:03:25-11:02:04 wilkenson redctl[9278]: key length: 32
2014:03:25-11:02:04 wilkenson red_server[9273]: cc85070bf665485: connected OK, pushing config
2014:03:25-11:02:05 wilkenson red_server[9273]: cc85070bf665485: command 'PING 0'
2014:03:25-11:02:05 wilkenson red_server[9273]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="cc85070bf665485" forced="0"
2014:03:25-11:02:05 wilkenson red_server[9273]: cc85070bf665485: PING remote_tx=0 local_rx=0 diff=0
2014:03:25-11:02:05 wilkenson red_server[9273]: cc85070bf665485: PONG local_tx=0
2014:03:25-11:02:20 wilkenson red_server[9273]: cc85070bf665485: command 'PING 27'
2014:03:25-11:02:20 wilkenson red_server[9273]: cc85070bf665485: PING remote_tx=27 local_rx=0 diff=27
2014:03:25-11:02:20 wilkenson red_server[9273]: cc85070bf665485: PONG local_tx=16
2014:03:25-11:02:35 wilkenson red_server[9273]: cc85070bf665485: command 'PING 56'
2014:03:25-11:02:35 wilkenson red_server[9273]: cc85070bf665485: PING remote_tx=56 local_rx=0 diff=56
2014:03:25-11:02:35 wilkenson red_server[9273]: cc85070bf665485: PONG local_tx=32
2014:03:25-11:03:05 wilkenson red_server[9273]: cc85070bf665485: No in-tunnel frame for 60 seconds, exiting.
2014:03:25-11:03:05 wilkenson red_server[9273]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="cc85070bf665485" forced="0"
2014:03:25-11:03:05 wilkenson red_server[9273]: cc85070bf665485 is disconnected.

To get the RED Tunnel working again we have to reboot the UTM on the main office. After we reboot the UTM on the main office the RED comes up again and traffic goes its way over the tunnel. But only to the the the internet connection is lost again.

So does anyone know how we get the RED tunnel up working after a connection loss without rebooting the whole UTM?

This thread was automatically locked due to age.