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

A coupe routing questions.

Scheduled Pinned Locked Moved Firewalling
5 Posts 3 Posters 734 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.
  • L
    lovingHDTV
    last edited by Dec 17, 2017, 1:32 PM

    I'm trying to take the next step on isolating guests and IOT devices from my LAN network.  I attached a picture of what I'm trying to accomplish.  Today I have it all working, except for the WAP device and being able to access Guest and IOT from LAN.  Today the WAP device is just plugged into port 2, so it is all tagged as VLAN Guest.

    Now I'd like to do a couple things.

    1. how do I see everything on Guest and IOT from LAN?  I did put in a firewall rule on both Guest and IOT to allow any connections that are not of destination LAN, so that keeps Guest and IOT traffic off LAN.  I then did allow access to my PLEX server from those two networks.  However, I cannot see anything on those networks from LAN.  How do I add this?  I thought I had read that with pfSense that should happen automatically?

    2. I'd also like to add the multiple SSIDs to the WAP and get them working.  I know how to setup the WAP with the SSIDs and get them tagged, but I'm just not sure what I need to do with port 8.  Is it as simple as adding port 8 to the Guest and IOT VLAN definition and mark it as a tagged port?  My expectation would be that all packets to the WAP will be tagged either 2, 10 coming in and everything else will get the default 1 (This would be the PVID setting I set for port 8).

    thanks,
    david

    network_setup.JPG
    network_setup.JPG_thumb

    1 Reply Last reply Reply Quote 0
    • J
      johnpoz LAYER 8 Global Moderator
      last edited by Dec 17, 2017, 2:27 PM

      Why are you tagging 1 to lan of pfsense?

      I would assume you have your lan interface native interface set to 192.168.1.x/24
      Then on this physical interface of pfsense you have vlan 10 and 2 setup..

      So port 1 of your switch would tag 10 and 2, and 1 would be untagged.  Then the same setup would be on your port 8 to your AP..

      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 24.11 | Lab VMs 2.8, 24.11

      1 Reply Last reply Reply Quote 0
      • L
        lovingHDTV
        last edited by Dec 17, 2017, 9:31 PM

        The only way to get my TP-Link switch to work, was to set port 1 as a tagged port within each VLAN.  The switch then tags any egress data from port 1 with the appropriate VLAN ID.  I can verify this works using tcpdump.

        For now I have a device plugged directly into port 4, so the packets coming in port 4 and leaving port 1 get tagged with VLAN 10.  Additionally I also have the WAP with only 1 SSID (Guest).  It is plugged into port 2 and when it leave port 1 get tagged with VLAN 2.

        I now want to add wireless access to VLAN IOT because I'm getting a wireless thermostat installed.  So I need to add the additional SSIDs to the WAP and get them hooked up to the switch correctly.

        One way is to have each SSID on the WAP be directed out a dedicated port on the WAP and then connect the WAP to the switch with three cables, but that takes a lot of ports.  I was hoping to be able to maintain a single connection between the WAP and the switch.  I'm just not sure how to do it.

        david

        1 Reply Last reply Reply Quote 0
        • D
          Derelict LAYER 8 Netgate
          last edited by Dec 17, 2017, 10:06 PM

          Good ole tp-link

          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
          • J
            johnpoz LAYER 8 Global Moderator
            last edited by Dec 17, 2017, 10:44 PM

            That is a tp-link 108e… Yeah get a different switch... Those are utter crap, they do not actually do vlans... Evey port has vlan 1 on it..

            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 24.11 | Lab VMs 2.8, 24.11

            1 Reply Last reply Reply Quote 0
            5 out of 5
            • First post
              5/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received