Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Netopia to Pfsense IPsec tunnel

    Scheduled Pinned Locked Moved
    IPsec
    2
    3
    2.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jcpolo
      last edited by

      I have read a little here and there about how people have been working on netopia to pfsense ipsec vpn tunnels but have not found a how to. I have tried just about everything to get the tunnel up and still cannot get it going.

      Equipment in question

      Netopia 3346 ENT
      Netopia 3386 ENT

      1 Reply Last reply Reply Quote 0
      • GruensFroeschliG
        GruensFroeschli
        last edited by

        http://forum.pfsense.org/index.php/topic,7001.0.html
        well a "little" bit more information is needed….

        what did you try.
        what did not work.
        the steps you took so far.
        etc.

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

        1 Reply Last reply Reply Quote 0
        • J
          jcpolo
          last edited by

          I tried setting up an aggressive tunnel with sha1, des, email address identifier, and shared key all matching… setup the subnets correctly on both sides. (same settings worked perfectly on my netscreen)

          I then tried main mode with the same settings as above.

          I tried aggressive with 3des, md5, as well as main mode with 3des, md5 all the other settings are the same. I get the same thing every time I save the ipsec information in the log file.

          Last 50 IPSEC log entries
          Jan 21 11:28:29 racoon: ERROR: configuration read failed
          Jan 21 11:28:29 racoon: ERROR: fatal parse failure (1 errors)
          Jan 21 11:28:29 racoon: ERROR: /var/etc/racoon.conf:5: "on" syntax error
          Jan 21 11:28:29 racoon: ERROR: not acceptable Identity Protection mode
          Jan 21 11:28:26 racoon: ERROR: failed to process packet.
          Jan 21 11:28:26 racoon: ERROR: failed to get valid proposal.
          Jan 21 11:28:26 racoon: ERROR: no suitable proposal found.
          Jan 21 11:28:26 racoon: ERROR: rejected hashtype: DB(prop#1:trns#1):Peer(prop#1:trns#1) = SHA:MD5
          Jan 21 11:28:26 racoon: WARNING: No ID match.
          Jan 21 11:28:26 racoon: INFO: begin Aggressive mode.
          Jan 21 11:28:26 racoon: [Marc Avila]: INFO: respond new phase 1 negotiation: 68.127.230.124[500]<=>71.243.199.124[500]
          Jan 21 11:28:25 racoon: ERROR: failed to process packet.
          Jan 21 11:28:25 racoon: ERROR: failed to get valid proposal.
          Jan 21 11:28:25 racoon: ERROR: no suitable proposal found.
          Jan 21 11:28:25 racoon: ERROR: rejected hashtype: DB(prop#1:trns#1):Peer(prop#1:trns#1) = SHA:MD5
          Jan 21 11:28:25 racoon: INFO: begin Aggressive mode.
          Jan 21 11:28:25 racoon: INFO: respond new phase 1 negotiation: 68.127.230.124[500]<=>75.6.178.20[500]
          Jan 21 11:28:22 racoon: ERROR: not acceptable Identity Protection mode
          Jan 21 11:28:20 racoon: ERROR: failed to process packet.
          Jan 21 11:28:20 racoon: ERROR: failed to get valid proposal.
          Jan 21 11:28:20 racoon: ERROR: no suitable proposal found.
          Jan 21 11:28:20 racoon: ERROR: rejected hashtype: DB(prop#1:trns#1):Peer(prop#1:trns#1) = SHA:MD5
          Jan 21 11:28:20 racoon: INFO: begin Aggressive mode.
          Jan 21 11:28:20 racoon: INFO: respond new phase 1 negotiation: 68.127.230.124[500]<=>68.238.74.36[500]
          Jan 21 11:28:18 racoon: ERROR: failed to process packet.
          Jan 21 11:28:18 racoon: ERROR: failed to get valid proposal.
          Jan 21 11:28:18 racoon: ERROR: no suitable proposal found.
          Jan 21 11:28:18 racoon: ERROR: rejected hashtype: DB(prop#1:trns#1):Peer(prop#1:trns#1) = SHA:MD5
          Jan 21 11:28:18 racoon: INFO: begin Aggressive mode.
          Jan 21 11:28:18 racoon: INFO: respond new phase 1 negotiation: 68.127.230.124[500]<=>66.189.169.99[500]
          Jan 21 11:28:14 racoon: ERROR: not acceptable Identity Protection mode
          Jan 21 11:28:10 racoon: ERROR: failed to process packet.
          Jan 21 11:28:10 racoon: ERROR: failed to get valid proposal.
          Jan 21 11:28:10 racoon: ERROR: no suitable proposal found.
          Jan 21 11:28:10 racoon: ERROR: rejected hashtype: DB(prop#1:trns#1):Peer(prop#1:trns#1) = SHA:MD5
          Jan 21 11:28:10 racoon: INFO: begin Aggressive mode.
          Jan 21 11:28:10 racoon: INFO: respond new phase 1 negotiation: 68.127.230.124[500]<=>75.6.178.20[500]
          Jan 21 11:28:07 racoon: ERROR: not acceptable Identity Protection mode
          Jan 21 11:28:07 racoon: INFO: unsupported PF_KEY message REGISTER
          Jan 21 11:28:05 racoon: ERROR: failed to process packet.
          Jan 21 11:28:05 racoon: ERROR: failed to get valid proposal.
          Jan 21 11:28:05 racoon: ERROR: no suitable proposal found.
          Jan 21 11:28:05 racoon: ERROR: rejected hashtype: DB(prop#1:trns#1):Peer(prop#1:trns#1) = SHA:MD5
          Jan 21 11:28:05 racoon: INFO: begin Aggressive mode.
          Jan 21 11:28:05 racoon: INFO: respond new phase 1 negotiation: 68.127.230.124[500]<=>68.238.74.36[500]
          Jan 21 11:28:05 racoon: INFO: unsupported PF_KEY message REGISTER
          Jan 21 11:28:03 racoon: ERROR: failed to process packet.
          Jan 21 11:28:03 racoon: ERROR: failed to get valid proposal.
          Jan 21 11:28:03 racoon: ERROR: no suitable proposal found.
          Jan 21 11:28:03 racoon: ERROR: rejected hashtype: DB(prop#1:trns#1):Peer(prop#1:trns#1) = SHA:MD5

          1 Reply Last reply Reply Quote 0
          • First post
            Last post