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

RED 10 now working - Sytem blink red and Tunnel green

Hi,

I picked out an older RED 10 and plugged these in my external Network (in front of my utm, not behind) to test these bevor driving to my new remote office.

The RED semes to be working but after a short time the System LED begin to blink red and the Tunnel LED green. After this the RED rebuilds the tunnel and again and again.
Also no packaged are being routet through this. DHCP / DNS / Firewall ... is configured.

 

The KB Artikel says this, but it make no sense, i've not using mobile broadband: (https://community.sophos.com/kb/en-us/116173)

Mobile broadband - locked by the RED appliance.
SIM requires PUK or PIN  is required, but no or wrong PIN given.

 

The RED is configured in operationmode standard / unified; uplinkmode dhcp

The Live-Log:
2017:06:12-21:05:49 utm1 redctl[11391]: key length: 32
2017:06:12-21:05:49 utm1 redctl[11392]: key length: 32
2017:06:12-21:05:49 utm1 red_server[11389]: A3200xxxxxxxxxx: connected OK, pushing config
2017:06:12-21:05:54 utm1 red_server[11389]: A3200xxxxxxxxxx: command 'UMTS_STATUS value=OK'
2017:06:12-21:05:54 utm1 red_server[11389]: A3200xxxxxxxxxx: command 'PING 0 uplink=WAN'
2017:06:12-21:05:54 utm1 red_server[11389]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="A3200xxxxxxxxxx" forced="0"
2017:06:12-21:05:54 utm1 red_server[11389]: A3200xxxxxxxxxx: PING remote_tx=0 local_rx=0 diff=0
2017:06:12-21:05:54 utm1 red_server[11389]: A3200xxxxxxxxxx: PONG local_tx=0
2017:06:12-21:05:54 utm1 red_server[4183]: SELF: (Re-)loading device configurations
2017:06:12-21:06:10 utm1 red_server[11389]: A3200xxxxxxxxxx: command 'PING 17 uplink=WAN'
2017:06:12-21:06:10 utm1 red_server[11389]: A3200xxxxxxxxxx: PING remote_tx=17 local_rx=0 diff=17
2017:06:12-21:06:10 utm1 red_server[11389]: A3200xxxxxxxxxx: PONG local_tx=1
2017:06:12-21:06:26 utm1 red_server[11389]: A3200xxxxxxxxxx: command 'PING 34 uplink=WAN'
2017:06:12-21:06:26 utm1 red_server[11389]: A3200xxxxxxxxxx: PING remote_tx=34 local_rx=0 diff=34
2017:06:12-21:06:26 utm1 red_server[11389]: A3200xxxxxxxxxx: PONG local_tx=2
2017:06:12-21:06:50 utm1 red_server[11389]: A3200xxxxxxxxxx: No in-tunnel frame for 60 seconds, exiting.
2017:06:12-21:06:50 utm1 red_server[11389]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="A3200xxxxxxxxxx" forced="0"
2017:06:12-21:06:50 utm1 red_server[11389]: A3200xxxxxxxxxx is disconnected.
2017:06:12-21:06:50 utm1 red_server[4183]: SELF: (Re-)loading device configurations
2017:06:12-21:06:53 utm1 red_server[11557]: SELF: New connection from 88.00.00.00 with ID A3200xxxxxxxxxx (cipher AES256-GCM-SHA384), rev1
2017:06:12-21:06:53 utm1 redctl[11559]: key length: 32
2017:06:12-21:06:53 utm1 redctl[11560]: key length: 32

my UTM Version is 9.501

 

Any Ideas?

Regards
Logan



This thread was automatically locked due to age.
Parents
  • I don't yet trust 9.501, so I think you probably should get Sophos Support involved.

    The one thing I see is No in-tunnel frame for 60 seconds, exiting.  What happens if you put a client behind the red so that the UTM sees something there?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • at first my utm was at version 9.413 and i got the same error so i updated to 9.501 in hope that this is only a bug

    A client is connected but this has no connection. Neither with dhcp nor with static ip. So link is there, but nothing is routed

Reply
  • at first my utm was at version 9.413 and i got the same error so i updated to 9.501 in hope that this is only a bug

    A client is connected but this has no connection. Neither with dhcp nor with static ip. So link is there, but nothing is routed

Children
No Data