summaryrefslogtreecommitdiffstats
path: root/net/ipv6
diff options
context:
space:
mode:
authorXin Long <lucien.xin@gmail.com>2019-06-02 13:10:24 +0200
committerDavid S. Miller <davem@davemloft.net>2019-06-06 01:59:21 +0200
commit0a90478b93a46bdcd56ba33c37566a993e455d54 (patch)
treed0adef52f77f02ee94d1111cb9bc537c539e81c4 /net/ipv6
parentMerge branch 's390-qeth-fixes' (diff)
downloadlinux-0a90478b93a46bdcd56ba33c37566a993e455d54.tar.xz
linux-0a90478b93a46bdcd56ba33c37566a993e455d54.zip
ipv4: not do cache for local delivery if bc_forwarding is enabled
With the topo: h1 ---| rp1 | | route rp3 |--- h3 (192.168.200.1) h2 ---| rp2 | If rp1 bc_forwarding is set while rp2 bc_forwarding is not, after doing "ping 192.168.200.255" on h1, then ping 192.168.200.255 on h2, and the packets can still be forwared. This issue was caused by the input route cache. It should only do the cache for either bc forwarding or local delivery. Otherwise, local delivery can use the route cache for bc forwarding of other interfaces. This patch is to fix it by not doing cache for local delivery if all.bc_forwarding is enabled. Note that we don't fix it by checking route cache local flag after rt_cache_valid() in "local_input:" and "ip_mkroute_input", as the common route code shouldn't be touched for bc_forwarding. Fixes: 5cbf777cfdf6 ("route: add support for directed broadcast forwarding") Reported-by: Jianlin Shi <jishi@redhat.com> Signed-off-by: Xin Long <lucien.xin@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv6')
0 files changed, 0 insertions, 0 deletions