Hello, this is my first post. I have a Mikrotik RB3011 installed and everything except Google Drive Desktop works. When we add a file it gets stuck and does not synchronize. I have tried directly with the ISP (MOVISTAR) and if it works. Someone who can help me?
Sounds like a google drive problem not an MT problem.
There is no functionality in MT that synchronizes drives???
I think he means that the sync feature won’t work for him as a result of something the MikroTik router/firewall is doing. Ya dig what I’m saying? Trying to access service X through the tik doesn’t work. Accessing servic X through some other router does. But OP gives us nothing to even work with other than a vague observation.
If PPPoE is used towards the provider it could be MTU-related, but that would also affect other HTTPS sites.
I’ve been using a RB3011 for many years and I’ve seen my share of weirdness from time to time after updates, but some thinkering on PPPoE/MTU then solved it etc.
But with only this kind of information…not much to go on…
PPPoE is used?
You have any DNS-filtering services running on your LAN
No other websites affected ? Just only “drive.google.com” ? (actually that will use QUIC protocol I guess these days, which is UDP/443 and desiged by Google by the way) => the desktop app will most like also use QUIC
Post sanitized version of your config (probably what others will ask anyway before spending any time on this)
Perhaps after you have provided enough information.
See Getting Answers and How to Report Bugs Effectively
@anav’s NEW USER POSTING FOR ASSISTANCE
Getting the most out of this forum
It's okay. This is the programming. It also happens that the PCs have Internet, however the little ball in the world appears that they do not have Internet. I have also tried with an ISP (4G) and the same thing happens.
\
sep/02/2022 19:26:18 by RouterOS 6.49.6
software id = 6KD5-HCWR
model = RB3011UiAS
serial number = XXXXXXXXX
/interface bridge
add name=BRIDGE-LAN
/interface ethernet
set [ find default-name=ether1 ] comment=ether1 name=WAN
/interface pppoe-client
add add-default-route=yes disabled=no interface=WAN name=pppoe-out1 user=
adslppp@telefonicanetpa
/interface vlan
add interface=WAN name=VLAN6 vlan-id=6
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=dhcp_pool0 ranges="192.168.50.2-192.168.50.54,192.168.50.56-192.168.5
0.99,192.168.50.101-192.168.50.129,192.168.50.151-192.168.50.191,192.168.5
0.193-192.168.50.254"
/ip dhcp-server
add address-pool=dhcp_pool0 disabled=no interface=BRIDGE-LAN name=dhcp1
/interface bridge port
add bridge=BRIDGE-LAN interface=ether2
add bridge=BRIDGE-LAN interface=ether3
add bridge=BRIDGE-LAN interface=ether4
add bridge=BRIDGE-LAN interface=ether5
add bridge=BRIDGE-LAN interface=ether6
add bridge=BRIDGE-LAN interface=ether7
add bridge=BRIDGE-LAN interface=ether8
add bridge=BRIDGE-LAN interface=ether9
add bridge=BRIDGE-LAN interface=ether10
/interface ethernet switch rule
add new-vlan-priority=1 ports=switch1-cpu switch=switch1
/interface l2tp-server server
set authentication=mschap2 default-profile=default enabled=yes use-ipsec=
required
/ip address
add address=192.168.50.150/24 interface=BRIDGE-LAN network=192.168.50.0
/ip arp
add address=192.168.50.139 interface=BRIDGE-LAN mac-address=3C:D9:2B:57:72:46
/ip cloud
set ddns-enabled=yes
/ip dhcp-client
add disabled=no interface=WAN
/ip dhcp-server lease
add address=192.168.50.21 client-id=1:c0:74:ad:34:fe:ab comment=Admin2
mac-address=C0:74:AD:34:FE:AB server=dhcp1
add address=192.168.50.12 client-id=1:c0:74:ad:34:fe:3f comment=Admin1
mac-address=C0:74:AD:34:FE:3F server=dhcp1
/ip dhcp-server network
add address=192.168.50.0/24 dns-server=8.8.8.8,8.8.4.4 gateway=192.168.50.150
/ip firewall filter
add action=fasttrack-connection chain=forward connection-state=
established,related
add action=accept chain=forward connection-state=established,related
add action=accept chain=input comment="Permitir L2TP" protocol=udp src-port=
1701,500,4500
add action=accept chain=input protocol=ipsec-esp
add action=drop chain=forward connection-state=invalid
/ip firewall nat
add action=masquerade chain=srcnat out-interface=pppoe-out1
add action=masquerade chain=srcnat out-interface=BRIDGE-LAN
add action=dst-nat chain=dstnat comment="SERVIDOR WEB" dst-port=80 protocol=
tcp to-addresses=192.168.50.192 to-ports=80
add action=dst-nat chain=dstnat dst-port=22 protocol=tcp to-addresses=
192.168.50.192 to-ports=22
add action=dst-nat chain=dstnat comment=RTP dst-port=10000-12000 protocol=udp
to-addresses=192.168.50.55 to-ports=10000-12000
add action=dst-nat chain=dstnat dst-port=5070 protocol=tcp to-addresses=
192.168.50.55 to-ports=5070
add action=accept chain=srcnat comment="VPN L2TP" protocol=udp src-port=
1701,500,4500
/ip service
set telnet disabled=yes
set ftp disabled=yes
set www port=8888
set ssh disabled=yes
set api disabled=yes
set winbox port=9999
set api-ssl disabled=yes
/ppp secret
add local-address=192.168.50.150 name=XXXXXXXX
192.168.50.1 service=l2tp
/system clock
set time-zone-name=Europe/Madrid
/system identity
set name=RouterOS
Since you are using pppoe, and it sounds like this may be MTU / MSS related, you may want to use mss clamping.
I have seen several different methods suggested, but since I don’t use pppoe, I have used none.
Here is one I have seen suggested.
/ip firewall mangle
add action=change-mss chain=forward new-mss=clamp-to-pmtu passthrough=yes protocol=tcp tcp-flags=syn
Some threads to read:
PPPoE MTU problem
PPPoE MSS clamp no working on upgrade
When answering questions
Some additional info about mss
TCP MSS Clamping – What Is It and Why Do We Need It?
PMTU and MSS Discovery Issues Resolved with MikroTik
MikroTik Mangle Documentation
You should read this:
https://forum.mikrotik.com/viewtopic.php?t=180838
This DHCP pool is some messy with gaps inn it.
192.168.50.2-192.168.50.54
192.168.50.56-192.168.50.99
192.168.50.101-192.168.50.129
192.168.50.151-192.168.50.191
192.168.50.193-192.168.50.254
Use DHCP range 192.168.50.2-192.168.50.254
Then make a reservation for the mac of the devices you like fixed IP.
This could then be for IP 55 100 130-150 and 192
Or set dhcp range from 128-256 and use fixed IP below 128,.
Not sure what this does? add action=masquerade chain=srcnat out-interface=BRIDGE-LAN
Out nat should normally be only set on out (public) interface.