AFP548 Changing the world one server at a time.

invalid ID payload

Home › Forums › Archive › VaporSec › invalid ID payload

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #355627
    pmorelli
    Participant

    Ran across a problem trying to use VaporSec to connect two computers.

    First, my setup.

    One computer (A) behind a linksys wireless 4 port router.
    External IP A.A.A.A
    NAT IP 20.20.20.100

    Another computer (B) is behind an Airport Extreme base station.
    External IP B.B.B.B
    NAT IP 10.0.1.2

    Both routers have been updated to the latest firmware version, both computers are on 10.2.6, and both routers have ipsec passthrough enabled (well, the linksys does for sure, since it has a setting, but the base station doesn’t seem to have a setting. However, the specs say it has IPSec passthrough.)

    I use vapor sec with the following settings on each computer:
    Computer A
    Remote IPSec Device B.B.B.B
    Internal Network 10.0.1.0/24

    Computer B
    Remote IPSec Device A.A.A.A
    Internal Network 20.20.20.0/24

    I’ve made sure the shared secret is the same.

    When I try to connect from computer B to A (afp://20.20.20.100/, in Connect to Server), it times out. Looking at my system log on computer A, I have the following snippet, so I know they see each other…

    May 17 19:17:47 Peters-Computer racoon: INFO: isakmp.c:891:isakmp_ph1begin_r(): respond new phase 1 negotiation: 20.20.20.100[500]<=>B.B.B.B[500]
    May 17 19:17:47 Peters-Computer racoon: INFO: isakmp.c:896:isakmp_ph1begin_r(): begin Identity Protection mode.
    May 17 19:17:47 Peters-Computer racoon: INFO: vendorid.c:128:check_vendorid(): received Vendor ID: KAME/racoon
    May 17 19:17:48 Peters-Computer racoon: ERROR: ipsec_doi.c:2968:ipsecdoi_checkid1(): Expecting IP address type in main mode, but User_FQDN.
    May 17 19:17:48 Peters-Computer racoon: ERROR: isakmp_ident.c:1216:ident_r3recv(): invalid ID payload.
    May 17 19:19:47 Peters-Computer racoon: ERROR: isakmp.c:1434:isakmp_ph1resend(): phase1 negotiation failed due to time up. 22684f0c96240405:5646022048c0021d

    What is an invalid ID payload? Am I doing everything correctly? Any ideas on how to fix this?

    –pete

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.