Just 1000? So it doesn't worth for this.. A Dell R210 can handle a bit more than that (PPPoE+dynamic queue+1 MSS rule) even on version 5.25.http://forum.mikrotik.com/viewtopic.php?f=2&t=75864
The response I got to my ticket was 1000 Sessions.
You tested it as a PPPoE server with 10.000 clients?it's been tested, you can believe me or not, but it's a fact
What version are you using? We are still in 3.13 because vesions after 3.13 are not stable for dual core CPU.What issue? Its gone!Any news about this issue?
This is not a solution for me. If I went to dual core CPU was because I already reach the limit for single core CPU.Swap CPU's to a really fast single core for time being?
No response from MK team.Have 17+ days of uptime on 3.13 with fixes from Mikrotik and no PPPoE queues are acting up. Did anyone find out if 3.15 has these fixes in it?
I really don´t understand why they do that.may MT confirm the HCI fix is inside the 3.15?
I don't see it into the change log.
Nothing yet. They are unable to enter my Mk router (I created a port forward rule and it works for me outside my network but doesn´t work for them)Hi josefranco,
may you update on the status of progress?
Still qaiting about the queue issue come up?
What???? On a Cisco Router??????Was looking to see if anyone has ever tried loading Mikrotik onto a Cisco Router or Dell PowerEdge or others?
No, they are really using it. We can see the over traffic at all equipments (switchs, routers, radios, etc).Ops, maybe we are being misled to believe the clients are using the extra bandwidth without actually using it?
We updated some MK routers (x86) to 3.13 where we have more problems with this bug. But we have to wait some days to see.any update from who is testing 3.13?
then please report also the platform, RB or x86.
I hope this fix is not the same as 3.12 beta because as told above the problem was not fixed with this beta version.ROS 3.12 is now released; change log tells that problem was fixed. Any one tested this version yet??
just make a simple queue with the same p2p parameter, very similar. but remember - if that uTorrent uses encryption - you can't limit it, only drop it.
No, I'm serious. If support promised that bug is fixed in next release - Did you try the fixed release?
How do you expect MikroTik to fix bugs, magically apply fixes to your system without upgrade???
In this case I don´t think it´s related to multi-core cpu. I had this problem with single core CPU too.it means multi core cpu.
It´s a P4 3.4Ghz dual-core with intel server mobo.Is it a multi-cpu box or an old fashion single core?We have some packetloss with version 3.7 and Intel Gigabit NIC. I don´t know if with Broadcom is worst but we have this problem with Intel (PCI or PCI-E).
But how change the queue type will help on it?Should be a simple PCQ queue
I´m trying to limit all users with one queue.Are you trying to limit p2p for all users or each user individually?
For us since 3.4 it was already stable with multi-cpu=yes, but it´s not helping to enable the second core since I continue to have dropped packets.Any experience on multi-cpu=yes about 3.7?
is it stable the smp verision about pppoe server?
Just to know have kind of little performance problem you have?We do not have any problems with 3.7 build time Mar/27/2008.
We run it 4 days on 4 PPPoE server with 500-800 active connections each.
We have only little performance problems that are common for older versions 2.9.x
Glad to hearDon't wory, 3.7 seems to be really very good.
Running 24 hours, no problems yet.
I have this same problem since version 2.9.50, so rollback didn´t solve my problem. But with older versions (2.9.4x) works fine.Hope that "7" will be lucky number I have same problem, but i rolled back to 2.9.51. I can't afford this to happen in my net.
Ok, I think they will release it soon..MT sent me to check corrections.
Good news!it seems they found. I am testing 3.7 and it works much more better...
Let´s cross our fingers and hope they find a solution as soon as possible.I have reply from MT support, they confirmed problem and they are working on solution.