Windows 10 hotspot clients consuming all the bandwidth

Hi guys.
i’m a newbie on this forum. i have a TIK CCR which is working fine.
the problem is some of the users on my network us their windows 10 OS to share a WiFi Hotspot from Ethernet LAN. this gives users access to my TIK network. i cannot locate the devices on the shared Hotspot in TIK DHCP server lease and a lot of bandwidth is going to the IP of the Computer that is sharing the network. i have Layer7 protocols configured to block Youtube but for some reason, mobile devices on the shared Hotspot goes straight through the firewall protocol and everyone on the shared WiFi Hotspot is streaming movies with precious bandwidth.

please how do i stop solve these problems

  1. i don’t want windows 10 to share my network via WiFi
  2. mobile Youtube client consuming bandwidth ignoring layer7 firewall rule

#thank you for any suggestions

First thing is to limit the per-user bandwidth in your hot spot. So when they share, they have nothing themselves remaining… :slight_smile:

Second thing is more an idea, I don’t know if this can work nor if ROS has the feature set to do it…
In Mikrotik wiki LTE page there is mentioning that TTL value gets reduced per hop.
This example given is the opposite, how to enable wifi sharing. Maybe you can also figure a way out to block this.
maybe one can drop packets if TTL is below a certain number…?

Avoiding tethering speed throttling
Some operators (TMobile, YOTA etc.) allows unlimited data only for device SIM card is used on, all other data coming from mobile hotspots or tethering is highly limited by volume or by throughput speed. Some sources have found out that this limitation is done by monitoring TTL (Time To Live) values from packets to determinate if limitations need to be applied (TTL is decreased by 1 for each “hop” made). RouterOS allows changing the TTL parameter for packets going from the router to allow hiding sub networks. Keep in mind that this may conflict with fair use policy.

/ip firewall mangle
add action=change-ttl chain=postrouting new-ttl=set:65 out-interface=lte1 passthrough=yes