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

    Connection speed %50 of normal

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    9 Posts 6 Posters 2.9k Views
    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.
    • MellowlynxM
      Mellowlynx
      last edited by

      I'm running pfSense for some time now and never have big issues anymore.

      Today I noticed that the speedtest.net results are %50 of what it should be.
      I did a test by connection my mac directly to the modem and than it's normal.
      After that I did test it again after disabling "Transparent HTTP proxy" and than is it normal to.
      When I enable "Transparent HTTP proxy" again it's at %50.

      I already edited "/boot/loader.conf" and looks like this.

      
      autoboot_delay="1"
      vm.kmem_size="435544320"
      vm.kmem_size_max="535544320"
      #kern.ipc.nmbclusters="0"
      kern.hz=100
      #for squid
      kern.ipc.nmbclusters="32768"
      kern.maxfiles="65536"
      kern.maxfilesperproc="32768"
      net.inet.ip.portrange.last="65535"
      hw.usb.no_pf="1"
      
      

      Anyone have a idea what the problem can be?

      I'm running
      2.1-BETA1 (i386) - built on Thu Mar 14 23:00:40 EDT 2013
      with squid3 - 3.1.20 pkg 2.0.6

      1 Reply Last reply Reply Quote 0
      • T
        trunglam
        last edited by

        let check proxy config

        1 Reply Last reply Reply Quote 0
        • T
          Tikimotel
          last edited by

          Builds get compiled every day, this post was from march 15th.
          I suggest installing/updating to a more current build first.

          1 Reply Last reply Reply Quote 0
          • MellowlynxM
            Mellowlynx
            last edited by

            Config should be good, never had problems and blocked domains are indeed blocked.
            Only the speed is different.

            I'm updated to the newest version and it's still the same.

            Any tips are still welcome!

            1 Reply Last reply Reply Quote 0
            • chpalmerC
              chpalmer
              last edited by

              Would be nice to know a bit more about your setup.

              Triggering snowflakes one by one..
              Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

              1 Reply Last reply Reply Quote 0
              • MellowlynxM
                Mellowlynx
                last edited by

                The systeem is running on a P4 1.7GHz

                With Wan, Lan and OPT1 with captive portal.
                And a transparent proxy to block a view domains.

                Everything is running fine and fast, except the internet speed…

                Do you need to know more?

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

                  sounds like you need
                  http://doc.pfsense.org/index.php/Squid_Package_Tuning

                  1 Reply Last reply Reply Quote 0
                  • MellowlynxM
                    Mellowlynx
                    last edited by

                    I already have some that trips running.
                    Worked fine before.

                    I'm now considering removing the proxy, I only use it to block two domains.
                    Does anyone have tips on how to easily block domains without a proxy on both LAN and OPT1?

                    Regards, R

                    1 Reply Last reply Reply Quote 0
                    • D
                      dhatz
                      last edited by

                      @rcktboy:

                      Does anyone have tips on how to easily block domains without a proxy on both LAN and OPT1?

                      Well, the two easiest ways that come to mind would be to

                      1. use the DNS forwarder to point those two domains to 127.0.0.1 or
                      2. block their IP ranges (using aliases makes it easier)

                      If you want to be thorough, you can use both ways.

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