I am using an ns-3-dev version updated three weeks ago
(cloned from http://code.nsnam.org/ns-3-dev)
./waf --run 'flow_monitoring 106'
may return the same situation described in this thread.
Otherwise, in order to detect the time of the anomaly for checking the
routing tables, log the tcp-socket-base, and search for 'ReTxTimeout
Expired at time '.
Thank you very much.
(cloned from http://code.nsnam.org/ns-3-dev)
./waf --run 'flow_monitoring 106'
may return the same situation described in this thread.
Otherwise, in order to detect the time of the anomaly for checking the
routing tables, log the tcp-socket-base, and search for 'ReTxTimeout
Expired at time '.
Thank you very much.
No comments:
Post a Comment