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

    Per user shaping does not work on 2.0.1

    Traffic Shaping
    2
    3
    1.7k
    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.
    • B
      benny_melb
      last edited by

      Got a bit of problem on the per-user shaping. I have about 5 machine running 1.2.3, i have the captive portal enabled and auth against a external radius server (freeradius + mysql), the per-user shaping works beautifully on those box and its running for more then a year without a single issue.

      I recently have a testing machine running 2.0.1 (2.0.1-RELEASE (i386) built on Mon Dec 12 17:53:52 EST 2011), have the CP turn on and pointing to the same radius but the per-user shaping does not work. In fact, as soon as i have the per-user shaping enabled, the end user will have no internet access although the authentication on radius server shows "Login OK"

      I've tested the same user account on the 1.2.3 machine and its working ok. Just doesn't work on the 2.0.1. I've tried the latest snapshot and it doesn't work as well. Perhaps someone will be able to help?

      The radius attribute i am using is  WISPr-Bandwidth-Max-Up = 1000 and WISPr-Bandwidth-Max-Down = 4000. radtest on radius server output the following

      radius:~# radtest username password 127.0.0.1:1812 0 secret
      Sending Access-Request of id 250 to 127.0.0.1 port 1812
             User-Name = "username"
             User-Password = "password"
             NAS-IP-Address = 255.255.255.255
             NAS-Port = 0
      rad_recv: Access-Accept packet from host 127.0.0.1:1812, id=250, length=44
             WISPr-Bandwidth-Max-Up = 1000
             WISPr-Bandwidth-Max-Down = 4000

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

        Earlier versions used those attributes wrongly. They're supposed to be in bps not Kbps. So you're limiting people to too slow a speed for a usable connection. Multiply those times 1024 and you'll have the same behavior as previously.

        1 Reply Last reply Reply Quote 0
        • B
          benny_melb
          last edited by

          Million Thanks cmb, you're life saver :) been working on this issue for a week and cant find any info on internet about this.

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