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

    VPN Client - IPv4 select but interface doesn't support - bug?

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 995 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
      torontob
      last edited by

      Hi everyone,

      If I just installed a box and add my config backup it, I get Interface doesn't support IPv4 (referring to WAN interface). This happens when setting up OpenVPN client. The reason for this is that pfSense is not connected to internet yet. This is not good because you can't configure the box offline. Is this a bug?

      Thanks,

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Do you have the WAN set to "none" or DHCP or some other type?

        If you have it set to "none" then the message is correct. If it's set to DHCP that should still allow you to configure it even if DHCP doesn't yet have an IP.

        If you don't want to set DHCP, just put a dummy IP on the interface and switch it before taking it live.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

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

          @jimp:

          Do you have the WAN set to "none" or DHCP or some other type?

          If you have it set to "none" then the message is correct. If it's set to DHCP that should still allow you to configure it even if DHCP doesn't yet have an IP.

          If you don't want to set DHCP, just put a dummy IP on the interface and switch it before taking it live.

          Thanks for the input.
          It is set to DHCP and using only IPv4. IPv6 is set to None. Could that be causing all these issues? I don't think so because when I allow the router to obtain DHCP on IPv4 then the problem is gone. Please test on your end. This is most likely a bug.

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