Project

General

Profile

Error #143

Sluggish latencies between nodes.

Added by Marc Navarro over 7 years ago. Updated about 1 year ago.

Status:
Tancat
Priority:
Normal
Assignee:
-
Category:
802.11n driver
Target version:
-
Start date:
04/27/2012
Due date:
% Done:

0%


Description

  1. ping6 fd02::15:6d18:9d17:0:12
    PING fd02::15:6d18:9d17:0:12 (fd02::15:6d18:9d17:0:12): 56 data bytes
    64 bytes from fd02::15:6d18:9d17:0:12: seq=0 ttl=64 time=1.803 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=1 ttl=64 time=1.330 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=2 ttl=64 time=411.800 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=3 ttl=64 time=1.352 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=4 ttl=64 time=1.319 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=5 ttl=64 time=1092.421 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=6 ttl=64 time=92.341 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=7 ttl=64 time=1.409 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=8 ttl=64 time=1.344 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=9 ttl=64 time=886.158 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=10 ttl=64 time=1.294 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=11 ttl=64 time=1.325 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=12 ttl=64 time=1.350 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=13 ttl=64 time=467.195 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=14 ttl=64 time=1.289 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=15 ttl=64 time=1.282 ms
    64 bytes from fd02::15:6d18:9d17:0:12: seq=16 ttl=64 time=1040.740 ms
I'm testing on:
  1. qmpinfo nodes
    qmp13 fd02::80:4874:4a62:0:12 --> RSPro ( WLM200NX )
    qmp17 fd02::15:6d18:9d17:0:12 --> Loco
    qmpe4 fd02::15:6d9c:dce4:0:12 --> NSM5

Same issue on all source/dest wlan interface on "comunity mode".

History

#1 Updated by Marc Navarro over 7 years ago

I'm working on:
qmp: 5a56b122f2502f9074d544b05fb4f682beed4a2c commit. After gwck merge.
fwgen: 0e76692751985919e66444907076f1d852bd827a commit. from apr 13.

All images are created by: make T=XX build [ with and without DEV=1 ]

I got an /24 guifi.net ip range and assigned a /28 to each node in comunity mode.

#2 Updated by Marc Navarro over 7 years ago

More tests:

Yesterday I entered from internet no my home Lan and used Wan port on qmpe4 node to access mesh: Pings were normal.
Once at home I tried back over Lan port on qmp13 and results were back to sluggish, tried on another node with the same result.
I logged back again to Wan port on e4 and pings were normal again.

I'm using a cheap UFO TP-link to access mesh via lan interfaces. But after that i connected by cable to qmp17 and got the same sluggish result.

#3 Updated by Pau Escrich almost 7 years ago

It seems it was a problem related with the b6m-spread update packages.
After disable b6m-spread all worked fine.
Probably the problem was something related with a weak wifi link and an application which sends data quite often.

#4 Updated by Pau Escrich almost 7 years ago

  • Status changed from Nou to Resolt

#5 Updated by Roger Pueyo Centelles about 1 year ago

  • Status changed from Resolt to Tancat

Also available in: Atom PDF