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

    Multiple Subnets not browseable

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 543 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.
    • SLIMaxPowerS
      SLIMaxPower
      last edited by

      This is my setup.

      Modem 192.168.0.254 (WAN)–- Network Appliance (PFSense) 192.168.2.1/24

      |                              |                  |                        |
                                                    LAN1                        LAN2            LAN3                LAN4

      |                                |                  |                          |
                                  subnet 192.168.2.* /24        192.168.1.*/24    unused                unused

      |                                |
                                              unmanaged switch      unmanaged switch

      Both subnets can browse the internet.

      I can ssh from 192.168.1.* into servers on 192.168.2.*

      I can't browse network shares on 192.168.2.* from 192.168.1.* on Windows PC's and vice-versa.

      Both LAN interfaces don't have an Upstream Gateway set.

      Both LAN interfaces don't block Reserved Networks.

      First Firewall Rule for 192.168.2.* passes any protocol from 192.168.2.* LAN net to 192.168.1.* LAN net

      Allow IP options are passed due to running multicast traffic for DMX\Pixel controllers running.

      First Firewall Rule for 192.168.1.* passes any protocol from 192.168.1.* LAN net to 192.168.2.* LAN net.

      What do I need to do to allow network shares visible on 192.168.1.*

      I will be adding another subnet soon and replacing the switches with managed switches, so things will get a little more complicated.

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

        Windows network "browsing" requires something to overcome the lack of broadcasts since broadcasts do not cross subnets. You should be able to connect using \ip.add.re.ss\sharename.

        You can probably get away with setting DNS names for your internal hosts. Running DNS on an active directory domain controller fixes all of this right up.

        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
        • SLIMaxPowerS
          SLIMaxPower
          last edited by

          ipadress sharename worked. good enough for me. cheers

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