Chris Buechler wrote:
On Sun, Feb 21, 2010 at 11:14 PM, Jim Spaloss <[email protected]> wrote:
Hello,
I'm not sure if this is the proper place to post a bug, but I couldn't find
the proper place. I'm a long time lurker on the M0n0wall list, but have
begun to use PFSense for some of my more complicated installs. I'm currently
working on setting up a shop for myself.
The Tech Bench has 20 ports, each on it's own VLAN and pfSense interface. I
am using a whitelist approach to the rules for the Tech Bench interfaces and
when I add a rule to allow DNS traffic to the pfSense interface address it
works fine on interfaces opt1-opt9. However, when I hit opt10, the rule
stops working and the the text "Interface IP address" in the Destination
field of the rule screen is blank. I tried editing the rule and re-saving it
multiple times, but the result is the same. Changing the destination from
the interface address to the subnet instead is a work-around that I am
currently using.
Please send me a full backup of your config off list.
I've noticed the same some time ago but never got time to troubleshoot
it. First of all OPT10and+ do not appear properly in web gui - instead
of "Interface IP address" you get empty space.
The only incorrect thing I found is in guiconfig.inc function
print_address($adr):
if (preg_match("/opt[0-999]ip/", $adr['network'])) {
does not work as "opt0 through opt999". I think it should be replaced with
if (preg_match("/opt[0-9]{1,3}ip/", $adr['network'])) {
Evgeny.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Commercial support available - https://portal.pfsense.org
