diff options
author | Julian Anastasov <ja@ssi.bg> | 2012-10-08 11:41:15 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2012-10-08 17:42:35 -0400 |
commit | e81da0e113a1b7fc7449ae6213f65f89ccac6d06 (patch) | |
tree | 3d5bb2401d12017decf57263936784aa809e524a /arch/tile | |
parent | 863472454ce50d4ef0929c6aa738cc5d64b84679 (diff) | |
download | linux-e81da0e113a1b7fc7449ae6213f65f89ccac6d06.tar.gz linux-e81da0e113a1b7fc7449ae6213f65f89ccac6d06.tar.bz2 linux-e81da0e113a1b7fc7449ae6213f65f89ccac6d06.zip |
ipv4: fix sending of redirects
After "Cache input routes in fib_info nexthops" (commit
d2d68ba9fe) and "Elide fib_validate_source() completely when possible"
(commit 7a9bc9b81a) we can not send ICMP redirects. It seems we
should not cache the RTCF_DOREDIRECT flag in nh_rth_input because
the same fib_info can be used for traffic that is not redirected,
eg. from other input devices or from sources that are not in same subnet.
As result, we have to disable the caching of RTCF_DOREDIRECT
flag and to force source validation for the case when forwarding
traffic to the input device. If traffic comes from directly connected
source we allow redirection as it was done before both changes.
Avoid setting RTCF_DOREDIRECT if IN_DEV_TX_REDIRECTS
is disabled, this can avoid source address validation and to
help caching the routes.
After the change "Adjust semantics of rt->rt_gateway"
(commit f8126f1d51) we should make sure our ICMP_REDIR_HOST messages
contain daddr instead of 0.0.0.0 when target is directly connected.
Signed-off-by: Julian Anastasov <ja@ssi.bg>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'arch/tile')
0 files changed, 0 insertions, 0 deletions