Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Bridge Interfaces L2 problem

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    6 Posts 4 Posters 240 Views 4 Watching
    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.
    • A Offline
      Alex 4
      last edited by

      hi . i have the folioing problem in Bridge Interfaces .
      1 have the master interface OP1 and the connect Bridge Interfaces OP2
      all work OK until i disconnect the cable from OP1 and OP1 port go down then i lost the L2 from OP2 !!!!!!!
      did anybody now how i can pass this problem ????

      luckman212L 1 Reply Last reply Reply Quote 0
      • luckman212L Offline
        luckman212 LAYER 8 @Alex 4
        last edited by

        Did you create your bridge by adding OPT1 and OPT2 interfaces to it, and then going back to Interfaces > add the BRIDGE0 interface, enable it and then move your IP config to the BRIDGE0 iface directly?

        I believe that's how it's supposed to be done, but some screenshots would help to clear this up…

        1 Reply Last reply Reply Quote 0
        • A Offline
          Alex 4
          last edited by

          HI again . i setup the master OP1 interface with the IP , i setup the second interface OP2 with no IP and then i add the first & second OP1 & 2 in the Bridge Interfaces section

          123789456.png

          patient0P 1 Reply Last reply Reply Quote 0
          • patient0P Online
            patient0 @Alex 4
            last edited by patient0

            @Alex-4 have a look at https://docs.netgate.com/pfsense/en/latest/bridges/interfaces.html#bridging-and-interfaces, especially this paragraph:

            "Configuring the IP address on the bridge itself is best in nearly all cases. The main reason for this is due to the fact that bridges are dependent on the state of the interface upon which the IP address is assigned. If the IP address for the bridge is configured on a member interface and that interface is down, the whole bridge will be down and no longer passing traffic. The most common case for this is a wireless interface bridged to an Ethernet LAN NIC. If the LAN NIC is unplugged, the wireless would be dead unless the IP address was configured on the bridge interface and not LAN. Another reason is that if limiters must be used for controlling traffic, then there must be an IP address on the bridge interface for them to work properly. Likewise, in order for Captive Portal or a transparent proxy to function on an internal bridge the IP address must be configured on the assigned bridge and not a member interface."

            The way your bridge it's configured at the moment what you see is expected.

            1 Reply Last reply Reply Quote 1
            • A Offline
              Ankalaev
              last edited by

              That explains the behavior. Since the IP is configured on OP1 instead of the bridge interface itself, the bridge depends on OP1 staying up. Moving the IP configuration to the BRIDGE interface should allow OP2 to keep passing traffic when OP1 goes down.

              1 Reply Last reply Reply Quote 0
              • A Offline
                Alex 4
                last edited by

                i see the problem now thanx for the replay .

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
                Privacy Policy · Cookie Policy