Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 26 subscribers
  • Views 2562 views
  • Users 0 members are here
Options
Suggested
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

Site 2 Site Ipsec VPN-Problem UTM 9 -> Watchgard

JoeT

Hallo Habe Ständig Abbrüche auf dem Site 2 Site VPN zwischen Sophos Utm9  akt. Firmware und Watchguard Firebox.

 

In IP Sec.log sind folgende Meldungen:

017:12:14-00:00:11 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:00:31 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:00:34 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:00:51 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:01:11 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:01:14 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:01:31 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:01:51 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:01:55 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:02:11 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:02:32 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:02:34 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:02:51 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:03:11 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:03:14 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:03:31 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:03:52 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:03:54 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:04:11 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:04:31 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:04:35 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:04:51 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:05:12 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:05:14 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:05:31 sophosutm125-1 pluto[9036]: "S_REF_IpsSitS2soldisle_0" #70: max number of retransmissions (20) reached STATE_MAIN_I1. No response (or no acceptable response) to our first IKE message
2017:12:14-00:05:31 sophosutm125-1 pluto[9036]: "S_REF_IpsSitS2soldisle_0" #70: starting keying attempt 24 of an unlimited number
2017:12:14-00:05:31 sophosutm125-1 pluto[9036]: "S_REF_IpsSitS2soldisle_0" #73: initiating Main Mode to replace #70
2017:12:14-00:05:31 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:05:52 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:05:54 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:06:01 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:06:31 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:06:35 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:06:41 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:07:11 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:07:15 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:07:22 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:07:51 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:07:55 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:08:02 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:08:31 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:08:35 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:08:41 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:09:11 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:09:16 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:09:21 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:09:51 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:09:55 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:10:01 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:10:32 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:10:35 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:10:41 sophosutm125-1 pluto[9036]: packet from 80.153.76.43:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:12:14-00:11:11 sophosutm125-1 pluto[9036]: "S_REF_IpsSitS2soldisle_4" #71: max number of retransmissions (20) reached STATE_MAIN_I1. No response (or no acceptable response) to our first IKE message
2017:12:14-00:11:11 sophosutm125-1 pluto[9036]: "S_REF_IpsSitS2soldisle_4" #71: starting keying attempt 5 of an unlimited number
2017:12:14-00:11:11 sophosutm125-1 pluto[9036]: "S_REF_IpsSitS2soldisle_4" #74: initiating Main Mode to replace #71



This thread was automatically locked due to age.
Parents
  • 0

    Hallo Joe,

    (Sorry, my German-speaking brain isn't creating thoughts at the moment. [:(])

    Confirm that DPD and NAT-T are selected in both the UTM and WatchGuard.  Please attach pictures of the Edit of the UTM's IPsec Policy and of the corresponding information from the WatchGuard.

    MfG - Bob (Bitte auf Deutsch weiterhin.)

Reply
  • 0

    Hallo Joe,

    (Sorry, my German-speaking brain isn't creating thoughts at the moment. [:(])

    Confirm that DPD and NAT-T are selected in both the UTM and WatchGuard.  Please attach pictures of the Edit of the UTM's IPsec Policy and of the corresponding information from the WatchGuard.

    MfG - Bob (Bitte auf Deutsch weiterhin.)

Children
No Data