linux-toradex.git/net/ipv4/arp.c, branch v3.2.15

net: Don't proxy arp respond if iif == rt->dst.dev if private VLAN is disabled

2012-03-01T00:30:57+00:00

[ Upstream commit 70620c46ac2b45c24b0f22002fdf5ddd1f7daf81 ]

Commit 653241 (net: RFC3069, private VLAN proxy arp support) changed
the behavior of arp proxy to send arp replies back out on the interface
the request came in even if the private VLAN feature is disabled.

Previously we checked rt->dst.dev != skb->dev for in scenarios, when
proxy arp is enabled on for the netdevice and also when individual proxy
neighbour entries have been added.

This patch adds the check back for the pneigh_lookup() scenario.

Signed-off-by: Thomas Graf 
Acked-by: Jesper Dangaard Brouer 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

neigh: Pass neighbour entry to output ops.

2011-07-18T06:11:17+00:00

This will get us closer to being able to do "neigh stuff"
completely independent of the underlying dst_entry for
protocols (ipv4/ipv6) that wish to do so.

We will also be able to make dst entries neigh-less.

Signed-off-by: David S. Miller

neigh: Kill ndisc_ops->queue_xmit

2011-07-17T01:30:59+00:00

It is always dev_queue_xmit().

Signed-off-by: David S. Miller

neigh: Kill neigh_ops->hh_output

2011-07-17T00:39:57+00:00

It's always dev_queue_xmit().

Signed-off-by: David S. Miller

ipv4: Inline neigh binding.

2011-07-13T08:12:28+00:00

Get rid of all of the useless and costly indirection
by doing the neigh hash table lookup directly inside
of the neighbour binding.

Rename from arp_bind_neighbour to rt_bind_neighbour.

Use new helpers {__,}ipv4_neigh_lookup()

In rt_bind_neighbour() get rid of useless tests which
are never true in the context this function is called,
namely dev is never NULL and the dst->neighbour is
always NULL.

Signed-off-by: David S. Miller

ipv4: Use universal hash for ARP.

2011-07-11T08:37:28+00:00

We need to make sure the multiplier is odd.

Signed-off-by: David S. Miller

net: gre: provide multicast mappings for ipv4 and ipv6

2011-03-30T07:10:47+00:00

My commit 6d55cb91a0020ac0 (gre: fix hard header destination
address checking) broke multicast.

The reason is that ip_gre used to get ipgre_header() calls with
zero destination if we have NOARP or multicast destination. Instead
the actual target was decided at ipgre_tunnel_xmit() time based on
per-protocol dissection.

Instead of allowing the "abuse" of ->header() calls with invalid
destination, this creates multicast mappings for ip_gre. This also
fixes "ip neigh show nud noarp" to display the proper multicast
mappings used by the gre device.

Reported-by: Doug Kehn 
Signed-off-by: Timo Teräs 
Acked-by: Doug Kehn 
Signed-off-by: David S. Miller

ipv4: Create and use route lookup helpers.

2011-03-12T23:08:42+00:00

The idea here is this minimizes the number of places one has to edit
in order to make changes to how flows are defined and used.

Signed-off-by: David S. Miller

ipv4: Make output route lookup return rtable directly.

2011-03-02T22:31:35+00:00

Instead of on the stack.

Signed-off-by: David S. Miller

net: arp_ioctl() must hold RTNL

2011-01-24T21:16:16+00:00

Commit 941666c2e3e0 "net: RCU conversion of dev_getbyhwaddr() and
arp_ioctl()" introduced a regression, reported by Jamie Heilman.
"arp -Ds 192.168.2.41 eth0 pub" triggered the ASSERT_RTNL() assert
in pneigh_lookup()

Removing RTNL requirement from arp_ioctl() was a mistake, just revert
that part.

Reported-by: Jamie Heilman 
Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller