| commit | 6d55cb91a0020ac0d78edcad61efd6c8cf5785a3 | |
| author | Timo Teräs <timo.teras@iki.fi> | |
| Wed, 3 Mar 2010 04:01:13 +0000 (3 04:01 +0000) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Thu, 4 Mar 2010 08:53:52 +0000 (4 00:53 -0800) | ||
| tree | 9aabbb2dac62f2e3ddcb8347da94df76f8976da7 | treesnapshot (tar.gz zip) |
| parent | c839d30a41dd92eb32d7fcfa2b4e99042fc64bf2 | commitdiff |
gre: fix hard header destination address checking
ipgre_header() can be called with zero daddr when the gre device is
configured as multipoint tunnel and still has the NOARP flag set (which is
typically cleared by the userspace arp daemon). If the NOARP packets are
not dropped, ipgre_tunnel_xmit() will take rt->rt_gateway (= NBMA IP) and
use that for route look up (and may lead to bogus xfrm acquires).
The multicast address check is removed as sending to multicast group should
be ok. In fact, if gre device has a multicast address as destination
ipgre_header is always called with multicast address.
Signed-off-by: Timo Teras <timo.teras@iki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
ipgre_header() can be called with zero daddr when the gre device is
configured as multipoint tunnel and still has the NOARP flag set (which is
typically cleared by the userspace arp daemon). If the NOARP packets are
not dropped, ipgre_tunnel_xmit() will take rt->rt_gateway (= NBMA IP) and
use that for route look up (and may lead to bogus xfrm acquires).
The multicast address check is removed as sending to multicast group should
be ok. In fact, if gre device has a multicast address as destination
ipgre_header is always called with multicast address.
Signed-off-by: Timo Teras <timo.teras@iki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
| net/ipv4/ip_gre.c | diffblobblamehistory |