[[=== SYSTEM INFORMATION ====]] HOST OPERATING SYSTEM: Ubuntu 14.04.1, 12.0.4.5
HOST ARCHITECTURE: x86_64
TARGET OPERATING SYSTEM (if different): N/A
TARGET ARCHITECTURE (if different): N/A
COMPILER and COMPILER VERSION (if applicable): gcc 4.8.2-19ubuntu1
[[=== VERSION INFORMATION ====]]
EMANE VERSION: 0.9.2
ACE VERSION: libace-6.0.3+dfsg-0
LIBXML2 VERSION: libxml2-2.9.1+dfsg1-3ubuntu4
LIBPCAP_VERSION (if applicable): N/A
WINPCAP_VERSION (if applicable): N/A
EMANE ADD-ON NAMES and VERSIONS (if applicable): N/A
[[== INSTALLATION INFORMATION ==]
EMANE INSTALLATION METHOD (MAKE INSTALL, RPM, OTHER)
(if applicable): debs
[[=== PROBLEM INFORMATION ====]]
TYPE (COMPILATION, INSTALLATION, EXECUTION, OTHER): EXECUTION
BRIEF SUMMARY:
I'm trying to update CORE to support EMANE 0.9.2. When I use RfPipe or 802.11
models, with 2-ray, freespace, or pathloss propagation models, I'm not able to
get packets to drop. Maybe my configuration is incorrect?
DETAILED DESCRIPTION:
REPEAT BY:
I could send you a patch for CORE to repeat if necessary. It simply involves
placing 3 routers and a WLAN, choosing the EMANE model, and trying to move a
node out of range (for 2-ray/freespace), or using the emaneevent-pathloss tool
(for pathloss).
CONFIGURATION:
3 NEMs using virtual transport on one platform. See attached XML.
ATTACHED FILE DESCRIPTION:
Attached tarball contains these files:
platform.xml
n4emane_ieee80211abgmac.xml
n4emane_ieee80211abgnem.xml
n4emane_ieee80211abgphy.xml
n4transvirtual.xml
SAMPLE FIX/WORKAROUND:
Also I recompiled the debs using this line in the debian/rules file:
override_dh_auto_configure:
dh_auto_configure -- --with-verbose-logging
I was hoping to get something useful out of emane.log with log level 4. This
was the only output (using RfPipe model, three nodes, you can see OSPFv3 hello
packets every 2 seconds):
14:36:04.070752 DEBUG TRANSPORTI 001 VirtualTransport::readDevice src 1, dst
65535, dscp 48, length 106
14:36:04.070839 DEBUG TRANSPORTI 003 VirtualTransport::processUpstreamPacket
src 1, dst 65535, dscp 48, length 106
14:36:04.070837 DEBUG TRANSPORTI 002 VirtualTransport::processUpstreamPacket
src 1, dst 65535, dscp 48, length 106
14:36:06.036799 DEBUG TRANSPORTI 001 EthernetTransport::lookupArpCache no nem
found for 33:33:00:00:00:05, using broadcast mac address
14:36:06.036913 DEBUG TRANSPORTI 001 VirtualTransport::readDevice src 1, dst
65535, dscp 48, length 114
14:36:06.037112 DEBUG TRANSPORTI 003 VirtualTransport::processUpstreamPacket
src 1, dst 65535, dscp 48, length 114
14:36:06.037109 DEBUG TRANSPORTI 002 VirtualTransport::processUpstreamPacket
src 1, dst 65535, dscp 48, length 114
14:36:06.081926 DEBUG TRANSPORTI 003 EthernetTransport::lookupArpCache no nem
found for 33:33:00:00:00:05, using broadcast mac address
14:36:06.081989 DEBUG TRANSPORTI 003 VirtualTransport::readDevice src 3, dst
65535, dscp 48, length 106
14:36:06.082091 DEBUG TRANSPORTI 001 VirtualTransport::processUpstreamPacket
src 3, dst 65535, dscp 48, length 106
14:36:06.082099 DEBUG TRANSPORTI 002 VirtualTransport::processUpstreamPacket
src 3, dst 65535, dscp 48, length 106
14:36:06.089069 DEBUG TRANSPORTI 002 EthernetTransport::lookupArpCache no nem
found for 33:33:00:00:00:05, using broadcast mac address
When I move nodes (and have CORE generate location events) I can see the events
in the log:
14:38:09.127758 DEBUG EventService packet received len: 65
14:38:09.127833 DEBUG PHYI 001 FrameworkPHY::processEvent event id: 100
14:38:09.127840 DEBUG PHYI 003 FrameworkPHY::processEvent event id: 100
14:38:09.127853 DEBUG PHYI 002 FrameworkPHY::processEvent event id: 100
14:38:09.127886 DEBUG PHYI 001 FrameworkPHY::processEvent location event: nem:
1 position: lat: 47.575160 lon: -122.119025 alt: 2.000000 orientation: none
velocity: none
14:38:09.127888 DEBUG PHYI 003 FrameworkPHY::processEvent location event: nem:
1 position: lat: 47.575160 lon: -122.119025 alt: 2.000000 orientation: none
velocity: none
14:38:09.127899 DEBUG PHYI 002 FrameworkPHY::processEvent location event: nem:
1 position: lat: 47.575160 lon: -122.119025 alt: 2.000000 orientation: none
velocity: none
(As a side note, how can I get this output in the log file?: "MACI %03hu %s
upstream EOR processing: src %hu, dst %hu, max noise %f, signal in noise %s,
SINR %f")
sample-core-emane-0.9.2-xml.tgz
Description: sample-core-emane-0.9.2-xml.tgz
_______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
