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-16 Released to GA

UTM Version 9.308 is now officially released:

UTM Up2Date 9.308 Released | Sophos Blog


This thread was automatically locked due to age.
  • What is everybody's experience with the new release?
      

    No problems so far, just wifi seperate zone, still needs a fix/workaround to function correctly [;)]

    Sent from my iPhone using Astaro.org

    -----

    Best regards
    Martin

    Sophos XGS 2100 @ Home | Sophos v20 Technician

  • the reseller try to contact sophos with no luck.
  • lines out of the kernel log

    2015:02:27-06:59:17 esie kernel: [58431.769429] httpproxy[9430]: segfault at 78696942 ip 00000000f7410d41 sp 00000000ecf1ce70 error 4 in libtcmalloc.so.4.1.0[f73ee000+48000] 

    2015:02:27-07:03:37 esie kernel: [58692.733555] EpollWorker_19[9698]: segfault at 0 ip 00000000f737f103 sp 00000000f3eb9d10 error 4 in libtcmalloc.so.4.1.0[f7358000+48000] 

    2015:02:27-07:04:03 esie kernel: [58718.003846] EpollWorker_01[10562]: segfault at 75706572 ip 00000000f73adb96 sp 00000000f62eafa0 error 4 in libtcmalloc.so.4.1.0[f7375000+48000] 

    2015:02:27-07:04:24 esie kernel: [58739.169294] EpollWorker_02[10787]: segfault at 0 ip 00000000f73bf103 sp 00000000f610cf50 error 4 in libtcmalloc.so.4.1.0[f7398000+48000] 

    2015:02:27-07:04:47 esie kernel: [58762.177594] EpollWorker_02[10988]: segfault at 78696942 ip 00000000f73dab96 sp 00000000f6116f80 error 4 in libtcmalloc.so.4.1.0[f73a2000+48000] 

    2015:02:27-07:05:07 esie kernel: [58782.285781] EpollWorker_01[11249]: segfault at 5050414b ip 00000000f7382b96 sp 00000000f62bff80 error 4 in libtcmalloc.so.4.1.0[f734a000+48000] 

    2015:02:27-07:05:28 esie kernel: [58803.772781] EpollWorker_01[11449]: segfault at 0 ip 00000000f73f6103 sp 00000000f6344f50 error 4 in libtcmalloc.so.4.1.0[f73cf000+48000] 

    2015:02:27-07:05:50 esie kernel: [58825.795399] EpollWorker_02[11651]: segfault at 7a696c42 ip 00000000f73ffb96 sp 00000000f613bf80 error
  • Having problems at work with our RED right after the update with our RED reconnecting every 2 minutes :-(

    2015:02:27-00:14:13 proxy-2 red_server[11203]: A30000B5***XB2X: connected OK, pushing config
    2015:02:27-00:14:20 proxy-2 red_server[11203]: A30000B5***XB2X: command 'PING 0'
    2015:02:27-00:14:20 proxy-2 red_server[11203]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="A30000B5***XB2X" forced="0"
    2015:02:27-00:14:20 proxy-2 red_server[7988]: SELF: (Re-)loading device configurations
    2015:02:27-00:14:20 proxy-2 red_server[11203]: A30000B5***XB2X: PING remote_tx=0 local_rx=0 diff=0
    2015:02:27-00:14:20 proxy-2 red_server[11203]: A30000B5***XB2X: PONG local_tx=42
    2015:02:27-00:14:35 proxy-2 red_server[11203]: A30000B5***XB2X: command 'PING 1'
    2015:02:27-00:14:35 proxy-2 red_server[11203]: A30000B5***XB2X: PING remote_tx=1 local_rx=1 diff=0
    2015:02:27-00:14:35 proxy-2 red_server[11203]: A30000B5***XB2X: PONG local_tx=133
    2015:02:27-00:14:51 proxy-2 red_server[11203]: A30000B5***XB2X: command 'PING 2'
    2015:02:27-00:14:51 proxy-2 red_server[11203]: A30000B5***XB2X: PING remote_tx=2 local_rx=6 diff=-4
    2015:02:27-00:14:51 proxy-2 red_server[11203]: A30000B5***XB2X: PONG local_tx=182
    2015:02:27-00:15:19 proxy-2 red_server[11765]: SELF: New connection from 89.166.***.XX with ID A30000B5***XB2X (cipher RC4-SHA), rev1
    2015:02:27-00:15:19 proxy-2 red_server[11765]: A30000B5***XB2X: already connected, releasing old connection.
    2015:02:27-00:15:19 proxy-2 red_server[11203]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="A30000B5***XB2X" forced="1"
    2015:02:27-00:15:19 proxy-2 red_server[7988]: SELF: (Re-)loading device configurations
    2015:02:27-00:15:19 proxy-2 red_server[11203]: A30000B5***XB2X is disconnected.
    2015:02:27-00:15:20 proxy-2 redctl[11876]: key length: 32
    2015:02:27-00:15:20 proxy-2 redctl[11877]: key length: 32
    2015:02:27-00:15:20 proxy-2 red_server[11765]: A30000B5***XB2X: connected OK, pushing config
    2015:02:27-00:15:27 proxy-2 red_server[11765]: A30000B5***XB2X: command 'PING 0'
    2015:02:27-00:15:27 proxy-2 red_server[11765]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="A30000B5***XB2X" forced="0"
    2015:02:27-00:15:27 proxy-2 red_server[7988]: SELF: (Re-)loading device configurations
    2015:02:27-00:15:27 proxy-2 red_server[11765]: A30000B5***XB2X: PING remote_tx=0 local_rx=0 diff=0
    2015:02:27-00:15:27 proxy-2 red_server[11765]: A30000B5***XB2X: PONG local_tx=0
    2015:02:27-00:15:43 proxy-2 red_server[11765]: A30000B5***XB2X: command 'PING 1'
    2015:02:27-00:15:43 proxy-2 red_server[11765]: A30000B5***XB2X: PING remote_tx=1 local_rx=1 diff=0
    2015:02:27-00:15:43 proxy-2 red_server[11765]: A30000B5***XB2X: PONG local_tx=1
    2015:02:27-00:15:59 proxy-2 red_server[11765]: A30000B5***XB2X: command 'PING 10'
    2015:02:27-00:15:59 proxy-2 red_server[11765]: A30000B5***XB2X: PING remote_tx=10 local_rx=10 diff=0
    2015:02:27-00:15:59 proxy-2 red_server[11765]: A30000B5***XB2X: PONG local_tx=2
    2015:02:27-00:16:26 proxy-2 red_server[12166]: SELF: New connection from 89.166.***.XX with ID A30000B5***XB2X (cipher RC4-SHA), rev1
    2015:02:27-00:16:26 proxy-2 red_server[12166]: A30000B5***XB2X: already connected, releasing old connection.
    2015:02:27-00:16:26 proxy-2 red_server[11765]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="A30000B5***XB2X" forced="1"
    2015:02:27-00:16:26 proxy-2 red_server[7988]: SELF: (Re-)loading device configurations
    2015:02:27-00:16:26 proxy-2 red_server[11765]: A30000B5***XB2X is disconnected.
  • Damn !!

    Giving us the same issue with RED !

    2015:02:27-18:21:38 DVicSophosUTM01-2 red_server[9031]: A3200C53DAE6057 is disconnected.
    2015:02:27-18:21:39 DVicSophosUTM01-2 redctl[9497]: key length: 32
    2015:02:27-18:21:39 DVicSophosUTM01-2 redctl[9498]: key length: 32
    2015:02:27-18:21:39 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: connected OK, pushing config
    2015:02:27-18:21:43 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: command 'UMTS_STATUS value=OK'
    2015:02:27-18:21:43 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: command 'PING 1 uplink=WAN'
    2015:02:27-18:21:43 DVicSophosUTM01-2 red_server[9382]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="A3DAE6057" forced="0"
    2015:02:27-18:21:44 DVicSophosUTM01-2 red_server[6990]: SELF: (Re-)loading device configurations
    2015:02:27-18:21:44 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: PING remote_tx=1 local_rx=2 diff=-1
    2015:02:27-18:21:44 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: PONG local_tx=3
    2015:02:27-18:21:59 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: command 'PING 24 uplink=WAN'
    2015:02:27-18:21:59 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: PING remote_tx=24 local_rx=24 diff=0
    2015:02:27-18:21:59 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: PONG local_tx=30
    2015:02:27-18:22:15 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: command 'PING 43 uplink=WAN'
    2015:02:27-18:22:15 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: PING remote_tx=43 local_rx=43 diff=0
    2015:02:27-18:22:15 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057: PONG local_tx=49
    2015:02:27-18:22:43 DVicSophosUTM01-2 red_server[9783]: SELF: New connection from 101.***.***.63 with ID A3200C53DAE6057 (cipher RC4-SHA), rev1
    2015:02:27-18:22:43 DVicSophosUTM01-2 red_server[9783]: A37: already connected, releasing old connection.
    2015:02:27-18:22:43 DVicSophosUTM01-2 red_server[9382]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="A37" forced="1"
    2015:02:27-18:22:43 DVicSophosUTM01-2 red_server[6990]: SELF: (Re-)loading device configurations
    2015:02:27-18:22:43 DVicSophosUTM01-2 red_server[9382]: A3200C53DAE6057 is disconnected.
    2015:02:27-18:22:44 DVicSophosUTM01-2 redctl[9898]: key length: 32
    2015:02:27-18:22:44 DVicSophosUTM01-2 redctl[9899]: key length: 32
    2015:02:27-18:22:44 DVicSophosUTM01-2 red_server[9783]: A3200C53DAE6057: connected OK, pushing config
    2015:02:27-18:22:49 DVicSophosUTM01-2 red_server[9783]: A3200C53DAE6057: command 'UMTS_STATUS value=OK'
    2015:02:27-18:22:49 DVicSophosUTM01-2 red_server[9783]: A3200C53DAE6057: command 'PING 0 uplink=WAN'
    2015:02:27-18:22:49 DVicSophosUTM01-2 red_server[9783]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="A327" forced="0"
    2015:02:27-18:22:49 DVicSophosUTM01-2 red_server[6990]: SELF: (Re-)loading device configurations
    2015:02:27-18:22:49 DVicSophosUTM01-2 red_server[9783]: A3200C53DAE6057: PING remote_tx=0 local_rx=0 diff=0
    2015:02:27-18:22:49 DVicSophosUTM01-2 red_server[9783]: A3200C53DAE6057: PONG local_tx=2
    2015:02:27-18:23:04 DVicSophosUTM01-2 red_server[9783]: A3200C53DAE6057: command 'PING 12 uplink=WAN'
    2015:02:27-18:23:04 DVicSophosUTM01-2 red_server[9783]: A3200C53DAE6057: PING remote_tx=12 local_rx=13 diff=-1
    2015:02:27-18:23:04 DVicSophosUTM01-2 red_server[9783]: A3200C53DAE6057: PONG local_tx=22

    SOPHOS; please get your act together ! Its causing a lot of grief !

    How can we get RED to remain connected !??
  • the RED remains connected, the only thing reconnecting seems to be the tunnel.

    We can ping the RED WAN IP all the time, but the tunnel keeps getting reconnecting...
  • For starters...

    Try to remove the RED Device and recreate it (ID and unlock code)....I know it's not satisfactorily....

    What UTM and RED do you use, do you run in bridge with the RED?

    -----

    Best regards
    Martin

    Sophos XGS 2100 @ Home | Sophos v20 Technician

  • 2x SG230 as HA, RED 10, not using bridge.
  • Are both SG230 in ready active mode under "High Availability"

    -----

    Best regards
    Martin

    Sophos XGS 2100 @ Home | Sophos v20 Technician

  • one is Active, one is Ready, aside from the RED Problem everything else is working except for some problems with our IPv6 Tunnel and the Proxy, but since we only use IPv6 for some testing it was not an issue to deactivate it for the moment.

    The Problem was that sites who offer ipv6 (google, facebook) were not able to open. But we did not follow on that problem yet as it was as easy as to deactive ipv6 [;)]



    SSL VPN via the sophos client on windows is working by the way.