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

ASG120 an Kabel-BW Zugang

Hallo beisammen,

kann mir evtl. jemand weiterhelfen? 

Und zwar geht es um die integration einer ASG120 an einem Kabel-BW Anschluß.

Hat hier schon jemand Erfahrungen und was gibt es evtl. hier zu beachten?


This thread was automatically locked due to age.
Parents
  • Folgendes sagt das Log. Vom iPad aus wollte ich die Verbindung aufbauen.
    Es scheint als wäre DynDNS schon richtig informiert. Sonst würde ich ja gar nicht hier ankommen.

    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: received Vendor ID payload [RFC 3947]
    
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [4df37928e9fc4fd1b3262170d515c662]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [8f8d83826d246b6fc7a8a6a428c11de8]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [439b59f8ba676c4c7737ae22eab8f582]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [4d1e0e136deafa34c4f3ea9f02ec7285]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [80d0bb3def54565ee84645d4c85ce3ee]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [9909b64eed937c6573de52ace952fa6b]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [FRAGMENTATION 80000000]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: received Vendor ID payload [Dead Peer Detection]
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[11] 80.187.104.69 #6: responding to Main Mode from unknown peer 80.187.104.69
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[11] 80.187.104.69 #6: NAT-Traversal: Result using RFC 3947: both are NATed
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[11] 80.187.104.69 #6: ignoring informational payload, type IPSEC_INITIAL_CONTACT
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[11] 80.187.104.69 #6: Peer ID is ID_IPV4_ADDR: '10.157.126.106'
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69 #6: deleting connection "S_for jj"[11] instance with peer 80.187.104.69 {isakmp=#0/ipsec=#0}
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69 #6: Dead Peer Detection (RFC 3706) enabled
    2013:05:07-15:45:18 auge007 pluto[19241]: | NAT-T: new mapping 80.187.104.69:500/3744)
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sent MR3, ISAKMP SA established
    2013:05:07-15:45:19 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: cannot respond to IPsec SA request because no connection is known for 5.56.210.73/32===192.168.178.22:4500[192.168.178.22]:17/1701...80.187.104.69:3744[10.157.126.106]:17/%any==={10.157.126.106/32}
    2013:05:07-15:45:19 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_ID_INFORMATION to 80.187.104.69:3744
    2013:05:07-15:45:22 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:22 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:25 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:25 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:28 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:28 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:31 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:31 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:34 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:34 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:37 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:37 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:40 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:40 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:43 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:43 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:46 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:46 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:49 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: received Delete SA payload: deleting ISAKMP State #6
    2013:05:07-15:45:49 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744: deleting connection "S_for jj"[12] instance with peer 80.187.104.69 {isakmp=#0/ipsec=#0}
Reply
  • Folgendes sagt das Log. Vom iPad aus wollte ich die Verbindung aufbauen.
    Es scheint als wäre DynDNS schon richtig informiert. Sonst würde ich ja gar nicht hier ankommen.

    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: received Vendor ID payload [RFC 3947]
    
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [4df37928e9fc4fd1b3262170d515c662]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [8f8d83826d246b6fc7a8a6a428c11de8]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [439b59f8ba676c4c7737ae22eab8f582]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [4d1e0e136deafa34c4f3ea9f02ec7285]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [80d0bb3def54565ee84645d4c85ce3ee]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [9909b64eed937c6573de52ace952fa6b]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: ignoring Vendor ID payload [FRAGMENTATION 80000000]
    2013:05:07-15:45:18 auge007 pluto[19241]: packet from 80.187.104.69:500: received Vendor ID payload [Dead Peer Detection]
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[11] 80.187.104.69 #6: responding to Main Mode from unknown peer 80.187.104.69
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[11] 80.187.104.69 #6: NAT-Traversal: Result using RFC 3947: both are NATed
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[11] 80.187.104.69 #6: ignoring informational payload, type IPSEC_INITIAL_CONTACT
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[11] 80.187.104.69 #6: Peer ID is ID_IPV4_ADDR: '10.157.126.106'
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69 #6: deleting connection "S_for jj"[11] instance with peer 80.187.104.69 {isakmp=#0/ipsec=#0}
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69 #6: Dead Peer Detection (RFC 3706) enabled
    2013:05:07-15:45:18 auge007 pluto[19241]: | NAT-T: new mapping 80.187.104.69:500/3744)
    2013:05:07-15:45:18 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sent MR3, ISAKMP SA established
    2013:05:07-15:45:19 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: cannot respond to IPsec SA request because no connection is known for 5.56.210.73/32===192.168.178.22:4500[192.168.178.22]:17/1701...80.187.104.69:3744[10.157.126.106]:17/%any==={10.157.126.106/32}
    2013:05:07-15:45:19 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_ID_INFORMATION to 80.187.104.69:3744
    2013:05:07-15:45:22 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:22 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:25 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:25 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:28 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:28 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:31 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:31 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:34 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:34 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:37 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:37 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:40 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:40 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:43 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:43 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:46 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x4f857fd9 (perhaps this is a duplicated packet)
    2013:05:07-15:45:46 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: sending encrypted notification INVALID_MESSAGE_ID to 80.187.104.69:3744
    2013:05:07-15:45:49 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744 #6: received Delete SA payload: deleting ISAKMP State #6
    2013:05:07-15:45:49 auge007 pluto[19241]: "S_for jj"[12] 80.187.104.69:3744: deleting connection "S_for jj"[12] instance with peer 80.187.104.69 {isakmp=#0/ipsec=#0}
Children
No Data