Navigation

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

    Bce0 error on update?

    Installation and Upgrades
    4
    4
    452
    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
      bubble1975 last edited by

      Hey Y'all,

      I've been updating all our pfSense 2.1 boxes to 2.2, and these last couple I updated worked OK but had alerts when I logged into the web interface after the update.  See attached pic of the alerts.  But basically a bunch of these came up:

      [ There were error(s) loading the rules: /tmp/rules.debug:11: syntax error - The line in question reads [11]: 103 = { bce0 }]

      I looked at the /tmp/rules.debug file and saw line 11:

      #System aliases

      loopback = "{ lo0 }"
      WAN = "{ mxge0 }"
      LAN = "{ mxge1 }"
      103 = "{ bce0 }"  <–-  Line 11
      OpenVPN = "{ openvpn }"

      Network 103 seems OK...  What does the error mean?

      Many thanks!!


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

        Stop calling your network iface 103 (and avoid any number-only stuff).

        1 Reply Last reply Reply Quote 0
        • P
          phil.davis last edited by

          There have been a couple of posts about this sort of thing - Alias names, Interface names… that are just numbers are not allowed.
          The webGUI will give an error now if you try to save something like that. But I guess there are old configs that could have that and give problems after upgrade.

          1 Reply Last reply Reply Quote 0
          • jimp
            jimp Rebel Alliance Developer Netgate last edited by

            Apparently the yacc parsing got more strict in pf. It used to accept those  (but we denied them). It was also the source of problem with some of the traffic shaping problems with DSCP and tag matching/setting. The latter of which have been fixed for 2.2.1.

            Numeric aliases and interface names are definitely not allowed though, it's lucky they ever worked.

            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