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

    Limiter and IPv6

    Scheduled Pinned Locked Moved IPv6
    22 Posts 7 Posters 6.1k 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.
    • M
      maverick_slo
      last edited by

      Bump, same behaviour on 2.2

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

        I have tried it myself in 2.2 yet…

        Can you provide details to open a bug report?

        1 Reply Last reply Reply Quote 0
        • M
          maverick_slo
          last edited by

          well Ive just set limiter 10 Mbit DL and 10Mbit UL and on IPv4 it works on IPv6 it doesnt.
          Pages are loading or not, pings are timing out, unstable behavior…

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            Does this actually work for anyone? Sure like hell not here on 2.2.1 - despite the bug suggesting otherwise.

            1 Reply Last reply Reply Quote 0
            • M
              maverick_slo
              last edited by

              Nope, it does not work.

              1 Reply Last reply Reply Quote 0
              • D
                doktornotor Banned
                last edited by

                OK, thanks for confirmation. Going to nag on the bug.

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

                  Works for me on 2.2.1, what specifically are you trying that doesn't work?

                  1 Reply Last reply Reply Quote 0
                  • D
                    doktornotor Banned
                    last edited by

                    Well, what's described on the bug and here. Extremely simple - it totally kills IPv6 traffic. I have a simple 8 Mbps Down/ 2 Mbps Up limiters. Assigned to an alias of bandwidth limited hosts on LAN and as a floating rule on WAN. IPv6 sites like www.google.com are totally inaccessible from the aliased hosts once the limiter rules are enabled. The now disabled IPv6 rules - screenshots below - simply kill traffic. I can browse IPv6 site just fine as soon as I stop limiting TCP. If I apply the limiter to all protocols, I cannot even ping IPv6 from those limited hosts to hosts on Internet. The limiters work perfectly fine with IPv4. There is no difference between the rules except for IPv4 vs. IPv6.

                    Limiters:

                    LAN:

                    WAN/HEIPv6 tunnel (floating, direction In):

                    1 Reply Last reply Reply Quote 0
                    • M
                      maverick_slo
                      last edited by

                      Same goes for me…

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

                        Same here. I used a limiter to limit inbound ICMPv6 traffic. This resulted in echo replies not being send out altogether. The matter is rather strange and might be hard to debug as seems to work from one location and not from another. Like, the queue filling up and dropping any additional traffic from the source.

                        I just confirmed it with my tunnel broker, SixxSx. After switching on the limiter, packets are dropped. But, not right away but after some time.

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

                          Edit: scratch that, found a way to replicate.

                          1 Reply Last reply Reply Quote 0
                          • M
                            maverick_slo
                            last edited by

                            Hmmm ok I used 32 bit.
                            I just migrated to 64 bit yesterday, will try it out asap.

                            1 Reply Last reply Reply Quote 0
                            • M
                              maverick_slo
                              last edited by

                              Nope.
                              Tried with 64bit and same results… test-ipv6 didn`t finish, pages are super slow limiter set to 7/7 Mbit/s.

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

                                I am running 32bit as well on the system tested.

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

                                  @maverick_slo:

                                  Nope.
                                  Tried with 64bit and same results… test-ipv6 didn`t finish, pages are super slow limiter set to 7/7 Mbit/s.

                                  what type of v6 connectivity do you have?

                                  1 Reply Last reply Reply Quote 0
                                  • MikeV7896M
                                    MikeV7896
                                    last edited by

                                    Just wanted to note that I'm seeing the same issue with limiters and IPv6. Running 2.2.1-RELEASE (amd64). I have native IPv6 via DHCP-PD, requesting a /60 from my ISP.

                                    I created a second network… static IPv4 and Track Interface IPv6 (prefix 1). I created an out limiter of 5Mbit/sec and an in limiter of 1Mbit/sec. When I apply the limiters to the Allow rule on that second network interface, IPv6 no longer functions. A test page will load via IPv4, but all IPv6 tests will fail. When I remove the limiters, IPv6 works great. IPv4 works fine whether the limiter is in place or not.

                                    The S in IOT stands for Security

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

                                      I can replicate issues now, put the bug back to confirmed and to me. https://redmine.pfsense.org/issues/2526

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        doktornotor Banned
                                        last edited by

                                        Can people here retest this with latest 2.2.3 snapshots? Seems working for me.

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

                                          @doktornotor:

                                          Can people here retest this with latest 2.2.3 snapshots? Seems working for me.

                                          Ditto, seems fine for me as well, but more widespread testing would be appreciated.

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