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

    VLAN wont Ping to Internet

    Scheduled Pinned Locked Moved Firewalling
    3 Posts 2 Posters 742 Views 2 Watching
    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.
    • N Offline
      nosenseatall
      last edited by

      Good Saturday to All -

      I was hoping to be past some of these beginner questions at this point, but I'm just not there yet.

      So, on my pfSense setup I have a VLAN (VLAN_50_IoT) in place that works fine and will ping internally as well as to the internet. It is using the LAN as the parent interface. But recently I tried creating a new VLAN (VLAN_TEST) just as I always do. I create it in interfaces, enable it, initially create an allow all firewall rule, and set up dhcp for it, and it doesn't work. Even though the settings appear to be exactly the same,as VLAN_50_IoT, other than VLAN_50_IoT is routed out to the Internet over VPN.

      My question is, at this point shouldn't I be able to use the pfSense ping tool and ping from the new vlan outside to the internet? I'm not sure if I inadvertently changed a setting somewhere, but I can't get any new vlans to reach the outside world.

      Thanks for any suggestions or help!!

      Here are some screenshots of the current setup:

      Screen Shot 2022-04-02 at 10.44.25 AM.png

      Screen Shot 2022-04-02 at 10.42.06 AM.png

      Screen Shot 2022-04-02 at 10.42.32 AM.png

      Screen Shot 2022-04-02 at 10.42.50 AM.png

      This screenshot doesn't show the bottom half because nothing is selected or entered anywhere below.

      Screen Shot 2022-04-02 at 10.43.45 AM.png

      N 1 Reply Last reply Reply Quote 0
      • N Offline
        nosenseatall @nosenseatall
        last edited by

        Figured out what the problem was for any folks that have this problem in the future.

        Somehow my NAT selection mysteriously switched from Hybrid to Manual.

        mytsuuM 1 Reply Last reply Reply Quote 0
        • mytsuuM Offline
          mytsuu @nosenseatall
          last edited by

          Hi @nosenseatall Yeah! outbound NAT are essential to allow packets between WAN ~ LAN (VLAN) interfaces.

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