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

OpenVPN interface won't get IPv4 Virtual Address

Scheduled Pinned Locked Moved OpenVPN
2 Posts 1 Posters 140 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.
  • S
    sparkman123
    last edited by sparkman123 Feb 15, 2025, 11:24 PM Feb 15, 2025, 11:20 PM

    I'm trying to utilize an interface derived from connected OpenVPN client. In this case, it is called OPT1.

    When I try assign it as an outgoing interface for services like squid, I get an error "The Outgoing Network Interface must have an IPv4 address."

    When I look at the status of the connection via OpenVPN status (Status -> OpenVPN , I see a virtual address, however, when I look at the status of interfaces (Status -> Interfaces) I see the OPT1 interface but I only see an IPv6 address, no IPv4 virtual address.

    virtual ip 272jpg.jpg

    This behavior is different than older versions of pfSense. When I look at my older install of pfSense 2.4.5, the Status ->Interfaces show an IPv4 virtual address.

    virtual ip 245jpg.jpg

    How do I get the IPv4 to be "seen" by the Interface Status (thereby have be seen by services)?

    1 Reply Last reply Reply Quote 0
    • S
      sparkman123
      last edited by Feb 16, 2025, 2:50 AM

      So I figured it out. You need to go to Interfaces -> WAN and set "IPv6 Configuration Type" from "DHCP6" to "None" and then reboot pfSense. When rebooted, the interface now has an IPv4 virtual address when you look at interface status that you can bind to and use.

      1 Reply Last reply Reply Quote 0
      1 out of 2
      • First post
        1/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received