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

    Route TCP/IP from Admin VLAN10 to VLAN20

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    5 Posts 2 Posters 502 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.
    • P
      paulnlynda
      last edited by

      I have several VLANs running on pfSense SG3100 and all are working fine. However, I would like to have the ability to use one of the VLANs as an administrator of the whole network. I have the free program Veyon which I use in several classrooms. However, they only seem to work within their own VLAN. Veyon uses TCP/IP to do its magic.
      I can currently Ping from Admin VLAN10 to VLAN 20, but cannot use Veyon to control computers from VLAN10 to VLAN20.

      My question is: how do I set up routing between VLANs so TCP works as needed?
      I looked into static routing, but when attempting to connect VLAN10GW to the IP of VLAN20 it errors indicating that it exists within VLAN20...

      Any help would be appreciated.

      JKnottJ 1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott @paulnlynda
        last edited by

        @paulnlynda

        Routing between networks connected to pfsense is already there. However, you have to create rules to allow the traffic as required. You create the rules on the source network to allow where you want to go.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        1 Reply Last reply Reply Quote 0
        • P
          paulnlynda
          last edited by

          If ping is working and my pass rule is not exclusive to ICMP, why isn't my TCP/IP passing?

          JKnottJ 1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott @paulnlynda
            last edited by

            @paulnlynda

            If ping works, it's not a routing issue. That leaves rules. Post a screen shot of yours.

            PfSense running on Qotom mini PC
            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
            UniFi AC-Lite access point

            I haven't lost my mind. It's around here...somewhere...

            1 Reply Last reply Reply Quote 0
            • P
              paulnlynda
              last edited by

              Found the answer was in how the host was identified in Veyon. Instead of the hostname, I had to use its static IP address. Now all working. Thanks.

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