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

    VLAN 100 to use different WAN

    Scheduled Pinned Locked Moved Routing and Multi WAN
    4 Posts 2 Posters 677 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.
    • M
      MikeKulls
      last edited by

      I have 4 interfaces defined in pfSense,
      LAN - standard LAN interface running DHCP
      VLAN100 - vlan interface sitting on top of LAN also running DHCP
      WAN - standard WAN interface connected to cable modem
      OpenVPN - an open VPN client interface that connects through the WAN port to a VPN server in the US

      I can get all traffic from the LAN to go through the VPN and also all traffic from the VLAN100 interface to go through the VPN. What I would like to do is have all traffic for the LAN exit via the WAN and not via the VPN connection. This way if I want to use the VPN I can just connect to a port on the switch that is configured for vlan 100. Does that make sense?

      Thanks for reading

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        You probably want to check Don't pull routes in the VPN client connection. That will stop you from pulling a default route from the VPN provider allowing you to selectively use policy routing to send only selected traffic over the VPN.

        https://doc.pfsense.org/index.php/What_is_policy_routing

        https://doc.pfsense.org/index.php/Bypassing_Policy_Routing

        There are already lots of threads about doing this.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • M
          MikeKulls
          last edited by

          Thanks, I will give it a try.

          1 Reply Last reply Reply Quote 0
          • M
            MikeKulls
            last edited by

            hmmm, well that work. Little easier than I expect :-) Thanks for your help

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