From 70d728ffcff59dc0a2390988b66ddb0dad5f3559 Mon Sep 17 00:00:00 2001
From: david <david@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Wed, 16 May 2012 23:50:03 +0000
Subject: [PATCH] Make "failed to determine route" a warning, not a fatal
 error.

---
 CHANGELOG  | 5 +++++
 targets.cc | 4 +++-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG b/CHANGELOG
index be23fdfa3..abd3f1e7c 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -1,5 +1,10 @@
 # Nmap Changelog ($Id$); -*-text-*-
 
+o The message "nexthost: failed to determine route to ..." is now a
+  warning rather than a fatal error. Addresses that are skipped in
+  this way are recorded in the XML output as <target> elements. [David
+  Fifield]
+
 o [NSE] Added the script http-drupal-modules, which enumerates the installed
   Drupal modules using drupal-modules.lst. [Hani Benhabiles]
 
diff --git a/targets.cc b/targets.cc
index 676359afd..b058c71c7 100644
--- a/targets.cc
+++ b/targets.cc
@@ -372,7 +372,9 @@ Target *nexthost(HostGroupState *hs, const addrset *exclude_group,
           )) {
         t->TargetSockAddr(&ss, &sslen);
         if (!nmap_route_dst(&ss, &rnfo)) {
-          fatal("%s: failed to determine route to %s", __func__, t->NameIP());
+          log_bogus_target(inet_ntop_ez(&ss, sslen));
+          error("%s: failed to determine route to %s", __func__, t->NameIP());
+          continue;
         }
         if (rnfo.direct_connect) {
           t->setDirectlyConnected(true);