Status: System logs: Firewall Easy Rules gives error

[cjbujold]

Love PFSense 2.0 , Reviewing my Firewall Logs and tried to create a new rule to block(hide) an entry in the firewall log and when I click on the "Easy Rule , Add to Block List " button I get the following error.  Can somebody help me resolve this issue.

Fatal error: Cannot use string offset as an array in /etc/inc/easyrule.inc on line 83

Thanks

I am using

2.0-BETA4  (i386)
built on Tue Sep 28 11:29:07 EDT 2010

[jimp]

I'll need to see exactly what the rule looked like that you clicked (screenshot if possible) and the easyrule URL that it used when you got that error (right click the link and copy/paste)

[cjbujold]

Here is a screen shot of the error screens.  The first shows the item I select which is the X+ button and the second is the error that is shown.

Thanks

[jimp]

A couple things:

1. I don't see how in the code with a valid config you could have received that error.

2. In your firewall log output, one line has the physical interface name (em2) - Had you just recently renamed or reassigned an interface?  I haven't seen that happen before.

I'm going to check in a small fix that might help, but I'm inclined to think there may be something else wrong on your system that led to that error, unless someone else can reproduce it as well.

[cjbujold]

I have 4 NIC's in the system but only use 3. (1 LAN 2 WANS).  Can I manually edit some config  file ( If you could provide instructions it would be appreciated) so that it does not see the fourth NIC, since this seems to be the issue you identified.  I cannot remove the 4th NIC since it is on the Motherboard.  I will also try your fix to see if it resolves the issue.

If my config is incorrect how can I fix it?

Thanks

[jimp]

Hard to say how it might not be correct without seeing the entire config.

If you do not have that fourth network card assigned under Interfaces > (assign), it's essentially disabled. If it's on the motherboard you might be able to disable it in the BIOS, but if it was unplugged and unassigned, it doesn't make sense that you'd see a log entry from it.

[cjbujold]

It is unplugged and unassigned and it does not show up in the interface as available.  But it is the only explanation I have that you would see an EM2 in the log.  Is there a way to remove that incorrect entry in a config file?

Thanks

[jimp]

Are all of your network cards the same?  If so, em2 would be the third network card in the list, since the numbering starts at 0.

It might help to see a screenshot of Interfaces > (assign), and Status > Interfaces, or perhaps even the output from Diagnostics > Command, type in "ifconfig -a"

[cjbujold]

Three of the cards are identical ,(Intel) and the motherboard NIC is a Broadcom (this is the disabled one).  My three cards are EM0 - LAN , EM1 - WAN2(opt) and EM2-WAN  the Bfe0 is not used.

Here are the images you requested.

Thank you for the help it is much appreciated.

[jimp]

OK, so the traffic from em2 is really your WAN plugged into your DSL modem. That's fine then.

If you want, you could assign em2 to a new interface and use that to manage your modem.
http://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall#Configure_a_new_Interface

[cjbujold]

Tired the update and it fixed my problem

Thanks