After installing 2.2.00 patch the R3000 doesn''t filter anymore

This article applies to:

• R3000 v 2.2.00

Symptoms:

• After installing 2.2.00 patch the R3000 doesn't filter anymore, it doesn't ping and the GUI can't be accessed but from the console everything looks ok.

Causes:

• This problem occurs only when the R3000 has both nics in the same subnet, regardless of the mode (invisible/router/firewall). Having both nics in the same subnet is an incorrect configuration. In those situations the OS upgrade included in patch 2.2.00 causes the kernel to default to eth0 (instead of eth1).

Resolution:

If the R3000 is in invisible mode, give the listening interface (usually eth0) a non-routable ip address with a 32-bit netmask, like 1.2.3.4/32  If the R3000 is in router or firewal mode you'll need to give the nics ip addresses in different subnets - If you can't do that for whatever reason please contact Tech Support.

Notes: