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

Adding limiters to IPv6 firewall rules breaks IPv6

Scheduled Pinned Locked Moved Traffic Shaping
7 Posts 2 Posters 1.2k 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.
  • C
    CiscoKid85
    last edited by Feb 21, 2015, 12:18 AM

    Adding a simple UP/Down limit to an IPv6 * -> Any firewall rule will break IPv6.

    Is this a known issue? Or a bug?

    1 Reply Last reply Reply Quote 0
    • D
      Derelict LAYER 8 Netgate
      last edited by Feb 21, 2015, 12:49 AM

      That does appear to cause some problems.  I'm on an HE.Net GIF tunnel though…

      Set 1Mbit up and 2Mbit down limiters on my IPv6 any any rule.  Can still ping out.  DNS appears to work, but anything TCP is worthless.  Can't browse.  I can telnet IPv6 to smtp.gmail.com.  I get a banner, but I get nothing back from an EHLO.

      Weird.

      Chattanooga, Tennessee, USA
      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
      Do Not Chat For Help! NO_WAN_EGRESS(TM)

      1 Reply Last reply Reply Quote 0
      • C
        CiscoKid85
        last edited by Feb 21, 2015, 12:51 AM

        What's the process for submitting this as a bug?

        1 Reply Last reply Reply Quote 0
        • D
          Derelict LAYER 8 Netgate
          last edited by Feb 21, 2015, 1:37 AM

          Is your IPv6 native or on a tunnel?

          With all the IPv6 stuff in the limiters, I'm not convinced it's a bug yet.  Things usually aren't.

          redmine.pfsense.org.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • C
            CiscoKid85
            last edited by Feb 21, 2015, 1:39 AM

            IPv6 is implemented natively. It was implemented by tracking the IPv6 interface.

            1 Reply Last reply Reply Quote 0
            • D
              Derelict LAYER 8 Netgate
              last edited by Feb 21, 2015, 1:41 AM

              https://redmine.pfsense.org/issues/2526

              Feedback and will be fixed in 2.2.1

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              1 Reply Last reply Reply Quote 0
              • C
                CiscoKid85
                last edited by Feb 21, 2015, 1:53 AM

                Many thanks!

                1 Reply Last reply Reply Quote 0
                2 out of 7
                • First post
                  2/7
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                  This community forum collects and processes your personal information.
                  consent.not_received