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

    Public IP on WAN is VPN IP

    Scheduled Pinned Locked Moved
    Routing and Multi WAN
    1
    1
    533
    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.
    • W
      wificalling
      last edited by

      Hi Guys,

      I have got along to almost complete my setup with the help of this forum. Thanks a lot. This specific problem I did not find a solution for so far

      Simple setup:

      Multiple WAN: 1 WAN ( comcast) ( default gateway) , 1 VPN ( torGuard)
      One LAN: 192.168.10.1/24

      Set up firewall alias/rules to route specific clients via vpn gateway.
      Verified it by:
      Traceroute on Wan routed (default) clients go through comcast
      Traceroute on VPN routed clients go through TG servers

      Installed Squid -  Interface LAN, Transparent Interface as LAN
      The routing works just as mentioned above verified with traceroute.
      Problem:
      All the clients routed through WAN(comcast) now have the VPN's public IP though the traceroute shows its going through comcast servers.

      Any help is appreciated.

      PS: When squid disabled : VPN routed clients get VPN public ip, WAN routed clients get WAN ip.
      All public ip's verified by 'wget http://ipinfo.io/ip -qO -' in the clients terminal
      All traceroutes are 'traceroute www.google.com'

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