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

    [SOLVED] Public IP address has not changed

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 507 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
      simon_lefisch
      last edited by simon_lefisch

      Hello everyone,

      I'm hoping someone can help/explain why I am receiving the error message below:

      Screen Shot 2020-02-03 at 1.50.45 PM.jpg

      I have setup my VPN and connect to it fine, however if I do not have "Redirect IPv4 Gateway Force all client-generated IPv4 traffic through the tunnel" enabled I get that error. If enabled on pfSense or in Viscosity, no error message. I would prefer to have IPv4 traffic destined for my home network to be routed thru the tunnel and any other traffic to not go thru the tunnel. What am I missing? If you need any other info, let me know and I will gladly post.

      BTW, I have DNS servers for the VPN server set as the IP address of my pfSense and also 8.8.8.8 as the second DNS server. If I have 8.8.8.8 set as the second DNS server, I cannot ping any of the hosts on my LAN. When 8.8.8.8 is removed, I can ping hosts. Thanks for any info/help you can provide.

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @simon_lefisch
        last edited by

        @simon_lefisch said in Public IP address has not changed:

        however if I do not have "Redirect IPv4 Gateway Force all client-generated IPv4 traffic through the tunnel" enabled I get that error.

        So it does what you told it to do.
        Not all traffic gets directed to the tunnel. The test you showed didn't take the tunnel, and thus it shwos a warning (is not an error).

        @simon_lefisch said in Public IP address has not changed:

        I would prefer to have IPv4 traffic destined for my home network to be routed thru the tunnel and any other traffic to not go thru the tunnel. What am I missing?
        Your missing "the test to check your apparent public IP" did not take the tunnel.
        If it would know that behind the tunnel another gateway is available, and using that one will show another IP for sure ...
        ( don't ask me how to do so .... I'm just "Redirect IPv4 / IPv6 Gateway force .... " and call it a day )

        As long as you can access your home network - and access the Internet without using the VPN connection to home - then all is well, right ?

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        S 1 Reply Last reply Reply Quote 0
        • S
          simon_lefisch @Gertjan
          last edited by

          @Gertjan you are correct. I will just set everything to go thru the tunnel and be done with it. Thanks for pointing these things out.

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