EMANE events not restricted to localhost lo device

[GoogleCodeExporter]

Two instances of CORE running on the same network will interfere with each 
other. To generate location events, CORE uses libemaneeventservice.

The library documentation says:
* The default values are: group 224.1.2.8, port 45703, multicast  loop
  enabled (1), TTL 32.  No default multicast device is specified.  The
  kernel routing table is used.

Even if the device is set to lo, the events will leak out usually due to the 
host's default route. CORE should consider the OTA manager device and Event 
service device set in the EMANE global config, and add an appropriate multicast 
route for the configured interface.

Original issue reported on code.google.com by ahrenh...@gmail.com on 9 May 2011 at 6:50

[GoogleCodeExporter]

Original comment by ahrenh...@gmail.com on 2 Apr 2013 at 8:55

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Changed from Defect to Enhancement because this is an 
EMANE-implementation-specific feature and not a bug with CORE.

This is a new feature request where CORE could possibly manage different 
multicast groups/port numbers used with EMANE so different sessions on the same 
network do not interfere with each other. Also, static routes could be added 
along with firewall rules for isolation.

Original comment by ahrenh...@gmail.com on 28 Jul 2014 at 3:01

• Added labels: Type-Enhancement
• Removed labels: Type-Defect