nstream issue

randyloveless · May 10, 2005, 3:13am

why does our new test link keep dropping connection . if i turn off nstream wont drop . but as soon as nstream is on it will drop every couple of min.

now the thruput is better with nstream on but cannot have the link going up and down. tryied restricting link to 6mb running 5ghz didnt seem to make much difference .

about a mile from ap.
signal is 82 to 85 now i thought i read somewhere about this . but never got a clear answer .

should we not be using nstream for standard links . or is it specificly designed for short strong signals only . and if this is the case what are we suppose to do about making the links more effiecent.

stephenpatrick · May 10, 2005, 5:34am

IMHO Nstreme only works well with good signal levels.

I’m guessing here, but by re-packetising the data into “wireless friendly chunks”, if you then lose packets due to noise/poor signal, it means you lose more than one packet of real data - and the Nstreme protocol then has to re-sync itself.

As with most things, there is no free lunch …

[No criticism intended: I think Nstreme is excellent, and will use it wherever we can]

randyloveless · May 10, 2005, 11:07pm

ok gota another link that is -68 station -69 ap side . when running nstream works great doesnt drop connection . but get very slow ping rates

this is without Nstream running

Pinging 192.168.10.112 with 32 bytes of data:

Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=12ms TTL=63
Reply from 192.168.10.112: bytes=32 time=7ms TTL=63
Reply from 192.168.10.112: bytes=32 time=7ms TTL=63
Reply from 192.168.10.112: bytes=32 time=7ms TTL=63
Reply from 192.168.10.112: bytes=32 time=11ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=10ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=5ms TTL=63
Reply from 192.168.10.112: bytes=32 time=7ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=10ms TTL=63
Reply from 192.168.10.112: bytes=32 time=7ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=7ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=7ms TTL=63
Reply from 192.168.10.112: bytes=32 time=7ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63

This is with Nstream running

Pinging 192.168.10.112 with 32 bytes of data:

Reply from 192.168.10.112: bytes=32 time=77ms TTL=63
Reply from 192.168.10.112: bytes=32 time=15ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=28ms TTL=63
Reply from 192.168.10.112: bytes=32 time=68ms TTL=63
Reply from 192.168.10.112: bytes=32 time=58ms TTL=63
Request timed out.
Reply from 192.168.10.112: bytes=32 time=29ms TTL=63
Reply from 192.168.10.112: bytes=32 time=39ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=58ms TTL=63
Reply from 192.168.10.112: bytes=32 time=49ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=19ms TTL=63
Request timed out.
Reply from 192.168.10.112: bytes=32 time=29ms TTL=63
Reply from 192.168.10.112: bytes=32 time=18ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=39ms TTL=63
Reply from 192.168.10.112: bytes=32 time=49ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=39ms TTL=63
Reply from 192.168.10.112: bytes=32 time=40ms TTL=63
Reply from 192.168.10.112: bytes=32 time=38ms TTL=63
Reply from 192.168.10.112: bytes=32 time=19ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=28ms TTL=63
Reply from 192.168.10.112: bytes=32 time=59ms TTL=63
Reply from 192.168.10.112: bytes=32 time=49ms TTL=63
Reply from 192.168.10.112: bytes=32 time=39ms TTL=63

This is my wireless config
by RouterOS 2.9beta19

software id = W7FC-3TT

/ interface wireless
set wlan1 name="wlan1" mtu=1500 mac-address=00:0B:6B:33:CC:51 arp=proxy-arp
disable-running-check=no radio-name="Escamilla Twr1" mode=ap-bridge
ssid="srs networks escamilla twr" area="" frequency-mode=manual-txpower
country="united states" antenna-gain=23 frequency=2432 band=2.4ghz-b/g
scan-list=2432,2412 rate-set=configured supported-rates-b=5.5Mbps,11Mbps
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps
basic-rates-b=5.5Mbps basic-rates-a/g=6Mbps max-station-count=25
ack-timeout=dynamic tx-power=default tx-power-mode=default
noise-floor-threshold=default periodic-calibration=default
burst-time=disabled fast-frames=yes dfs-mode=none antenna-mode=ant-a
wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no
update-stats-interval=disabled default-authentication=no
default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0
hide-ssid=yes security-profile=default disconnect-timeout=3s
on-fail-retry-time=100ms preamble-mode=both comment="" disabled=no
/ interface wireless nstreme
set wlan1 enable-nstreme=yes enable-polling=yes framer-policy=dynamic-size
framer-limit=3200
/ interface wireless manual-tx-power-table
set wlan1 manual-tx-powers=1Mbps:17,2Mbps:17,5.5Mbps:17,11Mbps:17,6Mbps:17,9Mbp
s:17,12Mbps:17,18Mbps:17,24Mbps:17,36Mbps:17,48Mbps:17,54Mbps:17
/ interface wireless security-profiles
set (unknown) name="default" mode=none wpa-unicast-ciphers=""
wpa-group-ciphers="" pre-shared-key="" static-algo-0=none static-key-0=""
static-algo-1=none static-key-1="" static-algo-2=none static-key-2=""
static-algo-3=none static-key-3="" static-transmit-key=key-0
static-sta-private-algo=none static-sta-private-key=""
radius-mac-authentication=no group-key-update=5m
/ interface wireless align
set frame-size=300 active-mode=yes receive-all=no filter-mac=00:00:00:00:00:00
ssid-all=no frames-per-second=25
/ interface wireless access-list
add mac-address=00:0F:3D:A0:00:83 interface=wlan1 authentication=yes
forwarding=yes ap-tx-limit=0 client-tx-limit=0 private-algo=none
private-key="" comment="" disabled=no
/ interface wireless snooper
set multiple-channels=yes channel-time=200ms receive-errors=no
/ interface wireless sniffer
set multiple-channels=no channel-time=200ms only-headers=no receive-errors=no
memory-limit=10 file-name="" file-limit=10 streaming-enabled=no
streaming-server=0.0.0.0 streaming-max-rate=0

any help

_ASM · May 11, 2005, 2:54am

use basic-rates-a/g=6,9,12,18,24 and supported-rates-a/g=6,9,12,18,24

Signal strenght is critical for 36 Mbit OFDM

randyloveless · May 11, 2005, 2:59am

thanks will play with the setting tonight

Randy

randyloveless · May 11, 2005, 3:07am

better but why are there so many high pings what else can i do to improve this

Randy

Pinging 192.168.10.112 with 32 bytes of data:

Reply from 192.168.10.112: bytes=32 time=13ms TTL=63
Reply from 192.168.10.112: bytes=32 time=19ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=10ms TTL=63
Reply from 192.168.10.112: bytes=32 time=18ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=18ms TTL=63
Reply from 192.168.10.112: bytes=32 time=69ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=19ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=18ms TTL=63
Reply from 192.168.10.112: bytes=32 time=30ms TTL=63
Reply from 192.168.10.112: bytes=32 time=61ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=28ms TTL=63
Reply from 192.168.10.112: bytes=32 time=38ms TTL=63
Reply from 192.168.10.112: bytes=32 time=38ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=18ms TTL=63
Reply from 192.168.10.112: bytes=32 time=18ms TTL=63
Reply from 192.168.10.112: bytes=32 time=38ms TTL=63
Reply from 192.168.10.112: bytes=32 time=188ms TTL=63
Reply from 192.168.10.112: bytes=32 time=18ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=145ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=19ms TTL=63
Reply from 192.168.10.112: bytes=32 time=18ms TTL=63
Reply from 192.168.10.112: bytes=32 time=6ms TTL=63
Reply from 192.168.10.112: bytes=32 time=88ms TTL=63
Reply from 192.168.10.112: bytes=32 time=19ms TTL=63
Reply from 192.168.10.112: bytes=32 time=7ms TTL=63
Reply from 192.168.10.112: bytes=32 time=48ms TTL=63
Reply from 192.168.10.112: bytes=32 time=9ms TTL=63
Reply from 192.168.10.112: bytes=32 time=18ms TTL=63
Reply from 192.168.10.112: bytes=32 time=29ms TTL=63
Reply from 192.168.10.112: bytes=32 time=19ms TTL=63
Reply from 192.168.10.112: bytes=32 time=68ms TTL=63
Reply from 192.168.10.112: bytes=32 time=59ms TTL=63
Reply from 192.168.10.112: bytes=32 time=38ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=48ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=8ms TTL=63
Reply from 192.168.10.112: bytes=32 time=37ms TTL=63
Reply from 192.168.10.112: bytes=32 time=58ms TTL=63

john2 · May 11, 2005, 6:34am

It appears that you have been playing around with all your rate sets and maybe more. You should not touch those unless you really know what you are doing. If you do play with those things and don’t know much about them, you should do a reset to defaults. Currently you will have to reset the whole config. In future versions there will be resets to default for each area (interface, queues…)

stephenpatrick · May 11, 2005, 8:03am

Hi John2

It would be nice to have an explanation of that “don’t play with rate settings”.
On most wireless kit, it’s normal to exclude rates that are too high (due to low SNR, interference) or too low (slows everyone down) and just operate in the middle.
Why is Mikrotik different?

Regards

randyloveless · May 12, 2005, 4:21am

john

then how do i get my setting back to default . do i uninstall wireless package the reinstall it //.?

when the setting where set to factory started settings . had same issue that is why i started tweaking it

Randy

rpingar · May 12, 2005, 5:50am

I think you have some interferences on that channel.
try to use dfs to select a different one or try to change the polarity of your antenna.
Some time we got a great benefit rotating the antenna. First step is rotating 45° and the second rotating 90°.

Nstream is working great when all rf issue are fixed. The cm9 also is doing great about it in 2.9rc1. We are very satisfied. Hope to see some improvment into the cpu utilizzation.
Rosario

tully · May 12, 2005, 10:17am

The wireless algorithms are optimizing the throughput, therefore it will (should not) help speed by changing these settings. If you change the basic rates support to higher rates, then you can lose important link management frames – which will really slow everything down.

John

randyloveless · May 12, 2005, 4:16pm

so how do i get the settings back to default?

randy