Bce0 error on update?

[bubble1975]

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!!

[doktornotor]

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

[phil.davis]

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.

[jimp]

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.