(Just agreeing with above quote and put to rest the minds of fellow noobs.)your hardware and signal strenght must be strong. What is your hardware and your signal?
We tried in the Lab. RB500 maximum TCP is around 20Mbps, RB300 40Mbps, RB600 40Mbps with maximum signal.
udp or tcp? our tests never got past 33mbps tcp. What setup were u using?(Just agreeing with above quote and put to rest the minds of fellow noobs.)your hardware and signal strenght must be strong. What is your hardware and your signal?
We tried in the Lab. RB500 maximum TCP is around 20Mbps, RB300 40Mbps, RB600 40Mbps with maximum signal.
It's true what they say - bigger is better! Or in this case, faster is better. Regardless of signal strength, the hardware needs to be able to handle the volume of data too. We tried an rb600; maximum internal speed was about 60 Mbps and maximum wireless link speed was about 41 Mbps over ~6km.
Picture a brand new highway as optimal signal strength; your horse and buggy will only be able to go so fast!
You never measure a wireless link speed in TCP. WiFi is Simplex and TCP is a full duplex protocol. I am doing +60 Mbit UDP on a Routerboard 333 one direction. If i add a radio/antenna i can either bundle 2 links and get around 80Mbit UDP or use it as 2 seperate links, one for each direction and get full duplex, ie + 60/60Mbit TCPudp or tcp? our tests never got past 33mbps tcp. What setup were u using?(Just agreeing with above quote and put to rest the minds of fellow noobs.)your hardware and signal strenght must be strong. What is your hardware and your signal?
We tried in the Lab. RB500 maximum TCP is around 20Mbps, RB300 40Mbps, RB600 40Mbps with maximum signal.
It's true what they say - bigger is better! Or in this case, faster is better. Regardless of signal strength, the hardware needs to be able to handle the volume of data too. We tried an rb600; maximum internal speed was about 60 Mbps and maximum wireless link speed was about 41 Mbps over ~6km.
Picture a brand new highway as optimal signal strength; your horse and buggy will only be able to go so fast!
Isn't WiFi actually Half-Duplex?WiFi is Simplex and TCP is a full duplex protocol
Half duplex / Simplex. This is why TCP goes slower. UDP is connectionless and TCP needs an ACK back for every packet it sends.Isn't WiFi actually Half-Duplex?WiFi is Simplex and TCP is a full duplex protocol
You may experience that the TCP test is slower when you do it directly between the boards - we have seen it too.Yes, TCP bandwidth test. The test done on two RB600 latest O.S.
Yes, TCP and UDP bandwidth tests done between the two boards directly!! Should we reach more? How much?
This was not a solution, only a "How to test speed on links".You may experience that the TCP test is slower when you do it directly between the boards - we have seen it too.Yes, TCP bandwidth test. The test done on two RB600 latest O.S.
Yes, TCP and UDP bandwidth tests done between the two boards directly!! Should we reach more? How much?
You should use test TCP bandwidth test through those routers then you will get the best speed
For UDP you can run directly between the routers, but I also recommend to do it through the routers.
If you set up 2 WDS links with Nstreme in routed mode you can get 70/70Mbit/s FD. For some reason protocols like Dual-Nstreme, Bonding and EoIP doesn't work well on V3.This was not a solution, only a "How to test speed on links".You may experience that the TCP test is slower when you do it directly between the boards - we have seen it too.Yes, TCP bandwidth test. The test done on two RB600 latest O.S.
Yes, TCP and UDP bandwidth tests done between the two boards directly!! Should we reach more? How much?
You should use test TCP bandwidth test through those routers then you will get the best speed
For UDP you can run directly between the routers, but I also recommend to do it through the routers.
Problem(all tested with tcp ftp traffic ~1400 avg packet size -- nearly ideal ):
rb600 - rb600 wds turbo: 4.21MByte/s (same with rb333)
rb600 - rb600 wds turbo nstreme: 6.21 - 8.1 Mbyte/s (same with rb333)
rb600 - rb600 nstreme 2 : 5Mbyte/s up/3 Mbyte/s down (better with rb333 but this is installation specific)
bonding:
bonding over wireless only works if you dont enable nstreme (speed nearly 7Mbyte/sec same as nstreme link).
bonding over 2 eoip interfaces over 2 wireless nstreme can reach 35Mbit/s on each device (70 Mbit/sec)
(bonding method balance-rr this works other methods can't works with scenario above)
cpu max at ~70%
conclusion: rb600 more powerful than rb333 but you unable to use this power.
This is the problem.