Disable bridge module insert?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















I have Fedora 20 setup with default kernel configuration, where bridge feature is enabled as a module (CONFIG_BRIDGE=m), and the bridge module loads as the system starts. I don't understand who initiates it, since I have not found anything about bridge.ko in /etc/sysconfig/modules/*. However it ends up in the memory and every time I have to 'rmmod' it.



I would like to prohibit loading of the bridge.ko on the start up, yet I still want to manually load/unload bridge.ko whenever necessary.



I know it is possible to use the blacklist feature in /etc/modprobe.d/blacklist.conf, but can anybody point out who is loading bridge.ko in default setup of Fedora 20?










share|improve this question




























    1















    I have Fedora 20 setup with default kernel configuration, where bridge feature is enabled as a module (CONFIG_BRIDGE=m), and the bridge module loads as the system starts. I don't understand who initiates it, since I have not found anything about bridge.ko in /etc/sysconfig/modules/*. However it ends up in the memory and every time I have to 'rmmod' it.



    I would like to prohibit loading of the bridge.ko on the start up, yet I still want to manually load/unload bridge.ko whenever necessary.



    I know it is possible to use the blacklist feature in /etc/modprobe.d/blacklist.conf, but can anybody point out who is loading bridge.ko in default setup of Fedora 20?










    share|improve this question


























      1












      1








      1








      I have Fedora 20 setup with default kernel configuration, where bridge feature is enabled as a module (CONFIG_BRIDGE=m), and the bridge module loads as the system starts. I don't understand who initiates it, since I have not found anything about bridge.ko in /etc/sysconfig/modules/*. However it ends up in the memory and every time I have to 'rmmod' it.



      I would like to prohibit loading of the bridge.ko on the start up, yet I still want to manually load/unload bridge.ko whenever necessary.



      I know it is possible to use the blacklist feature in /etc/modprobe.d/blacklist.conf, but can anybody point out who is loading bridge.ko in default setup of Fedora 20?










      share|improve this question
















      I have Fedora 20 setup with default kernel configuration, where bridge feature is enabled as a module (CONFIG_BRIDGE=m), and the bridge module loads as the system starts. I don't understand who initiates it, since I have not found anything about bridge.ko in /etc/sysconfig/modules/*. However it ends up in the memory and every time I have to 'rmmod' it.



      I would like to prohibit loading of the bridge.ko on the start up, yet I still want to manually load/unload bridge.ko whenever necessary.



      I know it is possible to use the blacklist feature in /etc/modprobe.d/blacklist.conf, but can anybody point out who is loading bridge.ko in default setup of Fedora 20?







      fedora drivers kernel-modules






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 3 '14 at 5:26









      slm

      253k71535687




      253k71535687










      asked Oct 2 '14 at 1:52









      MarkMark

      5102624




      5102624




















          1 Answer
          1






          active

          oldest

          votes


















          0














          If you look at the output of lsmod it'll typically tell you which modules are loaded due to being a dependency of some other module. For example, in the case of bridge, it looks like stp & llc required it.



          $ lsmod | grep brid
          bridge 116006 1 ebtable_broute
          stp 12868 1 bridge
          llc 13941 2 stp,bridge


          NOTE: This is from my Fedora 20 system as well (laptop). You can use another tool, modinfo to find out information about the 2 modules:



          $ modinfo stp
          filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/802/stp.ko
          license: GPL
          depends: llc
          intree: Y
          vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
          signer: Fedora kernel signing key
          sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
          sig_hashalgo: sha256

          $ modinfo llc
          filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/llc/llc.ko
          description: LLC IEEE 802.2 core support
          author: Procom 1997, Jay Schullist 2001, Arnaldo C. Melo 2001-2003
          license: GPL
          depends:
          intree: Y
          vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
          signer: Fedora kernel signing key
          sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
          sig_hashalgo: sha256


          That didn't shed much more light on the situation, so let's see what Google has to say about "linux llc". Here's the project page and a synopsis of what this module is all about.



          excerpt - https://code.google.com/p/linux-llc/


          linux-llc is a collection of programs that form the base set of the
          Linux-LLC networking stack's userspace components for the Linux
          operating system.



          Logical Link Control (LLC) is a sublayer of the IEEE 802.2 LAN
          Protocol Suite. LLC is the top sub-layer in the data link layer and is
          the common access method to the different medium access technologies
          such as Tokenring, Ethernet and FDDI. LLC sockets provides a
          convenient and easy to use method for accessing LLC1 and LLC2
          functions from userspace.



          An LLC2 socket inherits all the functionality of an LLC1 socket. The
          LLC1 socket uses the LLC datalink connectionless mode (Unacknowledged
          data transfer) protocol. Verses an LLC2 socket uses the LLC datalink
          connection oriented mode plus datalink connectionless mode.




          So based on this information, I'd say this is a pretty core module, that you'll have a hard time removing and/or going without, especially if you're using any of the listed networking technologies.






          share|improve this answer






















            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f158759%2fdisable-bridge-module-insert%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            If you look at the output of lsmod it'll typically tell you which modules are loaded due to being a dependency of some other module. For example, in the case of bridge, it looks like stp & llc required it.



            $ lsmod | grep brid
            bridge 116006 1 ebtable_broute
            stp 12868 1 bridge
            llc 13941 2 stp,bridge


            NOTE: This is from my Fedora 20 system as well (laptop). You can use another tool, modinfo to find out information about the 2 modules:



            $ modinfo stp
            filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/802/stp.ko
            license: GPL
            depends: llc
            intree: Y
            vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
            signer: Fedora kernel signing key
            sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
            sig_hashalgo: sha256

            $ modinfo llc
            filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/llc/llc.ko
            description: LLC IEEE 802.2 core support
            author: Procom 1997, Jay Schullist 2001, Arnaldo C. Melo 2001-2003
            license: GPL
            depends:
            intree: Y
            vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
            signer: Fedora kernel signing key
            sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
            sig_hashalgo: sha256


            That didn't shed much more light on the situation, so let's see what Google has to say about "linux llc". Here's the project page and a synopsis of what this module is all about.



            excerpt - https://code.google.com/p/linux-llc/


            linux-llc is a collection of programs that form the base set of the
            Linux-LLC networking stack's userspace components for the Linux
            operating system.



            Logical Link Control (LLC) is a sublayer of the IEEE 802.2 LAN
            Protocol Suite. LLC is the top sub-layer in the data link layer and is
            the common access method to the different medium access technologies
            such as Tokenring, Ethernet and FDDI. LLC sockets provides a
            convenient and easy to use method for accessing LLC1 and LLC2
            functions from userspace.



            An LLC2 socket inherits all the functionality of an LLC1 socket. The
            LLC1 socket uses the LLC datalink connectionless mode (Unacknowledged
            data transfer) protocol. Verses an LLC2 socket uses the LLC datalink
            connection oriented mode plus datalink connectionless mode.




            So based on this information, I'd say this is a pretty core module, that you'll have a hard time removing and/or going without, especially if you're using any of the listed networking technologies.






            share|improve this answer



























              0














              If you look at the output of lsmod it'll typically tell you which modules are loaded due to being a dependency of some other module. For example, in the case of bridge, it looks like stp & llc required it.



              $ lsmod | grep brid
              bridge 116006 1 ebtable_broute
              stp 12868 1 bridge
              llc 13941 2 stp,bridge


              NOTE: This is from my Fedora 20 system as well (laptop). You can use another tool, modinfo to find out information about the 2 modules:



              $ modinfo stp
              filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/802/stp.ko
              license: GPL
              depends: llc
              intree: Y
              vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
              signer: Fedora kernel signing key
              sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
              sig_hashalgo: sha256

              $ modinfo llc
              filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/llc/llc.ko
              description: LLC IEEE 802.2 core support
              author: Procom 1997, Jay Schullist 2001, Arnaldo C. Melo 2001-2003
              license: GPL
              depends:
              intree: Y
              vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
              signer: Fedora kernel signing key
              sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
              sig_hashalgo: sha256


              That didn't shed much more light on the situation, so let's see what Google has to say about "linux llc". Here's the project page and a synopsis of what this module is all about.



              excerpt - https://code.google.com/p/linux-llc/


              linux-llc is a collection of programs that form the base set of the
              Linux-LLC networking stack's userspace components for the Linux
              operating system.



              Logical Link Control (LLC) is a sublayer of the IEEE 802.2 LAN
              Protocol Suite. LLC is the top sub-layer in the data link layer and is
              the common access method to the different medium access technologies
              such as Tokenring, Ethernet and FDDI. LLC sockets provides a
              convenient and easy to use method for accessing LLC1 and LLC2
              functions from userspace.



              An LLC2 socket inherits all the functionality of an LLC1 socket. The
              LLC1 socket uses the LLC datalink connectionless mode (Unacknowledged
              data transfer) protocol. Verses an LLC2 socket uses the LLC datalink
              connection oriented mode plus datalink connectionless mode.




              So based on this information, I'd say this is a pretty core module, that you'll have a hard time removing and/or going without, especially if you're using any of the listed networking technologies.






              share|improve this answer

























                0












                0








                0







                If you look at the output of lsmod it'll typically tell you which modules are loaded due to being a dependency of some other module. For example, in the case of bridge, it looks like stp & llc required it.



                $ lsmod | grep brid
                bridge 116006 1 ebtable_broute
                stp 12868 1 bridge
                llc 13941 2 stp,bridge


                NOTE: This is from my Fedora 20 system as well (laptop). You can use another tool, modinfo to find out information about the 2 modules:



                $ modinfo stp
                filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/802/stp.ko
                license: GPL
                depends: llc
                intree: Y
                vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
                signer: Fedora kernel signing key
                sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
                sig_hashalgo: sha256

                $ modinfo llc
                filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/llc/llc.ko
                description: LLC IEEE 802.2 core support
                author: Procom 1997, Jay Schullist 2001, Arnaldo C. Melo 2001-2003
                license: GPL
                depends:
                intree: Y
                vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
                signer: Fedora kernel signing key
                sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
                sig_hashalgo: sha256


                That didn't shed much more light on the situation, so let's see what Google has to say about "linux llc". Here's the project page and a synopsis of what this module is all about.



                excerpt - https://code.google.com/p/linux-llc/


                linux-llc is a collection of programs that form the base set of the
                Linux-LLC networking stack's userspace components for the Linux
                operating system.



                Logical Link Control (LLC) is a sublayer of the IEEE 802.2 LAN
                Protocol Suite. LLC is the top sub-layer in the data link layer and is
                the common access method to the different medium access technologies
                such as Tokenring, Ethernet and FDDI. LLC sockets provides a
                convenient and easy to use method for accessing LLC1 and LLC2
                functions from userspace.



                An LLC2 socket inherits all the functionality of an LLC1 socket. The
                LLC1 socket uses the LLC datalink connectionless mode (Unacknowledged
                data transfer) protocol. Verses an LLC2 socket uses the LLC datalink
                connection oriented mode plus datalink connectionless mode.




                So based on this information, I'd say this is a pretty core module, that you'll have a hard time removing and/or going without, especially if you're using any of the listed networking technologies.






                share|improve this answer













                If you look at the output of lsmod it'll typically tell you which modules are loaded due to being a dependency of some other module. For example, in the case of bridge, it looks like stp & llc required it.



                $ lsmod | grep brid
                bridge 116006 1 ebtable_broute
                stp 12868 1 bridge
                llc 13941 2 stp,bridge


                NOTE: This is from my Fedora 20 system as well (laptop). You can use another tool, modinfo to find out information about the 2 modules:



                $ modinfo stp
                filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/802/stp.ko
                license: GPL
                depends: llc
                intree: Y
                vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
                signer: Fedora kernel signing key
                sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
                sig_hashalgo: sha256

                $ modinfo llc
                filename: /lib/modules/3.16.3-200.fc20.x86_64/kernel/net/llc/llc.ko
                description: LLC IEEE 802.2 core support
                author: Procom 1997, Jay Schullist 2001, Arnaldo C. Melo 2001-2003
                license: GPL
                depends:
                intree: Y
                vermagic: 3.16.3-200.fc20.x86_64 SMP mod_unload
                signer: Fedora kernel signing key
                sig_key: 55:46:C1:1D:28:CF:EC:0B:46:B1:C1:F1:93:0D:6B:F3:EC:63:B0:67
                sig_hashalgo: sha256


                That didn't shed much more light on the situation, so let's see what Google has to say about "linux llc". Here's the project page and a synopsis of what this module is all about.



                excerpt - https://code.google.com/p/linux-llc/


                linux-llc is a collection of programs that form the base set of the
                Linux-LLC networking stack's userspace components for the Linux
                operating system.



                Logical Link Control (LLC) is a sublayer of the IEEE 802.2 LAN
                Protocol Suite. LLC is the top sub-layer in the data link layer and is
                the common access method to the different medium access technologies
                such as Tokenring, Ethernet and FDDI. LLC sockets provides a
                convenient and easy to use method for accessing LLC1 and LLC2
                functions from userspace.



                An LLC2 socket inherits all the functionality of an LLC1 socket. The
                LLC1 socket uses the LLC datalink connectionless mode (Unacknowledged
                data transfer) protocol. Verses an LLC2 socket uses the LLC datalink
                connection oriented mode plus datalink connectionless mode.




                So based on this information, I'd say this is a pretty core module, that you'll have a hard time removing and/or going without, especially if you're using any of the listed networking technologies.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Oct 3 '14 at 5:26









                slmslm

                253k71535687




                253k71535687



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f158759%2fdisable-bridge-module-insert%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown






                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?