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

    Bridge problem pfs 1.2.2

    General pfSense Questions
    3
    14
    4.1k
    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
      cmb
      last edited by

      VLAN bridging in 1.2.2 was broken with the bridging rewrite bug fix that fixed several other problems. It's fixed in the 1.2.3 snapshots.

      1 Reply Last reply Reply Quote 0
      • S
        ssbaksa
        last edited by

        @cmb:

        VLAN bridging in 1.2.2 was broken with the bridging rewrite bug fix that fixed several other problems. It's fixed in the 1.2.3 snapshots.

        This is production firewall. Can I safely use 1.2.3? Is it going 1.2.1 better or could I say safer way for now? 1.2 gave me big problems on this platform (Intel® Server Platform SR1530HCLR with added 1 Intel eth card + 2 GB RAM).

        Sasa

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

          As stated in http://blog.pfsense.org/?p=364 1.2.3 isn't ready for production environment. 1.2.2 is one you should use http://blog.pfsense.org/?p=351

          /Perry
          doc.pfsense.org

          1 Reply Last reply Reply Quote 0
          • S
            ssbaksa
            last edited by

            @Perry:

            As stated in http://blog.pfsense.org/?p=364 1.2.3 isn't ready for production environment. 1.2.2 is one you should use http://blog.pfsense.org/?p=351

            Hi Perry!
            I know that but working bridge is essential to this setup and one in 1.2.2 is broken as cmb stated so ???
            There is slim chance to go back to 1.2 having in mind this restart problem.

            Sasa

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

              You can change the following.
              @http://forum.pfsense.org/index.php/topic:

              The quick hack:
              /usr/local/www/interfaces_opt.php (you can open it and paste from Diagnostics -> Edit file)
              find
              $bridgecmd .= " addm $bridgeif stp $bridgeif ";
              and change it to
              $bridgecmd .= " addm $bridgeif ";
              save and reboot

              /Perry
              doc.pfsense.org

              1 Reply Last reply Reply Quote 0
              • S
                ssbaksa
                last edited by

                @Perry:

                You can change the following.
                @http://forum.pfsense.org/index.php/topic:

                The quick hack:
                /usr/local/www/interfaces_opt.php (you can open it and paste from Diagnostics -> Edit file)
                find
                $bridgecmd .= " addm $bridgeif stp $bridgeif ";
                and change it to
                $bridgecmd .= " addm $bridgeif ";
                save and reboot

                Ok. I will try your solution. It will be life sever if bridge come to life again.

                vi and command line is my preferred way ;-))

                TNX

                Sasa

                1 Reply Last reply Reply Quote 0
                • S
                  ssbaksa
                  last edited by

                  Can I modify interfaces.inc like this (from twitter) to get results?

                  $bridgecmd = "/sbin/ifconfig bridge{$x} ";
                  1627 1627 $lowestmtu = "1500";
                  1628 1628 $wirelessbridge = false;
                  1629 // iterate through and see if any of the involved interfaces are wireless
                  1629 $vlanbridge = false;
                  1630 // iterate through and see if any of the involved interfaces are wireless or VLANs
                  1630 1631 foreach ($bridgearray[$x] as $bridgeif) {
                  1631 1632 $friendlyifname = convert_real_interface_to_friendly_interface_name($bridgeif);
                  1632 1633 if(is_interface_wireless($friendlyifname))
                  1633 1634 $wirelessbridge = true;
                  1635 if(substr($bridgeif,0,4) == "vlan")
                  1636 $vlanbridge = true;
                  1634 1637 }
                  1638
                  1635 1639 foreach ($bridgearray[$x] as $bridgeif) {
                  1636 1640 // iterate through all the interfaces in this bridge
                  1637 1641 // append to the bridgecmd for this interface
                  1638 1642 // only use STP if no wireless interfaces are involved
                  1639 1643 if($wirelessbridge)
                  1644 $bridgecmd .= " addm $bridgeif ";
                  1645 elseif (substr($bridgeif,0,4) == "vlan")
                  1640 1646 $bridgecmd .= " addm $bridgeif ";
                  1641 1647 else
                  1642 1648 $bridgecmd .= " addm $bridgeif stp $bridgeif ";

                  1 Reply Last reply Reply Quote 0
                  • S
                    ssbaksa
                    last edited by

                    @Perry:

                    You can change the following.
                    @http://forum.pfsense.org/index.php/topic:

                    The quick hack:
                    /usr/local/www/interfaces_opt.php (you can open it and paste from Diagnostics -> Edit file)
                    find
                    $bridgecmd .= " addm $bridgeif stp $bridgeif ";
                    and change it to
                    $bridgecmd .= " addm $bridgeif ";
                    save and reboot

                    I have search inside this file but there is no line with bridgecmd or stp inside.

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by

                      That's in /etc/inc/interfaces.inc

                      It should be fine to use 1.2.3 in production, but given the switch of FreeBSD versions, there is more risk.

                      1 Reply Last reply Reply Quote 0
                      • S
                        ssbaksa
                        last edited by

                        @cmb:

                        That's in /etc/inc/interfaces.inc

                        It should be fine to use 1.2.3 in production, but given the switch of FreeBSD versions, there is more risk.

                        Yes, I can see that from code posted on Tweeter.
                        If I change that part of code manually would bi that to wise. I am not in position to reinstall pfS for next
                        few day's.

                        Sasa

                        1 Reply Last reply Reply Quote 0
                        • C
                          cmb
                          last edited by

                          You can change it manually, that will work fine. Or on 1.2.2 you can just take out stp in the bridgecmd.

                          1 Reply Last reply Reply Quote 0
                          • S
                            ssbaksa
                            last edited by

                            @cmb:

                            You can change it manually, that will work fine. Or on 1.2.2 you can just take out stp in the bridgecmd.

                            TNX! I will try that.

                            1 Reply Last reply Reply Quote 0
                            • S
                              ssbaksa
                              last edited by

                              Problem solved by applying patch from GIT. If someone need this patch to, I can send patched file by e-mail.
                              TNX to cmb and perry for help.

                              Sasa

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