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

    VLANS and some other help

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 873 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.
    • O Offline
      oboi
      last edited by

      Hey everyone i have had pfsense for about 4ish months haven't really played around with it, i got a couple of packages(squid,snort) but that is it. I started studying for my net+ so i want to start messing around with pfsense currently i have no subnets or vlans but i wanted to organize my IP address's to make it "cleaner" I have a 16 port "smart" switch the D-Link DGS-1216T i do not think its layer 3 it can only setup vlans using 802.1q vlans https://gyazo.com/482e412b66f30211d6aba4fb27b883ac
      im trying to split up my ip address's using VLAN theres a guide i was reading over just wanted to know if this is how i should do it or if you guys can make it better
      currently ip's
      192.168.1.1 pfsense
      192.168.1.2 16 port switch
      192.168.1.3 freenas
      192.168.1.4 owncloud (package on freenas)
      192.168.1.5 Access point (i have an open NIC on my pfsense i was wondering if i should put the AP on the open NIC?)
      (192.168.1.10 I have fios parents still want VOD so i needed a ethernet to coax these 2 ip's
      192.168.1.11) are the two Set top boxes
      192.168.1.122 Ubuntu server (i would have had it at .6 but i had a package on freenas take that ip and my pfsense wont show me dhcp leases below 192.168.1.10 i opened the pool to show 192.168.1.1-192.168.1.254 but i cant release it so w/e)
      my idea was to set up vlans looking like this
      VLAN1 192.168.1.1-192.168.1.254
      pfsense 192.168.1.1
      switch 192.168.1.2
      current pc 192.168.1.100 (doesnt matter specifics just in the first vlan)
      VLAN10 192.168.10.1-192.168.11.1
      ubuntu server 192.168.10.2
      freenas 192.168.10.3
      all packages just +.1 after the freenas ip
      VLAN20 192.168.20.1-192.168.20.254
      wireless printer 192.168.20.2
      AP 192.168.20.3
      all clients using AP get VLAN20 range

      i have been basing my idea of this website
      https://www.iceflatline.com/2013/09/how-to-create-and-configure-vlans-in-pfsense/
      sorry if this is in the wrong section or if it reads like gibberish
      but thanks in advance
      if you guys need any more info just ask i can post pics or explain things better

      1 Reply Last reply Reply Quote 0
      • johnpozJ Offline
        johnpoz LAYER 8 Global Moderator
        last edited by

        sure that should work.

        As to trunk depends on how many interfaces you have in pfsense?  If your going to connect a port from switch that is in in each vlan on switch you don't even need to setup vlans on pfsense, only the interfaces.  your switch is doing all the vlan stuff.

        If you only have 1 interface in pfsense and are going to create the vlans on that physical interface, then yes you need a trunk to that interface from your switch and pfsense will figure out what packets are what based on the tags.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 25.07.1 | Lab VMs 2.8, 25.07.1

        1 Reply Last reply Reply Quote 0
        • O Offline
          oboi
          last edited by

          @johnpoz:

          sure that should work.

          As to trunk depends on how many interfaces you have in pfsense?  If your going to connect a port from switch that is in in each vlan on switch you don't even need to setup vlans on pfsense, only the interfaces.  your switch is doing all the vlan stuff.

          If you only have 1 interface in pfsense and are going to create the vlans on that physical interface, then yes you need a trunk to that interface from your switch and pfsense will figure out what packets are what based on the tags.

          i have 3 interfaces
          wan ( connected to my ONT/modem)
          lan (switch is connected to this one)
          opt1( nothing connected just an extra NIC card i had)
          Sorry im not fully grasping what your saying i plan on having 3 vlans on my switch unless i can connect my AP to my OPT1 and have that be its own VLAN type of thing then i will only have 2 vlans on my switch. what i picked up is if i connect a ethernet cable in each of my vlans to its own interface on pfsense then i dont need to configure VLANS on pfsense but if i plan to only use one cable from my Pfsense to my switch then i do need to trunk the VLANS?

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