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

    Problems setting up a bridge?

    Scheduled Pinned Locked Moved General pfSense Questions
    7 Posts 5 Posters 750 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.
    • C
      captain351
      last edited by

      I have managed to setup pfSense with a 4 port intel nic. I don't need all 4 ports so setup 3 ports as a bridge. It works fine but with one exception.

      When I first set it up I had my workstation and my nas each plugged into a port on the router. The problem started when I tried to connect to my nas. I could ping it and manually map it using the IP but was unable to browse the network. After pulling my hair out for a few days it finally had the thought to plug the workstation and nas to my switch and plug the switch into the router. It then worked prefect.

      All interfaces have a rule to pass all traffic both TCP and UDP. The netbios traffic should be UDP but appears to not be passing.

      Any ideas to solve this problem?

      NollipfSenseN V provelsP 3 Replies Last reply Reply Quote 0
      • NollipfSenseN
        NollipfSense @captain351
        last edited by NollipfSense

        @captain351 It sounds as if you needed a two-port NIC and a separate switch, maybe a smart managed 5 ports, new on eBay or Amazon for $34 or less...makes your life easier...

        pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
        pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

        1 Reply Last reply Reply Quote 0
        • V
          viragomann @captain351
          last edited by

          @captain351 said in Problems setting up a bridge?:

          The problem started when I tried to connect to my nas. I could ping it and manually map it using the IP but was unable to browse the network.

          What do you mean exactly?
          If you enter the UNC path of the NAS you see nothing?
          Or even the shares are not shown up automatically?

          Show your rules.

          C 1 Reply Last reply Reply Quote 0
          • C
            captain351 @viragomann
            last edited by

            @viragomann The shares don't show up automaticaly. For instance in windows if I try to view the network I can see nothing but the local machine. I can map a network drive using the ip address but if use the machine name it can not find that name and errors out.

            My server (NAS) has the same problem I had drives mapped for backup purposes. They worked before I changed everything over to pfSense and they work fine again when plugged into my switch. It stops working if anything is pluged into a bridge port.

            I thought of something else since the last post. I have tested all 3 bridge ports and they all work as the link to my switch. I thought the problem might be UDP related but DHCP works fine on all 3 bridge ports. the problem seems to be netbios traffic traveling between the bridge ports!

            V 1 Reply Last reply Reply Quote 0
            • provelsP
              provels @captain351
              last edited by provels

              @captain351 Could be wrong, but it sounds like you could use a crossover cable instead of a switch. 🤷

              Peder

              MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
              BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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

                @provels

                You are wrong. Crossovers are not needed with gigabit and newer 100 Mb interfaces.

                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
                • V
                  viragomann @captain351
                  last edited by

                  @captain351
                  So your devices are obviously using WINS for name resolution.

                  Why don't you move over to DNS?
                  Since you probably run a DHCP server on pfSense you can configure it to register the host names in the DNS server directly. So all devices would be able to resolve the host names.

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