Here the complete log with changed ip addresses and ID
2013:06:14-07:43:27 firewall-1 red_server[4924]: SELF: New connection from 111.111.111.111 with ID A00000000000000 (cipher RC4-SHA), rev1
2013:06:14-07:43:27 firewall-1 red_server[4924]: SELF: Starting REDv2 protocol
2013:06:14-07:43:27 firewall-1 red_server[4924]: A00000000000000: connected OK, pushing config
2013:06:14-07:43:27 firewall-1 red_server[4924]: A00000000000000: Sending PEERS+222.222.222.222
2013:06:14-07:43:30 firewall-1 red_server[4924]: A00000000000000: command 'UMTS_STATUS value=OK'
2013:06:14-07:43:30 firewall-1 red_server[4924]: A00000000000000: command 'PING 0 uplink=WAN'
2013:06:14-07:43:30 firewall-1 red_server[4924]: A00000000000000: PING remote_tx=0 local_rx=0 diff=0
2013:06:14-07:43:30 firewall-1 red_server[4924]: A00000000000000: PONG local_tx=0
2013:06:14-07:43:41 firewall-1 red2ctl[25080]: Overflow happened on reds1:0
2013:06:14-07:43:41 firewall-1 red2ctl[25080]: Missing keepalive from reds1:0, disabling peer 111.111.111.111
2013:06:14-07:43:46 firewall-1 red_server[4924]: A00000000000000: command 'PING 0 uplink=WAN'
2013:06:14-07:43:46 firewall-1 red_server[4924]: A00000000000000: PING remote_tx=0 local_rx=0 diff=0
2013:06:14-07:43:46 firewall-1 red_server[4924]: A00000000000000: PONG local_tx=0
2013:06:14-07:43:51 firewall-1 red2ctl[25080]: Received keepalive from reds1:0, enabling peer 111.111.111.111
2013:06:14-07:44:01 firewall-1 red_server[4924]: A00000000000000: command 'PING 0 uplink=WAN'
2013:06:14-07:44:01 firewall-1 red_server[4924]: A00000000000000: PING remote_tx=0 local_rx=0 diff=0
2013:06:14-07:44:01 firewall-1 red_server[4924]: A00000000000000: PONG local_tx=0
2013:06:14-07:44:05 firewall-1 red_server[5212]: SELF: New connection from 111.111.111.111 with ID A00000000000000 (cipher RC4-SHA), rev1
2013:06:14-07:44:05 firewall-1 red_server[5212]: A00000000000000: already connected, releasing old connection
2013:06:14-07:44:31 firewall-1 red2ctl[25080]: Missing keepalive from reds1:0, disabling peer 111.111.111.111
I think this issue was already reported under Mantis ID #25375 in the beta forum but it still not seems to be fixed in the current release 9.101-12 which we are using.
Are there any updates on this or maybe workarounds to temporary fix the issue?
The only workaround I found is powering off/on the RED50 manually.
Since this does not work on remote site I have to wait until this bug is fixed before I can use the red50 in a live system.
This thread was automatically locked due to age.
