From 7bf004382faaec4048fe51fff89505f13a1bed3a Mon Sep 17 00:00:00 2001 From: ume Date: Thu, 28 Feb 2002 17:05:46 +0000 Subject: - In nd6_rtrequest(), ignored a route when it is created by cloning and is not a neighbor. see comments for the detailed reason. - Rejected the process of nd6_rtrequest() when the request is RESOLVE and the interface does not need neighbor caches. Obtained from: KAME MFC After: 1 week --- sys/netinet6/nd6.c | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) (limited to 'sys/netinet6') diff --git a/sys/netinet6/nd6.c b/sys/netinet6/nd6.c index 2dd1758..c5b8101 100644 --- a/sys/netinet6/nd6.c +++ b/sys/netinet6/nd6.c @@ -1110,6 +1110,27 @@ nd6_rtrequest(req, rt, info) return; } + if (req == RTM_RESOLVE && + (nd6_need_cache(ifp) == 0 || /* stf case */ + !nd6_is_addr_neighbor((struct sockaddr_in6 *)rt_key(rt), ifp))) { + /* + * FreeBSD and BSD/OS often make a cloned host route based + * on a less-specific route (e.g. the default route). + * If the less specific route does not have a "gateway" + * (this is the case when the route just goes to a p2p or an + * stf interface), we'll mistakenly make a neighbor cache for + * the host route, and will see strange neighbor solicitation + * for the corresponding destination. In order to avoid the + * confusion, we check if the destination of the route is + * a neighbor in terms of neighbor discovery, and stop the + * process if not. Additionally, we remove the LLINFO flag + * so that ndp(8) will not try to get the neighbor information + * of the destination. + */ + rt->rt_flags &= ~RTF_LLINFO; + return; + } + switch (req) { case RTM_ADD: /* -- cgit v1.1