I have a hard time with mikrotik model:
RB2011UiAS-2HnD
I Have a router with internet connection (8Mb). We set configure to have internet using the mikrotik as DHCP, DNS, hotspot
on the router internet is speed, but through mikrotik (connected alone), it’s disappointing.
firewall filter:nothing, nat:masquerade mangle:nothing
route, dst:0..0.0.0/0 gateway Router IP.
So If I can have some help to understand that situation.
In above one, connection is okay.
In below, that’s where I have troubles. Pages opening fast in above scheme delay to load here. and during that time, browser says waiting for gogogle.net… stucks there a
while and then slowly load.
After resetting, get same situation. stuck at gogogle.net… for a while and slowly load.
I did and check all. maybe an option in the mikrotik need to be uncheck or check but which one?
Détermination de l’itinéraire vers dns.google [8.8.8.8]
avec un maximum de 30 sauts :
1 <1 ms <1 ms <1 ms 172.16.0.254
2 1 ms 1 ms 2 ms 192.168.1.1
3 * * * Délai d’attente de la demande dépassé.
4 31 ms 32 ms 35 ms 212.52.159.166
5 32 ms 32 ms * 10.10.1.5
6 161 ms 160 ms 168 ms ix-pos-9-0-0.core1.pye-paris.as6453.net [80.231.196.37]
7 160 ms 160 ms 161 ms if-xe-1-0-0-2.tcore1.pye-paris.as6453.net [80.231.154.45]
8 168 ms 160 ms 160 ms 72.14.202.66
9 161 ms 160 ms 161 ms 108.170.244.225
10 159 ms 159 ms 158 ms 216.239.48.151
11 160 ms 159 ms 159 ms dns.google [8.8.8.8]
Itinéraire déterminé.
Envoi d’une requête ‘Ping’ 8.8.8.8 avec 32 octets de données :
Réponse de 8.8.8.8 : octets=32 temps=159 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=159 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=160 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=159 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=159 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=159 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=160 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=164 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=160 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=160 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=160 ms TTL=49
Réponse de 8.8.8.8 : octets=32 temps=159 ms TTL=49
Are you sure it’s not a DNS issue? Did you try setting DNS manually on the PC to see if that makes a difference?
From your route trace it apperas the connection is fine as you can ping your modem from behind the mikrotik without issues. Ping times to your ISPs router to the pipe are rather high but nothing you can do about it (other than to ring em up and let 'em have it).
The one thing that comes to mind regarding slow speed issues is MTU size and MSS. Try pinging with the DNF flag set and see how high you can go. But other than that, I don’t think this is a general issue. To me it looks like more of a browsing issue. So with that the prime suspect is DNS. Oh and check your DHCP assigned gateways too. I’ve seen networks behaving oddly only to find out there was a second gateway assigned via DHCP.
Finally if it ain’t any of that and you made sure, NAT, firewall and all other rules like queues, etc are good, I’m out of ideas.
After reading all your suggestions and applied them, the final diagnostic I think of is hardware problem, the device itself.
I don’t see any other explanation.
Will change it.
Thanks all of you, for giving me a little of your time.
Hi, I’m new here and I don’t know how to create a specific question or post. so i am just gonna ask my question where i found its more related.
So, i recently got hold of the Mikrotik cloud router switch ( CRS212-1G-10S-1S+IN). I am connecting it a remote end of a radio link P2P connection. While the Master side of the radio link also have the same. But the remote end is not getting the bandwidth i send to it from the main radio. I swapped the SFPs for the device, got new SFPs and check. Still the bandwidth does not go above 30mbps while i am sending 50Mbps. And yes, there is no QOS policy applied on the remote router. I switched the router to the RB493H model router and it works perfectly on the remote end with giving enough bandwidth i want to send.
Did anyone ever encounter with this issue? if so how did you guys fix it and what can i do to fix the issue.