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

    Bridging two networks

    General pfSense Questions
    3
    4
    732
    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.
    • M
      Mascot
      last edited by

      I'm trying to create a bridge between two LAN networks. But when I assign BRIDGE0 to "LAN" interface it becomes inaccessible.

      What I did so far:

      1. As suggested in pfSense documentation, I set net.link.bridge.pfil_member to 0 and net.link.bridge.pfil_bridge to 1.
      2. IP configuration of OPT1 interface set to none.
      3. Created BRIDGE0 and added OPT1 there.
      4. Assigned BRIDGE0 to "LAN" interface.

      At this point "LAN" becomes inaccessible. I also tried adding OPT2 to the BRIDGE0, but result is same.

      "LAN" has "Static IPv4" configuration and it works fine as long as it has something different than bridge assigned to it.

      Please help me figure out what I'm doing wrong.

      V DerelictD 2 Replies Last reply Reply Quote 0
      • V
        viragomann @Mascot
        last edited by

        @mascot said in Bridging two networks:

        Assigned BRIDGE0 to "LAN" interface.

        ?

        So I assume you have a setup with LAN configured and accessing the web configurator via LAN.

        I had the same situation and did it with these steps:

        • Assigned the OPTx interface to a network port and enabled it.
        • Added the bridge (BRIDGE0) and added the members LAN and OPTx to it.
        • Added a new Interface (OPTy) with BRIDGE0 as network port and enabled it.

        As far as I know a restart was necessary after that to get it work.

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

          @mascot said in Bridging two networks:

          What I did so far:

          As suggested in pfSense documentation, I set net.link.bridge.pfil_member to 0 and net.link.bridge.pfil_bridge to 1.
          IP configuration of OPT1 interface set to none.
          Created BRIDGE0 and added OPT1 there.
          Assigned BRIDGE0 to "LAN" interface.

          At this point "LAN" becomes inaccessible. I also tried adding OPT2 to the BRIDGE0, but result is same.

          Did you then move your management device to OPT1? That would be the only port on "LAN" at that point.

          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 1
          • M
            Mascot
            last edited by Mascot

            @viragomann said in Bridging two networks:

            So I assume you have a setup with LAN configured and accessing the web configurator via LAN.
            As far as I know a restart was necessary after that to get it work.

            I tried both - accessing from this "LAN" interface and from other interface. I also tried assigning bridge to "OPT2" instead of "LAN" as you suggest and did reboot pfSense, but that didn't help.


            @derelict said in Bridging two networks:

            Did you then move your management device to OPT1? That would be the only port on "LAN" at that point.

            Yes, it supposed to be accessible via 192.168.1.x, but I can't access nor ping it.

            Could problem be that one of these two LAN networks is at virtual port (between pfSense VM and host machine)? I also tried adding only 1 physical port to this bridge, but still can't access it.

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