I already posted the results with TCPNice speed with udp.You can running the test with tcp packet?Please paste the resoult.
Nstream seems to be stable, but TCP traffic performance is not exciting as UDP ones.
Topped at 78/80 Mbps HDX no matter of the boards, way we measured and setup..
Please try this new BIOS. It can be installed with Xmodem transfer protocol from your terminal program (hyperterminal):
No problem with mac-telnet here too, both with v.3 and 2.9.x devices. Tried both on ethernet and wireless.i cannot confirm that, for me mac telnet is working as expected, check configuration, is /tool mac-server configuration ok?
Ok, so the answer is netinstall must be used some way.. thank you!You may try to find Windows box or run with VMware to run netinstall,
I think it should be cheaper rather than buy new license (especialy when you can avoid it).
What version are you using? we experienced some similar problems on heavy loaded RB, try 2.9.38 if you're using something else..Nobody's ever seen this? Anyone from Mikrotik know what these messages mean?
Well, it depends what is "a lot" for youNot many money
I do understand you, but after checking i followed plan B[
I am going from Argentina to the Orlando MUM to know about this first
I think he's announcing ok, if it was filtered the prefix wouldn't appear in the announcements.. @ubb: can you ask your upstream to send you a list of what receives from you?here is what I use that works - maybe it's the prefix length that needs to be set ?
sets the nexthop for the peer, so that the routes can be seen as reacheable, else they won't propagate..I'll try setting nexthop-choice to force-self and see what that does. What exactly does this do for me?
Yes, i understand your point, but unfortunately i can't help , except confirm that i've found much better results without nstreamthan 30 clients but someone else with an RB532 as AP without NStreme has +50 clients associated with no problems it does make you wounder why!
ok... i'll try..Ricky, you can try to run snooper,
'interface wireless snooper snoop wlan1 file=12345' and specify additional options.
All this commands will cause disconnect for remotely connected nodes.
This could indicate an MTU problem, try adjusting the MTU on you EoIP inteface to 1466 or even lower. Hotmail.com is a good place to test if your MTU is screwed, it wont show if its wrong.
No.. i want to have the traffic routed through the tunnel.. i.e. i want to use the eiop tunnel as a point-to-point interface, with public ips to the end user ethernet.Hi there Ricky,
Have you created a bridge and added the EoIP interface to it?
rb532 - cm9Hi
I have identical probs , but in 2.4GHZ band. I reduce ( but no solving ) the effect switching from B to G mode ..
With 9 / 10 client every work .
what type of board you have ? And what type of card ?
With Cm9 i can see both noise floor and signal to noise ratio.post upgrade 2.9.34 no wireless noise meter??????? rb532A two nmp-8602
2.9.31 yes view noise meters on wireless
Yes, on a congested link i tried once.. latency gets impacted, but pps (and cpu) get drammaticaly lower, with just simple aggregation, on an RB532.has anyone tried using packet packer in this situation to clump packets together and lower the overall pps ?
I see. the point is upgrade period for a level5 license bought after last november should not be expired, isn't it?The only way to upgrade if you license period is over (after the "old" licensing scheme) is doing a netinstall, I fear...
done... i have it on a couple of MT since yesterday.. seems no problems so far, i can tell you for sure the memory leak is not there anymoreSo, has anyone upgraded to v2.9.29 yet? Who is willing to test the waters first? <grin>