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

    FYI: Error msg when applying ICMPv6 block rule with GUI

    Firewalling
    2
    5
    2.6k
    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.
    • S
      Snailer
      last edited by

      Because I dont use IPv6, I thought: Just block it. As I did this with ICMPv6 on my Wan-side, I got this error msg using only the GUI:

      There were error(s) loading the rules: /tmp/rules.debug:130: unknown protocol icmp6pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [130]:
      block in quick on $wan proto icmp6 from 84.28.56.65 to any label "USER_RULE: Block all ICMPv6"…

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

        What version?

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

          I am using the pfSense 1.0.1 RELEASE version. Is that what you want to know? :s

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

            Yeah.

            It's probably a bug, and probably still a bug in 1.2b1. We removed IPv6 from the kernel entirely, this definitely isn't going to work (no need to allow/block IPv6 traffic, pfsense is going to completely ignore it all).

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

              @cmb:

              It's probably a bug, and probably still a bug in 1.2b1. We removed IPv6 from the kernel entirely, this definitely isn't going to work (no need to allow/block IPv6 traffic, pfsense is going to completely ignore it all).

              Funny, my dutch linux/bsd magazine stated that their are real plans to push ipv6 into real action. :)
              I am aware that ipsense blocks by default -well done-, but it doesn't hurd to add a rule explicitly denying some traffic. (and by this trowing up a 2nd barrier ;D).

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