How do I whitelist some connections by ip from being dropped by connlimit?











up vote
3
down vote

favorite












I'm using these rules in /etc/ufw/before.rules



# Limit to 20 concurrent connections on port 80 per IP
-A ufw-before-input -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP
-A ufw-before-input -p tcp --syn --dport 443 -m connlimit --connlimit-above 20 -j DROP

# Limit to 20 connections on port 80 per 2 seconds per IP
-A ufw-before-input -p tcp --dport 80 -i eth0 -m state --state NEW -m recent --set
-A ufw-before-input -p tcp --dport 80 -i eth0 -m state --state NEW -m recent --update --seconds 2 --hitcount 20 -j DROP
-A ufw-before-input -p tcp --dport 443 -i eth0 -m state --state NEW -m recent --set
-A ufw-before-input -p tcp --dport 443 -i eth0 -m state --state NEW -m recent --update --seconds 2 --hitcount 20 -j DROP


I want to add a rule that will force the local system ips to not be connection or rate limited at all. For example, I have many cron jobs that connect to the server within the server. I need to prevent these from failing when too many are running at once.



UPDATE WITH SOLUTION: I think I just had to add more rules in before.rules instead of ufw command line to override the connection limit for specific ips. I can't answer my own question yet.



I just adds these rules above the connlimit rules:



-A ufw-before-input -p tcp --dport 80 -s 127.0.0.1 -j ACCEPT
-A ufw-before-input -p tcp --dport 443 -s 127.0.0.1 -j ACCEPT









share|improve this question




























    up vote
    3
    down vote

    favorite












    I'm using these rules in /etc/ufw/before.rules



    # Limit to 20 concurrent connections on port 80 per IP
    -A ufw-before-input -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP
    -A ufw-before-input -p tcp --syn --dport 443 -m connlimit --connlimit-above 20 -j DROP

    # Limit to 20 connections on port 80 per 2 seconds per IP
    -A ufw-before-input -p tcp --dport 80 -i eth0 -m state --state NEW -m recent --set
    -A ufw-before-input -p tcp --dport 80 -i eth0 -m state --state NEW -m recent --update --seconds 2 --hitcount 20 -j DROP
    -A ufw-before-input -p tcp --dport 443 -i eth0 -m state --state NEW -m recent --set
    -A ufw-before-input -p tcp --dport 443 -i eth0 -m state --state NEW -m recent --update --seconds 2 --hitcount 20 -j DROP


    I want to add a rule that will force the local system ips to not be connection or rate limited at all. For example, I have many cron jobs that connect to the server within the server. I need to prevent these from failing when too many are running at once.



    UPDATE WITH SOLUTION: I think I just had to add more rules in before.rules instead of ufw command line to override the connection limit for specific ips. I can't answer my own question yet.



    I just adds these rules above the connlimit rules:



    -A ufw-before-input -p tcp --dport 80 -s 127.0.0.1 -j ACCEPT
    -A ufw-before-input -p tcp --dport 443 -s 127.0.0.1 -j ACCEPT









    share|improve this question


























      up vote
      3
      down vote

      favorite









      up vote
      3
      down vote

      favorite











      I'm using these rules in /etc/ufw/before.rules



      # Limit to 20 concurrent connections on port 80 per IP
      -A ufw-before-input -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP
      -A ufw-before-input -p tcp --syn --dport 443 -m connlimit --connlimit-above 20 -j DROP

      # Limit to 20 connections on port 80 per 2 seconds per IP
      -A ufw-before-input -p tcp --dport 80 -i eth0 -m state --state NEW -m recent --set
      -A ufw-before-input -p tcp --dport 80 -i eth0 -m state --state NEW -m recent --update --seconds 2 --hitcount 20 -j DROP
      -A ufw-before-input -p tcp --dport 443 -i eth0 -m state --state NEW -m recent --set
      -A ufw-before-input -p tcp --dport 443 -i eth0 -m state --state NEW -m recent --update --seconds 2 --hitcount 20 -j DROP


      I want to add a rule that will force the local system ips to not be connection or rate limited at all. For example, I have many cron jobs that connect to the server within the server. I need to prevent these from failing when too many are running at once.



      UPDATE WITH SOLUTION: I think I just had to add more rules in before.rules instead of ufw command line to override the connection limit for specific ips. I can't answer my own question yet.



      I just adds these rules above the connlimit rules:



      -A ufw-before-input -p tcp --dport 80 -s 127.0.0.1 -j ACCEPT
      -A ufw-before-input -p tcp --dport 443 -s 127.0.0.1 -j ACCEPT









      share|improve this question















      I'm using these rules in /etc/ufw/before.rules



      # Limit to 20 concurrent connections on port 80 per IP
      -A ufw-before-input -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP
      -A ufw-before-input -p tcp --syn --dport 443 -m connlimit --connlimit-above 20 -j DROP

      # Limit to 20 connections on port 80 per 2 seconds per IP
      -A ufw-before-input -p tcp --dport 80 -i eth0 -m state --state NEW -m recent --set
      -A ufw-before-input -p tcp --dport 80 -i eth0 -m state --state NEW -m recent --update --seconds 2 --hitcount 20 -j DROP
      -A ufw-before-input -p tcp --dport 443 -i eth0 -m state --state NEW -m recent --set
      -A ufw-before-input -p tcp --dport 443 -i eth0 -m state --state NEW -m recent --update --seconds 2 --hitcount 20 -j DROP


      I want to add a rule that will force the local system ips to not be connection or rate limited at all. For example, I have many cron jobs that connect to the server within the server. I need to prevent these from failing when too many are running at once.



      UPDATE WITH SOLUTION: I think I just had to add more rules in before.rules instead of ufw command line to override the connection limit for specific ips. I can't answer my own question yet.



      I just adds these rules above the connlimit rules:



      -A ufw-before-input -p tcp --dport 80 -s 127.0.0.1 -j ACCEPT
      -A ufw-before-input -p tcp --dport 443 -s 127.0.0.1 -j ACCEPT






      iptables ufw






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 16 '14 at 19:19

























      asked Jan 16 '14 at 15:48









      Bruce Kirkpatrick

      1615




      1615






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          I found another solution using iptables.



          iptables command to limit connections:



          iptables -A INPUT -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP


          you can exclude one ip:



          iptables -A INPUT -p tcp --syn --dport 80 -d ! 127.0.0.1 -m connlimit --connlimit-above 20 -j DROP


          I hope this is helpful for you.






          share|improve this answer




























            up vote
            0
            down vote













            First , you have not provided sufficeint information for us to give you a specific answer.



            Second, those are ufw rules. ufw is a front end for iptables and you can manage the rules from the command line, ufw or a graphical interface, gufw.



            Using iptables directly will conflict with your ufw rules, so use one tool or another.



            You need to post your ufw rules. In general you are going to allow your local network prior to the rules you posted. How are you managing your ufw rules? command line? gufw?



            for ufw, something like this



            sudo ufw allow from 192.168.0.0/24


            See also:



            http://blog.bodhizazen.com/linux/firewall-ubuntu-servers/



            https://help.ubuntu.com/community/UFW



            and for iptables http://bodhizazen.com/Tutorials/iptables






            share|improve this answer























            • ufw already has port 80 & 443 open to all ips with ufw allow 80/tcp and ufw allow 443/tcp. If I add a rule in ufw, I don't think it will work. To do connection limiting, I had to use /etc/ufw/before.rules according to other resources. If you know a better way to do that limiting with ufw, that might help. I don't see that "ufw limit" is documented in a way that explains how to do specify how many connections at once, and over time.
              – Bruce Kirkpatrick
              Jan 16 '14 at 16:18










            • Hard to venture a guess without knowing your rules. Order of rules is critical. I do not know how a port can be allowed and limited at the same time. Also, as you can see, your connection limits on ports 80 and 443 are way too conservative, web servers can handle thousands of hits. I use sudo iptables -A INPUT -p tcp --dport 80 -m state --state NEW -m limit --limit 50/minute --limit-burst 200 -j ACCEPT . Also REJECT is better then DROP. See unix.stackexchange.com/questions/109459/…
              – Panther
              Jan 16 '14 at 18:30










            • the limit is per ip and 20 is plenty since real users only do 2 to 6 connections per host name. I can make it a little more if have trouble with that. I'll try REJECT as you say, but i think that only helps a user avoid waiting forever for a client timeout.
              – Bruce Kirkpatrick
              Jan 16 '14 at 19:17










            • I think I just had to add more rules above those rules for the ips I want to accept. thanks.
              – Bruce Kirkpatrick
              Jan 16 '14 at 19:20











            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2faskubuntu.com%2fquestions%2f406444%2fhow-do-i-whitelist-some-connections-by-ip-from-being-dropped-by-connlimit%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            I found another solution using iptables.



            iptables command to limit connections:



            iptables -A INPUT -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP


            you can exclude one ip:



            iptables -A INPUT -p tcp --syn --dport 80 -d ! 127.0.0.1 -m connlimit --connlimit-above 20 -j DROP


            I hope this is helpful for you.






            share|improve this answer

























              up vote
              0
              down vote













              I found another solution using iptables.



              iptables command to limit connections:



              iptables -A INPUT -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP


              you can exclude one ip:



              iptables -A INPUT -p tcp --syn --dport 80 -d ! 127.0.0.1 -m connlimit --connlimit-above 20 -j DROP


              I hope this is helpful for you.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                I found another solution using iptables.



                iptables command to limit connections:



                iptables -A INPUT -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP


                you can exclude one ip:



                iptables -A INPUT -p tcp --syn --dport 80 -d ! 127.0.0.1 -m connlimit --connlimit-above 20 -j DROP


                I hope this is helpful for you.






                share|improve this answer












                I found another solution using iptables.



                iptables command to limit connections:



                iptables -A INPUT -p tcp --syn --dport 80 -m connlimit --connlimit-above 20 -j DROP


                you can exclude one ip:



                iptables -A INPUT -p tcp --syn --dport 80 -d ! 127.0.0.1 -m connlimit --connlimit-above 20 -j DROP


                I hope this is helpful for you.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Sep 5 '14 at 2:17









                Gino

                21615




                21615
























                    up vote
                    0
                    down vote













                    First , you have not provided sufficeint information for us to give you a specific answer.



                    Second, those are ufw rules. ufw is a front end for iptables and you can manage the rules from the command line, ufw or a graphical interface, gufw.



                    Using iptables directly will conflict with your ufw rules, so use one tool or another.



                    You need to post your ufw rules. In general you are going to allow your local network prior to the rules you posted. How are you managing your ufw rules? command line? gufw?



                    for ufw, something like this



                    sudo ufw allow from 192.168.0.0/24


                    See also:



                    http://blog.bodhizazen.com/linux/firewall-ubuntu-servers/



                    https://help.ubuntu.com/community/UFW



                    and for iptables http://bodhizazen.com/Tutorials/iptables






                    share|improve this answer























                    • ufw already has port 80 & 443 open to all ips with ufw allow 80/tcp and ufw allow 443/tcp. If I add a rule in ufw, I don't think it will work. To do connection limiting, I had to use /etc/ufw/before.rules according to other resources. If you know a better way to do that limiting with ufw, that might help. I don't see that "ufw limit" is documented in a way that explains how to do specify how many connections at once, and over time.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 16:18










                    • Hard to venture a guess without knowing your rules. Order of rules is critical. I do not know how a port can be allowed and limited at the same time. Also, as you can see, your connection limits on ports 80 and 443 are way too conservative, web servers can handle thousands of hits. I use sudo iptables -A INPUT -p tcp --dport 80 -m state --state NEW -m limit --limit 50/minute --limit-burst 200 -j ACCEPT . Also REJECT is better then DROP. See unix.stackexchange.com/questions/109459/…
                      – Panther
                      Jan 16 '14 at 18:30










                    • the limit is per ip and 20 is plenty since real users only do 2 to 6 connections per host name. I can make it a little more if have trouble with that. I'll try REJECT as you say, but i think that only helps a user avoid waiting forever for a client timeout.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 19:17










                    • I think I just had to add more rules above those rules for the ips I want to accept. thanks.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 19:20















                    up vote
                    0
                    down vote













                    First , you have not provided sufficeint information for us to give you a specific answer.



                    Second, those are ufw rules. ufw is a front end for iptables and you can manage the rules from the command line, ufw or a graphical interface, gufw.



                    Using iptables directly will conflict with your ufw rules, so use one tool or another.



                    You need to post your ufw rules. In general you are going to allow your local network prior to the rules you posted. How are you managing your ufw rules? command line? gufw?



                    for ufw, something like this



                    sudo ufw allow from 192.168.0.0/24


                    See also:



                    http://blog.bodhizazen.com/linux/firewall-ubuntu-servers/



                    https://help.ubuntu.com/community/UFW



                    and for iptables http://bodhizazen.com/Tutorials/iptables






                    share|improve this answer























                    • ufw already has port 80 & 443 open to all ips with ufw allow 80/tcp and ufw allow 443/tcp. If I add a rule in ufw, I don't think it will work. To do connection limiting, I had to use /etc/ufw/before.rules according to other resources. If you know a better way to do that limiting with ufw, that might help. I don't see that "ufw limit" is documented in a way that explains how to do specify how many connections at once, and over time.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 16:18










                    • Hard to venture a guess without knowing your rules. Order of rules is critical. I do not know how a port can be allowed and limited at the same time. Also, as you can see, your connection limits on ports 80 and 443 are way too conservative, web servers can handle thousands of hits. I use sudo iptables -A INPUT -p tcp --dport 80 -m state --state NEW -m limit --limit 50/minute --limit-burst 200 -j ACCEPT . Also REJECT is better then DROP. See unix.stackexchange.com/questions/109459/…
                      – Panther
                      Jan 16 '14 at 18:30










                    • the limit is per ip and 20 is plenty since real users only do 2 to 6 connections per host name. I can make it a little more if have trouble with that. I'll try REJECT as you say, but i think that only helps a user avoid waiting forever for a client timeout.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 19:17










                    • I think I just had to add more rules above those rules for the ips I want to accept. thanks.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 19:20













                    up vote
                    0
                    down vote










                    up vote
                    0
                    down vote









                    First , you have not provided sufficeint information for us to give you a specific answer.



                    Second, those are ufw rules. ufw is a front end for iptables and you can manage the rules from the command line, ufw or a graphical interface, gufw.



                    Using iptables directly will conflict with your ufw rules, so use one tool or another.



                    You need to post your ufw rules. In general you are going to allow your local network prior to the rules you posted. How are you managing your ufw rules? command line? gufw?



                    for ufw, something like this



                    sudo ufw allow from 192.168.0.0/24


                    See also:



                    http://blog.bodhizazen.com/linux/firewall-ubuntu-servers/



                    https://help.ubuntu.com/community/UFW



                    and for iptables http://bodhizazen.com/Tutorials/iptables






                    share|improve this answer














                    First , you have not provided sufficeint information for us to give you a specific answer.



                    Second, those are ufw rules. ufw is a front end for iptables and you can manage the rules from the command line, ufw or a graphical interface, gufw.



                    Using iptables directly will conflict with your ufw rules, so use one tool or another.



                    You need to post your ufw rules. In general you are going to allow your local network prior to the rules you posted. How are you managing your ufw rules? command line? gufw?



                    for ufw, something like this



                    sudo ufw allow from 192.168.0.0/24


                    See also:



                    http://blog.bodhizazen.com/linux/firewall-ubuntu-servers/



                    https://help.ubuntu.com/community/UFW



                    and for iptables http://bodhizazen.com/Tutorials/iptables







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Aug 22 '17 at 19:04

























                    answered Jan 16 '14 at 16:03









                    Panther

                    77.5k12156258




                    77.5k12156258












                    • ufw already has port 80 & 443 open to all ips with ufw allow 80/tcp and ufw allow 443/tcp. If I add a rule in ufw, I don't think it will work. To do connection limiting, I had to use /etc/ufw/before.rules according to other resources. If you know a better way to do that limiting with ufw, that might help. I don't see that "ufw limit" is documented in a way that explains how to do specify how many connections at once, and over time.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 16:18










                    • Hard to venture a guess without knowing your rules. Order of rules is critical. I do not know how a port can be allowed and limited at the same time. Also, as you can see, your connection limits on ports 80 and 443 are way too conservative, web servers can handle thousands of hits. I use sudo iptables -A INPUT -p tcp --dport 80 -m state --state NEW -m limit --limit 50/minute --limit-burst 200 -j ACCEPT . Also REJECT is better then DROP. See unix.stackexchange.com/questions/109459/…
                      – Panther
                      Jan 16 '14 at 18:30










                    • the limit is per ip and 20 is plenty since real users only do 2 to 6 connections per host name. I can make it a little more if have trouble with that. I'll try REJECT as you say, but i think that only helps a user avoid waiting forever for a client timeout.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 19:17










                    • I think I just had to add more rules above those rules for the ips I want to accept. thanks.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 19:20


















                    • ufw already has port 80 & 443 open to all ips with ufw allow 80/tcp and ufw allow 443/tcp. If I add a rule in ufw, I don't think it will work. To do connection limiting, I had to use /etc/ufw/before.rules according to other resources. If you know a better way to do that limiting with ufw, that might help. I don't see that "ufw limit" is documented in a way that explains how to do specify how many connections at once, and over time.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 16:18










                    • Hard to venture a guess without knowing your rules. Order of rules is critical. I do not know how a port can be allowed and limited at the same time. Also, as you can see, your connection limits on ports 80 and 443 are way too conservative, web servers can handle thousands of hits. I use sudo iptables -A INPUT -p tcp --dport 80 -m state --state NEW -m limit --limit 50/minute --limit-burst 200 -j ACCEPT . Also REJECT is better then DROP. See unix.stackexchange.com/questions/109459/…
                      – Panther
                      Jan 16 '14 at 18:30










                    • the limit is per ip and 20 is plenty since real users only do 2 to 6 connections per host name. I can make it a little more if have trouble with that. I'll try REJECT as you say, but i think that only helps a user avoid waiting forever for a client timeout.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 19:17










                    • I think I just had to add more rules above those rules for the ips I want to accept. thanks.
                      – Bruce Kirkpatrick
                      Jan 16 '14 at 19:20
















                    ufw already has port 80 & 443 open to all ips with ufw allow 80/tcp and ufw allow 443/tcp. If I add a rule in ufw, I don't think it will work. To do connection limiting, I had to use /etc/ufw/before.rules according to other resources. If you know a better way to do that limiting with ufw, that might help. I don't see that "ufw limit" is documented in a way that explains how to do specify how many connections at once, and over time.
                    – Bruce Kirkpatrick
                    Jan 16 '14 at 16:18




                    ufw already has port 80 & 443 open to all ips with ufw allow 80/tcp and ufw allow 443/tcp. If I add a rule in ufw, I don't think it will work. To do connection limiting, I had to use /etc/ufw/before.rules according to other resources. If you know a better way to do that limiting with ufw, that might help. I don't see that "ufw limit" is documented in a way that explains how to do specify how many connections at once, and over time.
                    – Bruce Kirkpatrick
                    Jan 16 '14 at 16:18












                    Hard to venture a guess without knowing your rules. Order of rules is critical. I do not know how a port can be allowed and limited at the same time. Also, as you can see, your connection limits on ports 80 and 443 are way too conservative, web servers can handle thousands of hits. I use sudo iptables -A INPUT -p tcp --dport 80 -m state --state NEW -m limit --limit 50/minute --limit-burst 200 -j ACCEPT . Also REJECT is better then DROP. See unix.stackexchange.com/questions/109459/…
                    – Panther
                    Jan 16 '14 at 18:30




                    Hard to venture a guess without knowing your rules. Order of rules is critical. I do not know how a port can be allowed and limited at the same time. Also, as you can see, your connection limits on ports 80 and 443 are way too conservative, web servers can handle thousands of hits. I use sudo iptables -A INPUT -p tcp --dport 80 -m state --state NEW -m limit --limit 50/minute --limit-burst 200 -j ACCEPT . Also REJECT is better then DROP. See unix.stackexchange.com/questions/109459/…
                    – Panther
                    Jan 16 '14 at 18:30












                    the limit is per ip and 20 is plenty since real users only do 2 to 6 connections per host name. I can make it a little more if have trouble with that. I'll try REJECT as you say, but i think that only helps a user avoid waiting forever for a client timeout.
                    – Bruce Kirkpatrick
                    Jan 16 '14 at 19:17




                    the limit is per ip and 20 is plenty since real users only do 2 to 6 connections per host name. I can make it a little more if have trouble with that. I'll try REJECT as you say, but i think that only helps a user avoid waiting forever for a client timeout.
                    – Bruce Kirkpatrick
                    Jan 16 '14 at 19:17












                    I think I just had to add more rules above those rules for the ips I want to accept. thanks.
                    – Bruce Kirkpatrick
                    Jan 16 '14 at 19:20




                    I think I just had to add more rules above those rules for the ips I want to accept. thanks.
                    – Bruce Kirkpatrick
                    Jan 16 '14 at 19:20


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2faskubuntu.com%2fquestions%2f406444%2fhow-do-i-whitelist-some-connections-by-ip-from-being-dropped-by-connlimit%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

                    數位音樂下載

                    When can things happen in Etherscan, such as the picture below?

                    格利澤436b