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

UTM RED TO XG TUNNEL

Hello,

 

Is the UTM to XG tunnel using RED tunnel is now officially supported?...can someone send me some support/help links please...



This thread was automatically locked due to age.
Parents Reply Children
  • Thank you...I'm positive to go for IPSEC, since it is fully documented on the knowledgebase.

  • Hi,

     

    I am trying the IPSEC and this error logged on the UTM, any suggestion?

     

    7:02-08:36:50 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: received Vendor ID payload [XAUTH]
    2018:07:02-08:36:50 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: received Vendor ID payload [Dead Peer Detection]
    2018:07:02-08:36:50 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: ignoring Vendor ID payload [Cisco-Unity]
    2018:07:02-08:36:50 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: received Vendor ID payload [RFC 3947]
    2018:07:02-08:36:50 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: enabling possible NAT-traversal with method 3
    2018:07:02-08:36:50 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: NAT-Traversal: Result using RFC 3947: i am NATed
    2018:07:02-08:36:50 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: next payload type of ISAKMP Hash Payload has an unknown value: 116
    2018:07:02-08:36:50 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: malformed payload in packet
    2018:07:02-08:37:00 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: next payload type of ISAKMP Hash Payload has an unknown value: 74
    2018:07:02-08:37:00 ryad-utm pluto[27818]: "S_SG_TO_XG" #1: malformed payload in packet