diff --git a/Shorewall/known_problems.txt b/Shorewall/known_problems.txt
index d73979403..7d8c7d000 100644
--- a/Shorewall/known_problems.txt
+++ b/Shorewall/known_problems.txt
@@ -1,12 +1,12 @@
 1) In kernel 2.6.31, the handling of the rp_filter interface option was
    changed incompatibly. Previously, the effective value was determined
-   by the setting of net.ipv4.config.dev.proxy_arp logically ANDed with
-   the setting of net.ipv4.config.all.proxy_arp.
+   by the setting of net.ipv4.config.dev.rp_filter logically ANDed with
+   the setting of net.ipv4.config.all.rp_filter.
 
    Beginning with kernel 2.6.31, the value is the arithmetic MAX of
    those two values. 
 
-   Given that Shorewall sets net.ipv4.config.all.proxy_arp to 1 if
+   Given that Shorewall sets net.ipv4.config.all.rp_filter to 1 if
    there are any interfaces specifying 'routefilter', specifying
    'routefilter' on any interface has the effect of setting the option
    on all interfaces.
diff --git a/Shorewall/releasenotes.txt b/Shorewall/releasenotes.txt
index 08cc4479f..c92a21199 100644
--- a/Shorewall/releasenotes.txt
+++ b/Shorewall/releasenotes.txt
@@ -174,8 +174,8 @@ Shorewall 4.4.5 Patch Release 1.
 ----------------------------------------------------------------------------
 1)  In kernel 2.6.31, the handling of the rp_filter interface option was
     chan ged incompatibly. Previously, the effective value was determined
-    by the setting of net.ipv4.config.dev.proxy_arp logically ANDed with
-    the setting of net.ipv4.config.all.proxy_arp.
+    by the setting of net.ipv4.config.dev.rp_filter logically ANDed with
+    the setting of net.ipv4.config.all.rp_filter.
 
     Beginning with kernel 2.6.31, the value is the arithmetic MAX of
     those two values.