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-to-Site VPN Tunnel zwischen Sophos UTM9 und Lancom 1781EW funktioniert nicht

Hallo,

ich versuche vergeblich einen VPN-Tunnel zwischen einer Sophos UTM9 und einem Lancom 1781EW aufzubauen. Ich habe es mit dieser Anleitung versucht http://www.utmfaq.de/sophos-utm-astaro/site-to-site-vpn/site-to-site-vpn.html jedoch ohne Erfolg.

Hier ein Auszug des Logs:

2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | *received 40 bytes from x.x.x.x:500 on eth7.101
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | **parse ISAKMP Message:
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | initiator cookie:
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | a2 d5 6c 61 7b 1e dc 99
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | responder cookie:
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | ff 9e 20 af b4 3e 2f fe
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | next payload type: ISAKMP_NEXT_N
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | ISAKMP version: ISAKMP Version 1.0
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | exchange type: ISAKMP_XCHG_INFO
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | flags: none
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | message ID: 00 00 00 00
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | length: 40
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | ICOOKIE: a2 d5 6c 61 7b 1e dc 99
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | RCOOKIE: ff 9e 20 af b4 3e 2f fe
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | peer: 50 93 49 44
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | state hash entry 19
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | state object not found
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | ***parse ISAKMP Notification Payload:
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | next payload type: ISAKMP_NEXT_NONE
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | length: 12
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | DOI: ISAKMP_DOI_IPSEC
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | protocol ID: 1
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | SPI size: 0
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | Notify Message Type: NO_PROPOSAL_CHOSEN
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: packet from x.x.x.x:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | info:
2017:10:06-08:14:12 sanomed_bs-2 pluto[20894]: | next event EVENT_SA_SYNC_UPDATE in 6 seconds
2017:10:06-08:14:18 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:14:18 sanomed_bs-2 pluto[20894]: | *time to handle event
2017:10:06-08:14:18 sanomed_bs-2 pluto[20894]: | event after this is EVENT_RETRANSMIT in 34 seconds
2017:10:06-08:14:18 sanomed_bs-2 pluto[20894]: | inserting event EVENT_SA_SYNC_UPDATE, timeout in 15 seconds
2017:10:06-08:14:18 sanomed_bs-2 pluto[20894]: | next event EVENT_SA_SYNC_UPDATE in 15 seconds
2017:10:06-08:14:33 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:14:33 sanomed_bs-2 pluto[20894]: | *time to handle event
2017:10:06-08:14:33 sanomed_bs-2 pluto[20894]: | event after this is EVENT_RETRANSMIT in 19 seconds
2017:10:06-08:14:33 sanomed_bs-2 pluto[20894]: | inserting event EVENT_SA_SYNC_UPDATE, timeout in 15 seconds
2017:10:06-08:14:33 sanomed_bs-2 pluto[20894]: | next event EVENT_SA_SYNC_UPDATE in 15 seconds
2017:10:06-08:14:48 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:14:48 sanomed_bs-2 pluto[20894]: | *time to handle event
2017:10:06-08:14:48 sanomed_bs-2 pluto[20894]: | event after this is EVENT_RETRANSMIT in 4 seconds
2017:10:06-08:14:48 sanomed_bs-2 pluto[20894]: | inserting event EVENT_SA_SYNC_UPDATE, timeout in 15 seconds
2017:10:06-08:14:48 sanomed_bs-2 pluto[20894]: | next event EVENT_RETRANSMIT in 4 seconds for #2
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | *time to handle event
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | event after this is EVENT_SA_SYNC_UPDATE in 11 seconds
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | handling event EVENT_RETRANSMIT for x.x.x.x "xxxxx" #2
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | inserting event EVENT_RETRANSMIT, timeout in 40 seconds for #2
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | next event EVENT_SA_SYNC_UPDATE in 11 seconds
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | *received 40 bytes from x.x.x.x:500 on eth7.101
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | **parse ISAKMP Message:
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | initiator cookie:
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | a2 d5 6c 61 7b 1e dc 99
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | responder cookie:
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | d2 2c 0a 6f 55 31 9d c3
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | next payload type: ISAKMP_NEXT_N
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | ISAKMP version: ISAKMP Version 1.0
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | exchange type: ISAKMP_XCHG_INFO
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | flags: none
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | message ID: 00 00 00 00
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | length: 40
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | ICOOKIE: a2 d5 6c 61 7b 1e dc 99
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | RCOOKIE: d2 2c 0a 6f 55 31 9d c3
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | peer: 50 93 49 44
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | state hash entry 29
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | state object not found
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | ***parse ISAKMP Notification Payload:
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | next payload type: ISAKMP_NEXT_NONE
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | length: 12
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | DOI: ISAKMP_DOI_IPSEC
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | protocol ID: 1
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | SPI size: 0
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | Notify Message Type: NO_PROPOSAL_CHOSEN
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: packet from x.x.x.x:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | info:
2017:10:06-08:14:52 sanomed_bs-2 pluto[20894]: | next event EVENT_SA_SYNC_UPDATE in 11 seconds
2017:10:06-08:15:03 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:15:03 sanomed_bs-2 pluto[20894]: | *time to handle event
2017:10:06-08:15:03 sanomed_bs-2 pluto[20894]: | event after this is EVENT_RETRANSMIT in 29 seconds
2017:10:06-08:15:03 sanomed_bs-2 pluto[20894]: | inserting event EVENT_SA_SYNC_UPDATE, timeout in 15 seconds
2017:10:06-08:15:03 sanomed_bs-2 pluto[20894]: | next event EVENT_SA_SYNC_UPDATE in 15 seconds
2017:10:06-08:15:18 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:15:18 sanomed_bs-2 pluto[20894]: | *time to handle event
2017:10:06-08:15:18 sanomed_bs-2 pluto[20894]: | event after this is EVENT_RETRANSMIT in 14 seconds
2017:10:06-08:15:18 sanomed_bs-2 pluto[20894]: | inserting event EVENT_SA_SYNC_UPDATE, timeout in 15 seconds
2017:10:06-08:15:18 sanomed_bs-2 pluto[20894]: | next event EVENT_RETRANSMIT in 14 seconds for #2
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | *time to handle event
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | event after this is EVENT_SA_SYNC_UPDATE in 1 seconds
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | handling event EVENT_RETRANSMIT for x.x.x.x "xxxxxx" #2
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | inserting event EVENT_RETRANSMIT, timeout in 40 seconds for #2
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | next event EVENT_SA_SYNC_UPDATE in 1 seconds
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | *received 40 bytes from x.x.x.x:500 on eth7.101
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | **parse ISAKMP Message:
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | initiator cookie:
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | a2 d5 6c 61 7b 1e dc 99
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | responder cookie:
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | 2f ff 11 1e b9 dc ff db
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | next payload type: ISAKMP_NEXT_N
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | ISAKMP version: ISAKMP Version 1.0
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | exchange type: ISAKMP_XCHG_INFO
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | flags: none
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | message ID: 00 00 00 00
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | length: 40
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | ICOOKIE: a2 d5 6c 61 7b 1e dc 99
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | RCOOKIE: 2f ff 11 1e b9 dc ff db
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | peer: 50 93 49 44
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | state hash entry 8
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | state object not found
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | ***parse ISAKMP Notification Payload:
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | next payload type: ISAKMP_NEXT_NONE
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | length: 12
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | DOI: ISAKMP_DOI_IPSEC
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | protocol ID: 1
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | SPI size: 0
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | Notify Message Type: NO_PROPOSAL_CHOSEN
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: packet from x.x.x.x:500: ignoring informational payload, type NO_PROPOSAL_CHOSEN
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | info:
2017:10:06-08:15:32 sanomed_bs-2 pluto[20894]: | next event EVENT_SA_SYNC_UPDATE in 1 seconds
2017:10:06-08:15:33 sanomed_bs-2 pluto[20894]: |
2017:10:06-08:15:33 sanomed_bs-2 pluto[20894]: | *time to handle event
2017:10:06-08:15:33 sanomed_bs-2 pluto[20894]: | event after this is EVENT_RETRANSMIT in 39 seconds
2017:10:06-08:15:33 sanomed_bs-2 pluto[20894]: | inserting event EVENT_SA_SYNC_UPDATE, timeout in 15 seconds
2017:10:06-08:15:33 sanomed_bs-2 pluto[20894]: | next event EVENT_SA_SYNC_UPDATE in 15 seconds
 
Danke im voraus.


This thread was automatically locked due to age.