Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 22 replies
  • Subscribers 1 subscriber
  • Views 11623 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

9.308 Killed RED !!

jazzoberoi
Hi Guys,

So we finally took the plunge on the 9.3 firmware thinking Sophos would've gotten their act together by now with the firmwares by installing 9.308.. BIG MISTAKE [:O]

Its killed our RED connection and it keeps getting disconnected after every 30 secs. Please HELP ! 

2015:02:27-19:10:33 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: connected OK, pushing config

2015:02:27-19:10:37 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: command 'UMTS_STATUS value=OK'

2015:02:27-19:10:37 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: command 'PING 1 uplink=WAN'

2015:02:27-19:10:37 DVicSophosUTM01-2 red_server[28872]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="A3200C53DAE6057" forced="0"

2015:02:27-19:10:38 DVicSophosUTM01-2 red_server[6990]: SELF: (Re-)loading device configurations

2015:02:27-19:10:38 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: PING remote_tx=1 local_rx=2 diff=-1

2015:02:27-19:10:38 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: PONG local_tx=3

2015:02:27-19:10:53 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: command 'PING 22 uplink=WAN'

2015:02:27-19:10:53 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: PING remote_tx=22 local_rx=22 diff=0

2015:02:27-19:10:53 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: PONG local_tx=22

2015:02:27-19:11:09 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: command 'PING 38 uplink=WAN'

2015:02:27-19:11:09 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: PING remote_tx=38 local_rx=38 diff=0

2015:02:27-19:11:09 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057: PONG local_tx=40

2015:02:27-19:11:37 DVicSophosUTM01-2 red_server[29248]: SELF: New connection from 101.172.213.63 with ID A3200C53DAE6057 (cipher RC4-SHA), rev1

2015:02:27-19:11:37 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: already connected, releasing old connection.

2015:02:27-19:11:37 DVicSophosUTM01-2 red_server[28872]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="A3200C53DAE6057" forced="1"

2015:02:27-19:11:37 DVicSophosUTM01-2 red_server[6990]: SELF: (Re-)loading device configurations

2015:02:27-19:11:37 DVicSophosUTM01-2 red_server[28872]: A3200C53DAE6057 is disconnected.

2015:02:27-19:11:38 DVicSophosUTM01-2 redctl[29363]: key length: 32

2015:02:27-19:11:38 DVicSophosUTM01-2 redctl[29364]: key length: 32

2015:02:27-19:11:38 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: connected OK, pushing config

2015:02:27-19:11:43 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: command 'UMTS_STATUS value=OK'

2015:02:27-19:11:43 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: command 'PING 1 uplink=WAN'

2015:02:27-19:11:43 DVicSophosUTM01-2 red_server[29248]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="A3200C53DAE6057" forced="0"

2015:02:27-19:11:43 DVicSophosUTM01-2 red_server[6990]: SELF: (Re-)loading device configurations

2015:02:27-19:11:43 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: PING remote_tx=1 local_rx=1 diff=0

2015:02:27-19:11:43 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: PONG local_tx=2

2015:02:27-19:11:59 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: command 'PING 16 uplink=WAN'

2015:02:27-19:11:59 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: PING remote_tx=16 local_rx=16 diff=0

2015:02:27-19:11:59 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: PONG local_tx=20

2015:02:27-19:12:15 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: command 'PING 33 uplink=WAN'

2015:02:27-19:12:15 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: PING remote_tx=33 local_rx=33 diff=0

2015:02:27-19:12:15 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057: PONG local_tx=39

2015:02:27-19:12:42 DVicSophosUTM01-2 red_server[29590]: SELF: New connection from 101.172.213.63 with ID A3200C53DAE6057 (cipher RC4-SHA), rev1

2015:02:27-19:12:42 DVicSophosUTM01-2 red_server[29590]: A3200C53DAE6057: already connected, releasing old connection.

2015:02:27-19:12:42 DVicSophosUTM01-2 red_server[29248]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="A3200C53DAE6057" forced="1"

2015:02:27-19:12:42 DVicSophosUTM01-2 red_server[6990]: SELF: (Re-)loading device configurations

2015:02:27-19:12:42 DVicSophosUTM01-2 red_server[29248]: A3200C53DAE6057 is disconnected.

2015:02:27-19:12:43 DVicSophosUTM01-2 redctl[29706]: key length: 32

2015:02:27-19:12:43 DVicSophosUTM01-2 redctl[29707]: key length: 32

2015:02:27-19:12:43 DVicSophosUTM01-2 red_server[29590]: A3200C53DAE6057: connected OK, pushing config

2015:02:27-19:12:48 DVicSophosUTM01-2 red_server[29590]: A3200C53DAE6057: command 'UMTS_STATUS value=OK'

2015:02:27-19:12:48 DVicSophosUTM01-2 red_server[29590]: A3200C53DAE6057: command 'PING 1 uplink=WAN'

2015:02:27-19:12:48 DVicSophosUTM01-2 red_server[29590]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="A3200C53DAE6057" forced="0"

2015:02:27-19:12:48 DVicSophosUTM01-2 red_server[6990]: SELF: (Re-)loading device configurations

2015:02:27-19:12:48 DVicSophosUTM01-2 red_server[29590]: A3200C53DAE6057: PING remote_tx=1 local_rx=1 diff=0

2015:02:27-19:12:48 DVicSophosUTM01-2 red_server[29590]: A3200C53DAE6057: PONG local_tx=2


This thread was automatically locked due to age.
Parents
  • 0
    Does your RED config apply for the workarounds? Do you have case 1 or case 2 from the kb entry?
  • 0 in reply to Hallowach2
    Does your RED config apply for the workarounds? Do you have case 1 or case 2 from the kb entry?

    Yes, I have two uplink interfaces and moved the one on which the REDs connect to the first position, also I entered the IP of this interface in the RED Config. But still I get reconnects every minute or so...

    Edit: What seems to help is to move the second to the standby interfaces, then let the reds connect on move it back. I will keep an eye on it...
Reply
  • 0 in reply to Hallowach2
    Does your RED config apply for the workarounds? Do you have case 1 or case 2 from the kb entry?

    Yes, I have two uplink interfaces and moved the one on which the REDs connect to the first position, also I entered the IP of this interface in the RED Config. But still I get reconnects every minute or so...

    Edit: What seems to help is to move the second to the standby interfaces, then let the reds connect on move it back. I will keep an eye on it...
Children
  • 0 in reply to SveN_01
    Our UTM is behind a Cisco firewall with NAT. The RED was connecting to one of the additional addresses of the WAN interface of the UTM.
    After the update to 9.308-16 the RED was connecting/disconnecting every 30 seconds. When changing the IP address to the 'real' ip address of the WAN interface the problem was solved and the RED came back online again.
Unfiltered HTML