Integrating antiDPI measures into the kernel

There are projects like https://github.com/hufrea/byedpi and https://github.com/ValdikSS/GoodbyeDPI by they are a royal PITA to use because they require changing your browser settings and under Android it's not even possible because there's no "proxy" settings whatsoever, so you need something like https://github.com/dovecoteescapee/ByeDPIAndroid

Is it possible to integrate these workarounds as a Linux kernel module, so that you can enable antiDPI measures for all traffic instead and allow all the clients to just work, instead of dabbling with settings or installing extra applications?

Why is it important and urgent? Russia last week basically disabled YouTube and without VPN or solutions like these, YouTube basically doesn't work any more.

Russian problem. Those dirty hacks and tricks do not belong to the kernel.

I was waiting for this question to come when I saw the news…
Well technically as far as I understood the news, it wasn’t Russia that disabled Youtube. Russia is under global sanctions so it was the American Alphabet (Google Youtube) that disabled the Russian audience.

But usually under these political circumstances the SOP is to get a VPN service and mount that in the router and all network traffic appears in some country of your choice.
It may or may not work the problem with streaming services since it is very easy for streaming services to find and block commercial VPN servers.
Like this, “just follow the ants to the nest and then disable the nest”.

Likely you can benefit from whatever-ray packages in broad use in much longer DPI-ed places.

This is a blatant lie.

Google says it is not involved in the problems with the service in Russia

On August 1, Russian users of YouTube faced massive disruptions in the service's operation, in some cases - up to the point of stopping the video stream. Telecom operators had earlier warned about the wear and tear of Google's equipment. However, Google told Kommersant that the disruptions in Russia "are not the result of any technical problems" on their part. Alexander Khinshtein, the head of the Duma Committee on Information Policy, earlier said the possibility of YouTube slowing down in Russia was a deliberate action by the authorities against "the administration of a foreign resource" that violates Russian law. A technical analysis of the traffic problems may indicate the beginning of the implementation of this plan, experts suggest.

Users of the Google-owned video hosting site YouTube in Russia started to complain about service interruptions starting from midnight on August 1, according to data from the website "Failure Detector" (owned by Brand Analytics). By the evening of the same day, the service "Failure.rf" noted 9.5 thousand complaints about the work of hosting against several dozen per day during the week. The Kommersant correspondent, when using YouTube from a computer, noted that it does not load videos. The technical data of the video player shows that the channel speed of the connection to YouTube was 322 Kbps, while the buffer value (i.e. the length of the pre-loaded piece of video) remained zero. In July, according to measurements under the same conditions, the player buffered at least 50 seconds of 1080p video. At the same time, the channel speed was decreasing: on July 25 it was 8.5 Mbps, on July 30 - 918 Kbps.

Most of the mobile and fixed-line operators interviewed refused to comment (MTS, Tele2, Er-Telecom) or did not answer (Vimpelcom) Kommersant's questions about YouTube. Rostelecom and MegaFon did not respond directly to the question about the reasons for the problems with YouTube, but said that the operators' equipment was working without fail. On July 12, Rostelecom said that YouTube's performance in Russia could deteriorate due to wear and tear on Google's Global Cache (GGC) servers installed in Russia. "Questions about failures in the work of YouTube equipment should be addressed to Google," Rostelecom added on Thursday.

Google responded to Kommersant's question: "We are aware of reports that some people cannot access YouTube in Russia. This is not the result of any technical problems or actions on our part".The deputy noted that he was referring to "the actions of the authorities", but did not explicitly refer to anyone's decision. Mr. Khinshtein stressed that "the 'degradation' of YouTube is a forced step directed not against Russian users, but against the administration of a foreign resource, which still believes it can violate and ignore our legislation with impunity".

Problems with uploading videos on YouTube may be caused by traffic slowdown due to the operation of TSPU equipment (technical means of countering threats; installed on operators' networks under the law "on the sovereign runet"), according to Kommersant's source in the telecom market and a source responsible for the Internet company's network infrastructure.

The slowdown is based on the analysis of SNI (Server Name Indication) information transmitted to the server, explains one of Kommersant's interlocutors. In the process of establishing a secure connection to the server, browsers and applications use SNI to specify which specific Internet resource they want to access. "The speed of access to the YouTube server turns out to be the same as it was a month ago if you change the SNI field in the headers. This behavior cannot be explained by the 'inefficiency' of GGCs or their use or non-use at all," he said. YouTube slowdown does not appear at all Internet providers, "but whether the video slows down on the network of any particular operator does not depend on it," added a source in the telecom market. This, he said, is characteristic of all blocking carried out on the TSPU.

Experts believe that the decrease in the availability of YouTube will not create problems for the mass Russian audience. The majority of Russian-language content is uploaded to VK Video and Rutube, and audience overflow to these platforms is also possible, believes Artur Makhlayuk, business analyst at Fplus IT Holding. The Russian services declined to comment. But the transition of viewers to online cinemas is unlikely to be observed - "the content of platforms overlap minimally," says Alexey Byrdin, general director of the Internet Video Association. But video hosting serves as a valuable promotional platform for streaming services due to reviews and first episodes of series, which they post for promotion purposes, he continues, and "YouTube still gives incomparably larger coverage and number of views than Russian video hosting".

Source.

The fact is that if Google had done that, these anti-DPI tools wouldn't have worked, but they do.

I understand that the OpenWRT community believes that the Russians must suffer under their regime.

That's kind of horrifying to hear, but whatever.

1 Like

Could you please tone it down a bit and keep it civil and friendly, please. Just allow for the possibility that no one desired to deceive you, but that there might be different explanations floating around making it easy to come to not fully correct conclusions.

2 Likes

TL;DR, Google refuses to respect Russian laws, Russian government throttles down YouTube.

Has got nothing to do with OpenWrt. You're addressing this question in a wrong place. OpenWrt is already very limited in resources.

1 Like

I expect the technical community to be a little more knowledgeable and willing to do some research before parroting what they hear on the internet or expressing their opinions. I don't opine about the stuff I've no clue about. I don't comment to cast a shadow on other nations or groups of people. That's despicable.

Secondly, this is a technical discussion, not a thread dedicated to people expressing their attitudes towards a particular country.

Thirdly, DPI is not enabled just in Russia. It's enabled in multiple US states, Europe, Turkey, Egypt, China and multiple other countries. In fact there are fewer countries where there are no Internet restrictions, than countries that allow unfettered Internet access.

Are you not talking for everyone, OK?

There could be people who do not belong to this community who can contribute the required kernel patches.

I didn't expect this request to be so politically divisive and frowned upon.

I guess some people here actually dislike the entire nation. Oh boy.

The best place to address it is in Github of those projects you mentioned above.

1 Like

The people who created those projects are not kernel contributors and they don't have the in-depth knowledge of the kernel to write/submit these patches. They may never bother, because it's quite an endeavour.

One week of YouTube abstinense makes horrible things to good people :laughing:

3 Likes

I believe you think they are concentrated here?

1 Like

Extra exposure never hurts.

As to where they are concentrated, I've no clue.

LKML (Linux Kernel Mailing List) might be it but I cannot vouch for that.

Use VPN, Tor. Screwing up network stack for the sake of DPI penetration is never a good idea.

Literarily one of your proposed "measures" actually is not valid https://github.com/dovecoteescapee/ByeDPIAndroid/issues/33

Would be nice that you do profound research before posting new packages over via github.

1 Like

I've never claimed the Android app works for this particular use case. I listed it just as an example.

With so much backlash and open dislike of one particular country, even though DPI is implemented in the vast majority of countries in the world, let's just forget what I asked for.

Man, you're taking it too far. It's YouTube abstinence talking in you.

3 Likes

It's not Russophobia, your question is invalid and in the wrong place.

You're looking for a way to force all traffic through a proxy that does the DPI stuff, a daemon and some firewall rules should take care of that. ("Just" have to write your own daemon). Not sure that would ultimately work from client devices really with TLS and such, unless you want to MiTM your own devices and install custom certs on them.
Instead of relying on these hacky anti-DPI tricks, tunnel through a VPN.

No new kernel modules required.

1 Like