Hello everyone, I've resolved the issue and now it is working. I missed setting event service device value as physical interface. after setting that it works.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE eventservice SYSTEM "file:///usr/share/emane/dtd/eventservice.dtd"> <eventservice> <param name="eventservicegroup" value="224.1.2.8:45703"/> <param name="eventservicedevice" value="eth0"/> <generator definition="eelgenerator.xml"/> </eventservice> Sincerely, On Tue, Feb 9, 2016 at 9:00 AM, <[email protected]> wrote: > Send emane-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of emane-users digest..." > > > Today's Topics: > > 1. Running EMANE without containers ([REDACTED]) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 8 Feb 2016 11:35:44 -0800 > From: [REDACTED] <[email protected]> > Subject: [emane-users] Running EMANE without containers > To: emane-users <[email protected]> > Message-ID: > <CA+yXOhNx3KMdTAd9dvMsf2jn8PhFAWJ3= > [email protected]> > Content-Type: text/plain; charset="utf-8" > > Hello everyone, > > I am trying to setup simple scenario on EMANE without the containers. > I have two machines which are connected using switch > Machine1: > Physical interface eth0: 192.168.1.1 platform1.XML > > Machine2: > Physical interface eth0:192.168.1.2 platform2.xml > > I've successfully brought up EMANE on each machine without containers like > > platform1.xml on machine one emane interface : 10.100.0.1 emane0 > > AND > > platform2.xml on machine two emane interface : 10.100.0.2 emane0 > > but I can't see any traffic hits emane interface and I confirm that with > checking emane statistics. > I've set OTA manager and eventservice manager as eth0 which is the physical > interface on my setup. > here is my platform configuration setup: > > platform1.xml > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE platform SYSTEM "file:///usr/share/emane/dtd/platform.dtd"> > <platform> > <param name="otamanagerchannelenable" value="on"/> > <param name="otamanagerdevice" value="eth0"/> > <param name="otamanagergroup" value="224.1.2.8:45702"/> > <param name="eventservicegroup" value="224.1.2.8:45703"/> > <param name="eventservicedevice" value="eth0"/> > <param name="controlportendpoint" value="0.0.0.0:47000"/> > > <nem id="1" definition="ieee80211abgnem.xml"> > <transport definition="transvirtual.xml"> > <param name="address" value="10.100.0.1"/> > <param name="mask" value="255.255.255.0"/> > </transport> > <phy> > <param name="frequencyofinterest" value="0.4G"/> > <param name="frequency" value="0.4G"/> > </phy> > </nem> > </platform> > > > platform2.xml > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE platform SYSTEM "file:///usr/share/emane/dtd/platform.dtd"> > <platform> > <param name="otamanagerchannelenable" value="on"/> > <param name="otamanagerdevice" value="eth0"/> > <param name="otamanagergroup" value="224.1.2.8:45702"/> > <param name="eventservicegroup" value="224.1.2.8:45703"/> > <param name="eventservicedevice" value="eth0"/> > <param name="controlportendpoint" value="0.0.0.0:47000"/> > > <nem id="1" definition="ieee80211abgnem.xml"> > <transport definition="transvirtual.xml"> > <param name="address" value="10.100.0.2"/> > <param name="mask" value="255.255.255.0"/> > </transport> > <phy> > <param name="frequencyofinterest" value="0.4G"/> > <param name="frequency" value="0.4G"/> > </phy> > </nem> > </platform> > > > and here is routing table on machine one > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 10.0.3.0 0.0.0.0 255.255.255.0 U 0 0 0 > lxcbr0 > 192.168.0.0 0.0.0.0 255.255.255.0 U 1 0 0 > eth0 > 10.100.0.0 0.0.0.0 255.255.255.0 U 0 0 0 > emane0 > 224.1.2.8 0.0.0.0 255.255.255.255 UH 0 0 0 > eth0 > > > Any help please regarding this issue? > > > Thanks, > Sam > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://pf.itd.nrl.navy.mil/pipermail/emane-users/attachments/20160208/47b80ef4/attachment-0001.html > > ------------------------------ > > _______________________________________________ > emane-users mailing list > [email protected] > http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users > > > End of emane-users Digest, Vol 72, Issue 5 > ****************************************** >
_______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
