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

    BRIGDE - Version 2.0

    Routing and Multi WAN
    2
    6
    2.0k
    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
      Padua
      last edited by

      Dear Colleagues,

      I need to make a bridge between the rl0 (wireless network) and rl2 (wired network). I went to the web GUI option: Interfaces -> (assign) click on Bridges tab, click on "+" to add the bridge and did the addition of the brigde, however it is not run, can not ping from one network to another.

      The addition of the bridge is only with this procedure? Or more must be done some other setting?
      I'm using version 2.0 RC1

      Thanks.

      1 Reply Last reply Reply Quote 0
      • GruensFroeschliG
        GruensFroeschli
        last edited by

        You also need to create firewall rules to actually allow traffic.

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

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

          And how would this rule?

          See the addresses:

          rl0 192.168.15.1

          rl2 192.168.1.254

          1 Reply Last reply Reply Quote 0
          • GruensFroeschliG
            GruensFroeschli
            last edited by

            In a bridged setup you have the same subnet on both interfaces.
            You have two different subnets.

            Set a static IP on the wired interface.
            Don't set an IP on the wireless interface.

            Make sure you have a DHCP running on either the wired interface on pfSense itself or on some other device on the wired side.

            For firewall rules:
            Create to start on both interfaces an "allow any to any" rule.
            After you have this working, you can make a more restrictive ruleset.

            We do what we must, because we can.

            Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

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

              Friend thanks for your interest.

              But in this particular case, what was missing was just between the subnet's gateway RL2 - 192.168.1.254.
              GW 192.168.1.1
              I added it there tab Interfaces -> Static IP configuration
              Now is running cool.
              No need for additional rules.

              Thanks.

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

                A correction!

                After insertion is possible to ping the gateway on this subnet, but to use devices (like print on a printer) is indeed necessary to insert a rule like the friend had earlier reported.

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