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

    [pfSense 2.0/AMD64] VPN Problems and Questions

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    2 Posts 1 Posters 1.4k Views
    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.
    • T
      TuxBrother
      last edited by

      Hello Hard-Coders.

      PPTP VPN is working on the latest Beta4 AMD64 snapshot correctly. When it comes to NAT-T L2TP IPSec, I got problems. I've correctly forwarded all the ports and protocols, but on connect I get the error attached. It is very strange, because the IPSec log stays empty. Is there any way to detect if my ISP (Ziggo, The Netherlands) blocks the L2TP IPsec traffic?

      Also, is there a way to make all users created within the user manager, access to VPN dailin? And, why I can't use special characters in L2TP passwords? It is less secure.

      Thanks for your support.

      screen789.png_thumb
      screen789.png

      1 Reply Last reply Reply Quote 0
      • T
        TuxBrother
        last edited by

        No one?

        Never mind, I am migrating to an external computer. Not a VM. It has only one NIC, so I added a USB NAD. It gets recognised. (ADMTek USB To Ethernet)

        In the internal setup, I must make the link up. Here is the error message:

        Please connect the WAN interface and make sure the link is up blabla.
        ue0: Link state changed to UP
        <enter>No link-up detected

        Please connect the WAN interface and make sure the link is up blabla.

        I thought: wtf?

        For exclamation, the WAN interface must be on the slowest (USB, 100Mbit) ethernet card.

        Although, when I connect the WAN to the onboard network card (Gigabit), it gets recognised successfully.

        It is the AMD64 pfSense 2.0 BETA4 2010-11-25 1721 build.

        How do I shoot this problem?
        Thanks!</enter>

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.