Mangle rule doesn't add to specific LIST IP addresses defined in CONTENT.


Sorry, but now (from 8 May...) Youtube use TLS 1.3..... and not only TCP....
All modern browsers and app use TLS 1.3, so you are unable to mark the traffic.
You just noticed it now, and of course you have to blame RouterOS...
Just if you still use some old browser that doesn't support TLS 1.3, but at most 1.2, it can make you match that rule.
The other domain doesn't know what it is, so I haven't checked it, if it still uses http you can still catch it,
but when that too switches to https, your rules won't be of any use.
Indeed, just checked up - tls search for *youtube* works unstable now.The user already have one reply...
viewtopic.php?p=1004654#p1004689Sorry, but now (from 8 May...) Youtube use TLS 1.3..... and not only TCP....
Will you please make an advise, how can I find updated lists?When the lists are updated...
Precisely...Will you please make an advise, how can I find updated lists?When the lists are updated...
Thank you in advance.
My only goal of using lists: to access local addresses directly + to access foreign addresses thru vpn.
The "drop all at the end what is not already allowed" rule makes the list completely useless