Thread Info
  • State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 4210 views
  • Users 0 members are here
Options
Suggested

[9.580-7] RED UTM-to-UTM tunnel not working

scorpionking

After updating both of my UTMs from 9.570 to 9.580 my RED site to site tunnel is not working an more. RED is shown as up on both sites but no traffic goes through the tunnel.

Repeated log entries every minute on the server UTM RED log:

2018:10:31-17:24:59 mx2 red_server[3933]: SELF: (Re-)loading device configurations
2018:10:31-17:25:00 mx2 redctl[9441]: key length: 32
2018:10:31-17:25:00 mx2 redctl[9442]: key length: 32
2018:10:31-17:25:00 mx2 red_server[9380]: 801a6f2a4ca2988: connected OK, pushing config
2018:10:31-17:25:01 mx2 red_server[9380]: 801a6f2a4ca2988: command 'PING 0'
2018:10:31-17:25:01 mx2 red_server[9380]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="801a6f2a4ca2988" forced="0"
2018:10:31-17:25:01 mx2 red_server[9380]: 801a6f2a4ca2988: PING remote_tx=0 local_rx=1 diff=-1
2018:10:31-17:25:01 mx2 red_server[9380]: 801a6f2a4ca2988: PONG local_tx=0
2018:10:31-17:25:01 mx2 red_server[3933]: SELF: (Re-)loading device configurations
2018:10:31-17:25:16 mx2 red_server[9380]: 801a6f2a4ca2988: command 'PING 1'
2018:10:31-17:25:16 mx2 red_server[9380]: 801a6f2a4ca2988: PING remote_tx=1 local_rx=2 diff=-1
2018:10:31-17:25:16 mx2 red_server[9380]: 801a6f2a4ca2988: PONG local_tx=25
2018:10:31-17:25:35 mx2 red_server[3933]: SELF: (Re-)loading device configurations
2018:10:31-17:25:35 mx2 red_server[3933]: Kicking device 801a6f2a4ca2988 as it was deactivated.
2018:10:31-17:25:35 mx2 red_server[9380]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="801a6f2a4ca2988" forced="1"
2018:10:31-17:25:35 mx2 red_server[9380]: 801a6f2a4ca2988 is disconnected.
2018:10:31-17:25:36 mx2 red_server[3933]: SELF: (Re-)loading device configurations
2018:10:31-17:25:38 mx2 red_server[3933]: SELF: (Re-)loading device configurations
2018:10:31-17:25:40 mx2 red_server[9849]: SELF: New connection from 87.138.186.171 with ID 801a6f2a4ca2988 (cipher AES256-GCM-SHA384), rev1
2018:10:31-17:25:40 mx2 redctl[9851]: key length: 32
2018:10:31-17:25:40 mx2 redctl[9852]: key length: 32
2018:10:31-17:25:40 mx2 red_server[9849]: 801a6f2a4ca2988: connected OK, pushing config
2018:10:31-17:25:41 mx2 red_server[9849]: 801a6f2a4ca2988: command 'PING 0'
2018:10:31-17:25:41 mx2 red_server[9849]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="801a6f2a4ca2988" forced="0"
2018:10:31-17:25:41 mx2 red_server[9849]: 801a6f2a4ca2988: PING remote_tx=0 local_rx=1 diff=-1
2018:10:31-17:25:41 mx2 red_server[9849]: 801a6f2a4ca2988: PONG local_tx=0
2018:10:31-17:25:41 mx2 red_server[3933]: SELF: (Re-)loading device configurations
2018:10:31-17:25:56 mx2 red_server[9849]: 801a6f2a4ca2988: command 'PING 7'
2018:10:31-17:25:56 mx2 red_server[9849]: 801a6f2a4ca2988: PING remote_tx=7 local_rx=8 diff=-1
2018:10:31-17:25:56 mx2 red_server[9849]: 801a6f2a4ca2988: PONG local_tx=15
2018:10:31-17:26:12 mx2 red_server[9849]: 801a6f2a4ca2988: command 'PING 8'
2018:10:31-17:26:12 mx2 red_server[9849]: 801a6f2a4ca2988: PING remote_tx=8 local_rx=9 diff=-1
2018:10:31-17:26:12 mx2 red_server[9849]: 801a6f2a4ca2988: PONG local_tx=20
2018:10:31-17:26:27 mx2 red_server[9849]: 801a6f2a4ca2988: command 'PING 14'
2018:10:31-17:26:27 mx2 red_server[9849]: 801a6f2a4ca2988: PING remote_tx=14 local_rx=16 diff=-2
2018:10:31-17:26:27 mx2 red_server[9849]: 801a6f2a4ca2988: PONG local_tx=37
2018:10:31-17:26:43 mx2 red_server[9849]: 801a6f2a4ca2988: command 'PING 28'
2018:10:31-17:26:43 mx2 red_server[9849]: 801a6f2a4ca2988: PING remote_tx=28 local_rx=29 diff=-1
2018:10:31-17:26:43 mx2 red_server[9849]: 801a6f2a4ca2988: PONG local_tx=66
2018:10:31-17:26:45 mx2 red_server[10054]: SELF: New connection from 87.138.186.171 with ID 801a6f2a4ca2988 (cipher AES256-GCM-SHA384), rev1
2018:10:31-17:26:45 mx2 red_server[10054]: 801a6f2a4ca2988: already connected, releasing old connection.
2018:10:31-17:26:45 mx2 red_server[9849]: id="4202" severity="info" sys="System" sub="RED" name="RED Tunnel Down" red_id="801a6f2a4ca2988" forced="1"
2018:10:31-17:26:45 mx2 red_server[9849]: 801a6f2a4ca2988 is disconnected.

Repeated log entries every minute on the client UTM RED log:

2018:10:31-17:25:00 vpn red_client[44777]: CHILD Tunnel 1: performing initial keying.
2018:10:31-17:25:00 vpn redctl[44799]: key length: 32
2018:10:31-17:25:00 vpn redctl[44800]: key length: 32
2018:10:31-17:25:00 vpn redctl[44802]: 138.201.174.12 = 
2018:10:31-17:25:00 vpn redctl[44802]:   138.201.174.12
2018:10:31-17:25:28 vpn red_client[4313]: SELF: (Re-)loading client configurations
2018:10:31-17:25:28 vpn red_client[4313]: Tunnel 1: Device config value 'status' changed from '0' to '1'
2018:10:31-17:25:28 vpn red_client[4313]: Tunnel 1: client has been deactivated
2018:10:31-17:25:28 vpn red_client[44777]: Tunnel 1: disconnected
2018:10:31-17:25:40 vpn red_client[4313]: SELF: (Re-)loading client configurations
2018:10:31-17:25:40 vpn red_client[4313]: Tunnel 1: Device config value 'status' changed from '1' to '0'
2018:10:31-17:25:40 vpn red_client[4313]: Tunnel 1: Forking client handler
2018:10:31-17:25:40 vpn red_client[45128]: CHILD Tunnel 1: performing initial keying.
2018:10:31-17:25:40 vpn redctl[45158]: key length: 32
2018:10:31-17:25:40 vpn redctl[45159]: key length: 32
2018:10:31-17:25:40 vpn redctl[45161]: 138.201.174.12 = 
2018:10:31-17:25:40 vpn redctl[45161]:   138.201.174.12
2018:10:31-17:26:43 vpn red_client[45128]: CHILD Tunnel 1: No in-tunnel packet received for 60 seconds, assuming link is dead.
2018:10:31-17:26:43 vpn red_client[45128]: Tunnel 1: disconnected
2018:10:31-17:26:45 vpn red_client[4313]: Tunnel 1: Forking client handler
Parents
  • 0

    Damn, after another reboot of both UTMs the error is gone...

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Reply
  • 0

    Damn, after another reboot of both UTMs the error is gone...

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Children
No Data
Unfiltered HTML