Page 1 of 1

Not bad for 106 KM :)

Posted: Sat Nov 28, 2015 6:25 am
by mickeymouse690
I must say im impressed. I was hoping to get around 30 Mbps. Was also not expecting this signal strength event though RadioMobile was spot on.! -58 both chains.!
notbad.png

Re: Not bad for 106 KM :)

Posted: Sat Nov 28, 2015 6:27 am
by mickeymouse690
I have to confess that i get half these results with same gear in semi urban environment at a third of the distance.!

Re: Not bad for 106 KM :)

Posted: Sat Nov 28, 2015 7:25 am
by chechito
I have to confess that i get half these results with same gear in semi urban environment at a third of the distance.!

whats your equipment??

Re: Not bad for 106 KM :)

Posted: Sat Nov 28, 2015 1:07 pm
by h3ll1
Test with TCP and post results

Re: Not bad for 106 KM :)

Posted: Sat Nov 28, 2015 1:28 pm
by macgaiver
Test with TCP and post results
Why? what benefit will that give?

Re: Not bad for 106 KM :)

Posted: Sat Nov 28, 2015 9:22 pm
by mickeymouse690
Link already in use with client so I can't easily get a computer behind both radio to test real tcp throughout. TCP tests with just the radios, I get around 180 Mbps.

Equipment
Netmetals
RocketDish 30 db

Client side is at a large tv and radio telecom site on top of a mountain so I didn't dare use a Mikrotik dish antenna with all the ice flying around off the towers in the winter, too damn thin the dish material. I can dent the dish with one finger.. The Rocket Dishs have already flown of buildings into brick walls with fair damage but not that bad considering what it just went through and have been put back in service. Sorry MT but make your Dishs thicker and I would be more than happy to use them :p. Love the Netmetals :)

Edit: Also using slant 45 on dish

Re: Not bad for 106 KM :)

Posted: Sun Nov 29, 2015 7:09 pm
by h3ll1
Test with TCP and post results
Why? what benefit will that give?
TCP test is closer to real life data

Re: Not bad for 106 KM :)

Posted: Mon Nov 30, 2015 7:45 am
by macgaiver
Test with TCP and post results
Why? what benefit will that give?
TCP test is closer to real life data
OMG not again!
Please, name me this "real life" traffic"???

1) speedtest?? - there is nothing "real life" here - it is sintetic single connection test,
2) Browsing?? - any modern browser using 8+ connections at the same, and connections are relatively short, so TCP bandwidth test will not represent anything
BTW not all browsing is not using TCP now - Google already moved to UDP - read this:
https://en.wikipedia.org/wiki/QUIC
So all your youtube videos actually use UDP now.
3) torrent download?? - it works with both protocols, but better with UDP.
4) gaming?? - uses both protocols, and in case of TCP - it is low speed connection so so TCP bandwidth test will not represent anything

bottom line:
TCP test is closer to real life data
it was true 10+ years ago, when i was in university Professors repeated this over and over again...
but that was 10+ years ago -in modern internet real traffic is "UDP".

while i was writing this post on my main gateway - 73,6% of client's traffic was UDP, 21.2% was TCP, rest was GRE, ICMP.

Re: Not bad for 106 KM :)

Posted: Mon Nov 30, 2015 9:19 am
by normis
TCP test is closer to real life data
could you please give an example of "real life TCP" ?

Re: Not bad for 106 KM :)

Posted: Mon Nov 30, 2015 10:42 pm
by InoX
while i was writing this post on my main gateway - 73,6% of client's traffic was UDP, 21.2% was TCP, rest was GRE, ICMP.
How can you tell? :shock:

Re: Not bad for 106 KM :)

Posted: Tue Dec 01, 2015 7:52 am
by macgaiver
How can you tell? :shock:
I created passthrough rules for TCP, UDP and ICMP and one rule for all traffic, that quickly found out that GRE was also present, it is easy to set up.

Re: Not bad for 106 KM :)

Posted: Tue Dec 01, 2015 1:44 pm
by h3ll1
Synthetic test TCP on mikrotik gives more credible results for passing data over wireless links. This is my opinion based on my personal experience. I have seen speeds over 500Mbps when using UDP, but TCP is near 200Mbps - that is big difference. So i expect on this particular link TCP speed test should be around 110Mbps, which is actualy OK.

Re: Not bad for 106 KM :)

Posted: Tue Dec 01, 2015 8:08 pm
by wispwest
Synthetic test TCP on mikrotik gives more credible results for passing data over wireless links. This is my opinion based on my personal experience. I have seen speeds over 500Mbps when using UDP, but TCP is near 200Mbps - that is big difference. So i expect on this particular link TCP speed test should be around 110Mbps, which is actualy OK.
Also check the CPU on the routerboard when running TCP test, it usually maxes out, so your TCP test is ONLY limited to what the CPU can handle. I've done TCP tests over PtP links on the radios themselves, and seen horrible results, but then test with RB1100AHx2 boards behind each end, and seen 300mb/s, whereas the ptp radios can only handle 80-120

Re: Not bad for 106 KM :)

Posted: Thu Dec 10, 2015 6:24 am
by Zorro
if you(or anyone else) obessed with "real usage/traffic"-alike stress/testing - then (commercial or free)software packages like NetChariot - had several relevant patterns for such testing.
or you can simply replay Exactly captured traffic - back again and again ;)