Navigation

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

    Traffic Sharper with dhcp users and pppoe

    Traffic Shaping
    3
    4
    2254
    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.
    • K
      kill649 last edited by

      Hi, at first sorry for my english…

      I'm use pfsense at the first realease and it is a great soft. At this time i work of version 1.0.1 embedded and have 30 user's with dhcp and 8 with pppoe. Of course all wil switch to pppoe in the future.
      Bad the problem is that a have trouble with the sharper of the pppoe interface. It doesnt work. Ok the dhcp user are sharpet great bad only one user who use pppoe with emule or a mail program (smtp) kill the trafic for all.

      I found in the wizard of the traffic sharper this:

      The upload speed of your WAN link in Kbits/second. Note: PPPOE users should take into account PPPOE overhead and put a lower speed here.

      but I don't understand ...take into account PPPOE overhead.....maybe this is me problem :-) please help :->

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

        Subtract about 30k from both upload and download and that might take it into account.  I cannot remember from the top of my head what the overhead is but that sounds about right.

        1 Reply Last reply Reply Quote 0
        • K
          kill649 last edited by

          @sullrich:

          Subtract about 30k from both upload and download and that might take it into account.  I cannot remember from the top of my head what the overhead is but that sounds about right.

          OK a put in the traffic sharper 2048Kb for download on LAN and 140Kb for upload on WAN (standard wizard with p2p catch all). This is the half speed from me isp (for testing) .

          I set the maximum allowed bandwidth for the qP2PUp queue to 64Kb (for testing).

          The dhcp user are sharped for download and upload.
          The pppoe user have full upload and ignore the traffic shaping for uploading :-/ "and download (from time to time)".
          I have no idea what i'm doing bad.

          1 Reply Last reply Reply Quote 0
          • H
            hoba last edited by

            The trafficshaper only works on 2 interfaces currently out of the box, the pppoe users will have a new interface for each connection that is not shaped. At least download won't be shaped. Upload through WAN will be shaped and put in the default queue.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            Products

            • Platform Overview
            • TNSR
            • pfSense
            • Appliances

            Services

            • Training
            • Professional Services

            Support

            • Subscription Plans
            • Contact Support
            • Product Lifecycle
            • Documentation

            News

            • Media Coverage
            • Press
            • Events

            Resources

            • Blog
            • FAQ
            • Find a Partner
            • Resource Library
            • Security Information

            Company

            • About Us
            • Careers
            • Partners
            • Contact Us
            • Legal
            Our Mission

            We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

            Subscribe to our Newsletter

            Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

            © 2021 Rubicon Communications, LLC | Privacy Policy