[Olsr-dev] inconsistency in MID handling

[Peter Tarjan]

Hi,

> @peter are you using tip-tip or stable branch?

I am working with the stable branch.

I think I managed to fix the problem, but I am not convinced that this
is the way it should be handled. It's just an idea, please think about
it.

--- a/src/mid_set.c     2009-03-26 16:59:05.000000000 +0100
+++ b/src/mid_set.c     2009-05-07 11:34:57.200697890 +0200
@@ -567,6 +567,8 @@
      OLSR_PRINTF(1, "MID new: (%s, ", olsr_ip_to_string(&buf,
&message.mid_origaddr));
      OLSR_PRINTF(1, "%s)\n", olsr_ip_to_string(&buf, &tmp_adr->alias_addr));
      insert_mid_alias(&message.mid_origaddr, &tmp_adr->alias_addr,
message.vtime);
+    } else {
+      olsr_insert_routing_table(&tmp_adr->alias_addr,
olsr_cnf->maxplen, &message.mid_origaddr, OLSR_RT_ORIGIN_MID);
    }
    tmp_adr = tmp_adr->next;
  }


--
Peter