From 16a422935d3c85136486e1897c0c85d0cc9060e3 Mon Sep 17 00:00:00 2001 From: puglieri <112409628+puglieri@users.noreply.github.com> Date: Wed, 4 Mar 2026 17:07:55 +0000 Subject: [PATCH] automatically update translations --- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 72 ++++++- .../protection/tracking-protection.md | 20 +- .../app-settings/advanced-settings.md | 22 +- .../adguard-for-windows/features/network.md | 36 +++- .../adguard-for-windows/installation.md | 2 +- .../adguard-mini-for-mac.md | 18 +- .../adguard-mini-for-mac/extensions.md | 38 ++-- .../adguard-mini-for-mac/installation.md | 38 ++-- .../solving-problems/rule-limit.md | 12 +- .../solving-problems/solving-problems.md | 12 +- .../ad-filtering/create-own-filters.md | 18 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 192 +++++++++++------- .../adguard-for-windows/features/network.md | 36 +++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 124 +++++++---- .../adguard-for-windows/features/network.md | 36 +++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 124 +++++++---- .../adguard-for-windows/features/network.md | 36 +++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 124 +++++++---- .../adguard-for-windows/features/network.md | 36 +++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 90 ++++++-- .../adguard-for-windows/features/network.md | 36 +++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../solving-problems/firefox-certificates.md | 2 +- .../current/adguard-for-linux/settings.md | 124 +++++++---- .../adguard-for-windows/features/network.md | 36 +++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 124 +++++++---- .../adguard-for-windows/features/network.md | 36 +++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 34 +++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 164 ++++++++++----- .../adguard-for-windows/features/network.md | 36 +++- .../ad-filtering/create-own-filters.md | 8 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 108 +++++++--- .../adguard-for-windows/features/network.md | 32 ++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 124 +++++++---- .../adguard-for-windows/features/network.md | 36 +++- .../ad-filtering/create-own-filters.md | 6 +- .../ads-not-blocked-in-opera.md | 15 ++ .../current/adguard-for-linux/settings.md | 68 ++++++- .../adguard-for-windows/features/network.md | 20 +- .../ad-filtering/create-own-filters.md | 6 +- 129 files changed, 3463 insertions(+), 793 deletions(-) create mode 100644 i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md create mode 100644 i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..e45d115eddd --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Problémy s blokováním reklam na vyhledávacích webech v prohlížeči Opera +sidebar_position: 3 +--- + +Pokud rozšíření prohlížeče AdGuard neblokuje reklamy na vyhledávacích webwch v Opeře, ať už automaticky nebo ručně, znamená to, že rozšíření nemá oprávnění k přístupu k výsledkům vyhledávání. + +Chcete-li udělit požadované oprávnění: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Klikněte na ikonu krychle vedle adresního řádku → _Spravovat rozšíření..._. +2. Vyhledejte blokátor reklam AdGuard v seznamu nainstalovaných rozšíření a zaškrtněte políčko vedle _Povolit přístup k výsledkům vyhledávání na stránce_. + +Jakmile to provedete, reklamy na vyhledávacích webech budou blokovány podle očekávání. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index 3508a4e2c9f..1ad88b59196 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ Chcete-li povolit zakázat, zadejte: adguard-cli stop ``` -Tento příkaz nejen zastaví proxy, ale také zastaví přesměrování na něj. +Tento příkaz nejen zastaví proxy, ale také zastaví přesměrování provozu na něj. ### Zkontrolovat stav ochrany @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Aktualizace ### Zkontrolovat aktualizace @@ -65,7 +73,7 @@ adguard-cli update ### Aktualizace výstupu skriptu -Chcete-li zobrazit výstup skriptu aktualizace, zadejte: +Chcete-li aktualizovat výstup skriptu aktualizace, zadejte: ```sh adguard-cli update -v @@ -75,15 +83,23 @@ adguard-cli update -v Pro konfiguraci AdGuardu pro Linux použijte příkaz `config`. Dílčí příkazy: -- `show`: Zobrazení aktuální konfigurace v souboru `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Konfigurace volby v souboru `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: Naslouchací port HTTP - `proxy_mode`: Režim proxy (`manuální` nebo `automatický`) -- `get`: Zjištění aktuálního stavu výše uvedených možností +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,21 +116,59 @@ Automatický režim lze použít pouze tehdy, že jsou splněny následující p Pro konfiguraci AdGuardu pro Linux použijte příkaz `filters`. Dílčí příkazy: -- `list`: Seznam nainstalovaných filtrů +- `list`: List installed and added filters - `--all`: Zobrazení všech filtrů ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Instalace filtru. Zadejte adresu URL filtru, který chcete nainstalovat +- `add`: Add a built-in filter by ID or name + +- `install`: Instalace filtru. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Povolení filtru. Zadejte název nebo ID filtru ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) -- `disable`: Zakázání filtrování. Zadejte název nebo ID filtru +- `disable`: Zakázání filtru. Zadejte název nebo ID filtru + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Dílčí příkazy: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Zadejte název nebo ID filtru +- `disable`: Disable a DNS filter. Zadejte název nebo ID filtru +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Dílčí příkazy: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update`: Aktualizace filtrů +Userscripts are updated by `adguard-cli check-update`. ## Změna poslechové adresy proxy v režimu ručního proxy diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/protection/tracking-protection.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/protection/tracking-protection.md index b60531bdde8..fe576a1fc75 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/protection/tracking-protection.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/protection/tracking-protection.md @@ -153,32 +153,32 @@ Totéž platí pro možnost _Skrýt referenční ID před třetími stranami_: A ### Skrýt User-Agent -When you visit a website, your browser sends a header called User-Agent as part of the HTTP request. It looks like a text line that begins with “User-Agent:”. This line usually contains details such as the browser name and version, operating system, and language settings. +Když navštívíte webovou stránku, váš prohlížeč odešle jako součást HTTP požadavku hlavičku nazvanou User-Agent. Vypadá to jako textový řádek, který začíná “User-Agent:”. Tento řádek obvykle obsahuje podrobnosti, jako je název a verze prohlížeče, operační systém a nastavení jazyka. -By enabling this option, AdGuard removes identifying information from the User-Agent so advertisers and trackers cannot use it to profile you. If you prefer, you can enter a custom value in the _Custom User-Agent_ field. To keep the default value, simply leave the field blank. +Povolením této možnosti AdGuard odstraní identifikační informace z User-Agent, aby je inzerenti a slídiče nemohli použít k vytvoření vašeho profilu. Pokud chcete, můžete zadat vlastní hodnotu do pole _Vlastní User-Agent_. Chcete-li zachovat výchozí hodnotu, jednoduše ponechte pole prázdné. -### Mask your IP address +### Maskovat adresu IP -AdGuard cannot completely hide your real IP address, but it can replace it with a different one so that websites interpret your connection as coming through a proxy. In some cases this helps to obscure your true IP. +AdGuard nemůže zcela skrýt vaši skutečnou IP adresu, ale může ji nahradit jinou, aby webové stránky interpretovaly vaše připojení jako připojení přes proxy server. V některých případech to pomáhá skrýt vaši skutečnou IP adresu. -You can enter any IP address you want to use in the corresponding field. Chcete-li použít výchozí IP adresu, ponechte pole prázdné. +Do příslušného pole můžete zadat libovolnou IP adresu, kterou chcete použít. Chcete-li použít výchozí IP adresu, ponechte pole prázdné. ### Odstranit X-Client-Data hlavičku -Prevents Google Chrome from sending information about its version and modifications in requests to Google domains, including services like DoubleClick and Google Analytics. +Zabraňuje prohlížeči Google Chrome odesílat informace o své verzi a úpravách v požadavcích na domény Google, včetně služeb jako DoubleClick a Google Analytics. ### Ochrana proti DPI Deep Packet Inspection je systém hloubkové analýzy a filtrování provozu podle obsahu paketů a shromažďování statistických údajů. Pomocí této technologie mají poskytovatelé internetových služeb možnost kontrolovat procházející provoz a omezovat přístup k obsahu pro své klienty. -Deep Packet Inspection (DPI) is a technology used by some ISPs to analyze and filter traffic based on packet content. It allows them to monitor connections, restrict access to certain resources, and collect statistics about users. +Deep Packet Inspection (DPI) je technologie používaná některými poskytovateli internetových služeb k analýze a filtrování provozu na základě obsahu paketů. Umožňuje jim monitorovat připojení, omezovat přístup k určitým zdrojům a shromažďovat statistické údaje o uživatelích. -When this option is enabled, AdGuard modifies outgoing packet data so that it no longer matches the DPI blocking criteria. This can help you bypass restrictions and access the content you need. However, not all DPI systems can be circumvented yet — improvements are still in progress. +Když je tato možnost zapnutá, AdGuard upraví odchozí data paketů tak, aby už nesplňovala kritéria blokování DPI. To vám pomůže obejít omezení a získat přístup k obsahu, který potřebujete. Ne všechny systémy DPI však lze zatím obejít — stále probíhají vylepšení. -The _Protect from DPI_ feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Funkce _Ochrana před DPI_ je již implementována v AdGuardu pro Windows, AdGuardu pro Mac a AdGuardu pro Android. :::caution -If this feature is enabled in AdGuard for Windows, it may interfere with the ESET antivirus. In this case, ESET will not be able to filter traffic, leaving some malicious or blocked websites accessible. +Pokud je tato funkce v AdGuardu pro Windows povolena, může docházet k interferenci s antivirem ESET. V takovém případě nebude ESET schopen filtrovat provoz, takže některé škodlivé nebo blokované webové stránky zůstanou přístupné. ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/advanced-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/advanced-settings.md index 0970cbb4ad4..f15c53835a0 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/advanced-settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/settings/app-settings/advanced-settings.md @@ -9,41 +9,41 @@ Tento článek popisuje AdGuard pro Windows v8.0, multifunkční blokátor rekla ::: -The _Advanced settings_ section contains options that go beyond what most users usually need. AdGuard for Windows works perfectly out of the box, but these settings can be useful in special cases or for troubleshooting. +Sekce _Pokročilá nastavení_ obsahuje možnosti, které přesahují to, co většina uživatelů obvykle potřebuje. AdGuard pro Windows funguje ihned po instalaci, ale tato nastavení mohou být užitečná ve zvláštních případech nebo při řešení problémů. :::caution -Changing advanced settings without understanding them may cause performance issues, break your Internet connection, or affect your security and privacy. Only modify them if you know what you’re doing or if instructed by our support team. +Změna pokročilých nastavení bez jejich pochopení může způsobit problémy s výkonem, přerušit připojení k internetu nebo ovlivnit vaše zabezpečení a soukromí. Upravujte je pouze v případě, že víte, co děláte, nebo pokud vás k tomu vyzve náš tým podpory. ::: ## Vyloučit aplikaci z filtrování zadáním úplné cesty -If you want AdGuard to skip filtering a specific app, enter its full file path here. You can add multiple apps by separating their paths with semicolons. +Pokud chcete, aby AdGuard přeskočil filtrování konkrétní aplikace, zadejte zde její úplnou cestu k souboru. Můžete přidat více aplikací oddělením jejich cest středníky. ## Povolit vyskakovací oznámení AdGuardu -Povolením této funkce zobrazíte vyskakovací oznámení AdGuardu. Nezobrazují se příliš často a obsahují pouze důležité informace. You can also reopen the latest notification from the tray menu. +Povolením této funkce zobrazíte vyskakovací oznámení AdGuardu. Nezobrazují se příliš často a obsahují pouze důležité informace. Nejnovější oznámení můžete také znovu otevřít z nabídky v liště. ## Automaticky zachytávat URL adresy pro odběr filtrů -When enabled, AdGuard will automatically detect filter subscription links (like `abp:subscribe`) and open a window to help you add them to your filters. +Pokud je tato funkce zapnutá, AdGuard automaticky detekuje odkazy na odběry filtrů (např. `abp:subscribe`) a otevře okno, které vám pomůže přidat je do vašich filtrů. ## Použít režim přesměrování ovladače -With this option enabled, AdGuard reroutes all your traffic to a local proxy server for filtering. +Při zapnutí této možnosti AdGuard přesměruje veškerý váš provoz na místní proxy server za účelem filtrování. -If it’s turned off, AdGuard filters traffic directly — without redirecting it. In this mode, Windows sees AdGuard as the only app connecting to the Internet, since all other apps go through it. This can slightly improve performance but may reduce the effectiveness of the system firewall. +Pokud je vypnuto, AdGuard filtruje provoz přímo — bez přesměrování. V tomto režimu Windows vnímá AdGuard jako jedinou aplikaci připojenou k internetu, protože všechny ostatní aplikace procházejí přes něj. To může mírně zlepšit výkon, ale může snížit účinnost systémového firewallu. -## Open AdGuard at system start-up +## Otevřít AdGuard při startu systému -Enable this option to launch the AdGuard window automatically when your PC starts. +Povolením této možnosti se okno AdGuardu spustí automaticky při zapnutí počítače. ## Zapnout filtrování při spuštění systému -Since version 7.12, AdGuard doesn’t start filtering traffic automatically after you boot your PC — unless the _Launch AdGuard at system start-up_ option is enabled. Instead, it runs in a passive “idle” mode. +Od verze 7.12 AdGuard nezačne automaticky filtrovat provoz po zapnutí počítače, pokud není povolena možnost _Spustit AdGuard při spuštění systému_. Místo toho běží v pasivním “nečinném“ režimu. -Turning this on allows AdGuard to filter traffic immediately, even if the app hasn’t been opened yet. +Zapnutí této možnosti umožní AdGuardu okamžitě filtrovat provoz, dokonce i když aplikace ještě nebyla otevřena. ## Filtrovat localhost diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 208919b7831..fc3f3468436 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ Tento článek popisuje AdGuard pro Windows, multifunkční blokátor reklam, kt Modul _Síť_ je věnován filtrování sítě a najdete v něm další možnosti související se sítí. Dvě z nich jsou standardně povoleny: _Povolit filtrování provozu_ a _Filtrovat HTTPS_. Jedná se o důležitá dodatečná opatření pro lepší filtrování webového prostoru. Většina webů nyní používá protokol HTTPS a totéž platí i pro reklamu. Z mnoha webů, jako je youtube.com, facebook.com a x.com, není možné odstranit reklamy bez HTTPS filtrování. Pokud tedy nemáte pádný důvod, ponechte funkci _Filtrovat HTTPS_ povolenou. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) V tomto modulu můžete vybrat _Použít AdGuard jako HTTP proxy_, chcete-li použít AdGuard jako běžný HTTP proxy, který bude filtrovat veškerý procházející provoz. Můžete také povolit funkci _Filtrovat webové stránky s certifikáty EV_. Certifikáty SSL s rozšířeným ověřením (Extended Validation, EV) poskytují silnější bezpečnostní záruku; majitelé těchto webových stránek musí projít důkladným a celosvětově standardizovaným procesem ověřování identity definovaným v pokynech pro EV. To je důvod, proč někteří uživatelé webovým stránkám s takovými certifikáty důvěřují a raději je nefiltrují. Nakonec je zde část s nastavením proxy. Zde můžete určit, který proxy má AdGuard používat k aktualizaci filtrů, získávání nových verzí atd. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -Poslední část je věnována AdGuard VPN — ideálnímu nástroji, který poskytuje bezpečnost a anonymitu při každém procházení internetu. Můžete si ji stáhnout kliknutím na tlačítko _Stáhnout_ nebo přejít na webové stránky AdGuard VPN kliknutím na tlačítko _Domovská stránka_. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -Jak funguje AdGuard VPN? Aniž bychom zacházeli do technických podrobností, můžeme říci, že VPN vytváří bezpečný šifrovaný tunel mezi počítačem nebo mobilním zařízením uživatele a vzdáleným serverem VPN. Tímto způsobem je zachována důvěrnost dat i anonymita uživatele, protože pozorovatel třetí strany vidí IP adresu serveru VPN, a nikoli skutečnou IP adresu uživatele. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**Co dělá AdGuard VPN:** +**What AdGuard VPN does:** -- skrývá vaše skutečné místo pobytu a pomáhá vám zůstat v anonymitě -- změní vaši IP adresu a ochrání vaše data před sledováním -- šifruje váš provoz, aby byl nečitelný pro třetí strany -- umožňuje nastavit, kde se má VPN používat a kde ne (funkce výjimek) +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -Chcete-li získat více informací o AdGuard VPN, ponořte se do [Databáze znalostí AdGuard VPN](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index 9a2e53c44f9..83ef63e0ecc 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -71,7 +71,7 @@ Pokud potřebujete AdGuard odinstalovat nebo přeinstalovat, postupujte následo ### Pokročilý způsob {#advanced} -Pokud běžná odinstalace z nějakého důvodu nefunguje, můžete zkusit pokročilou metodu. First of all, you need to [download the uninstaller tool](https://static.adtidy.org/windows/uninstaller/uninstall_utility.zip) created by our developers. Rozbalte archiv do libovolné složky v počítači, spusťte soubor **Adguard.UninstallUtility.exe** a nechte aplikaci provést změny v zařízení. Poté postupujte podle níže uvedených pokynů: +Pokud běžná odinstalace z nějakého důvodu nefunguje, můžete zkusit pokročilou metodu. Nejprve si musíte stáhnout [nástroj pro odinstalaci](https://static.adtidy.org/windows/uninstaller/uninstall_utility.zip) vytvořený našimi vývojáři. Rozbalte archiv do libovolné složky v počítači, spusťte soubor **Adguard.UninstallUtility.exe** a nechte aplikaci provést změny v zařízení. Poté postupujte podle níže uvedených pokynů: - Vyberte *Blokátor reklam AdGuard* a *Standardní* typ odinstalace a poté klikněte na *Odinstalovat*. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/adguard-mini-for-mac.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/adguard-mini-for-mac.md index c476cd43916..fa5b45e9783 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/adguard-mini-for-mac.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/adguard-mini-for-mac.md @@ -5,24 +5,24 @@ sidebar_position: 1 :::info -This page is about AdGuard Mini for Mac, which safeguards only your Safari browser. Chcete-li zcela ochránit svůj Mac, [stáhněte si aplikaci AdGuard](https://agrd.io/download-kb-adblock) +Tato stránka je o AdGuardu Mini pro Mac, který chrání pouze váš prohlížeč Safari. Chcete-li zcela ochránit svůj Mac, [stáhněte si aplikaci AdGuard](https://agrd.io/download-kb-adblock) ::: -AdGuard Mini for Mac (formerly AdGuard for Safari) was designed to conform to Apple’s restrictions for ad blocking browser extensions. Although it can’t be compared to our desktop ad blocking apps, it’s free and can protect you from ads, trackers, phishing, and malicious websites. +AdGuard Mini pro Mac (dříve AdGuard pro Safari) byl navržen tak, aby odpovídal omezením Apple pro rozšíření prohlížeče pro blokování reklama. Přestože se nedá srovnávat s našimi aplikacemi pro blokování reklam na počítači, je zdarma a dokáže vás ochránit před reklamami, slídiči, phishingem a škodlivými webovými stránkami. -- [Features](/adguard-mini-for-mac/features/features.md) +- [Funkce](/adguard-mini-for-mac/features/features.md) - Main features and settings available in AdGuard Mini for Mac + Hlavní funkce a nastavení dostupné v aplikaci AdGuard Mini pro Mac -- [Installation](/adguard-mini-for-mac/installation.md) +- [Instalace](/adguard-mini-for-mac/installation.md) - Installation, removal, and system requirements for AdGuard Mini for Mac + Instalace, odstranění a systémové požadavky AdGuardu Mini pro Mac -- [Safari extensions](/adguard-mini-for-mac/extensions.md) +- [Rozšíření Safari](/adguard-mini-for-mac/extensions.md) - Mechanisms that enable content blocking and add functionality to the Safari web browser + Mechanismy, které umožňují blokování obsahu a přidávají funkce do webového prohlížeče Safari -- [Solving problems](/adguard-mini-for-mac/solving-problems/solving-problems.md) +- [Řešení problémů](/adguard-mini-for-mac/solving-problems/solving-problems.md) Známé problémy a možná řešení diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/extensions.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/extensions.md index a523a4e50f4..79955a8211e 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/extensions.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/extensions.md @@ -11,11 +11,11 @@ Tento článek je o AdGuardu Mini pro Mac, který chrání pouze váš prohlíž ## Co jsou rozšíření Safari -Rozšíření Safari jsou malé programy, které přidávají funkce do webového prohlížeče Safari. Umožňují uživatelům přizpůsobit a vylepšit prohlížení stránek přidáním funkcí, které nejsou nativně zabudovány v prohlížeči. AdGuard Mini for Mac uses extensions primarily to apply filtering rules on websites opened in Safari. +Rozšíření Safari jsou malé programy, které přidávají funkce do webového prohlížeče Safari. Umožňují uživatelům přizpůsobit a vylepšit prohlížení stránek přidáním funkcí, které nejsou nativně zabudovány v prohlížeči. AdGuard Mini pro Mac používá rozšíření především k použití pravidel filtrování na webových stránkách otevřených v Safari. ## Jak to funguje -K blokování reklam, slídičů a obtěžujících prvků na webových stránkách používá AdGuard pravidla filtrování. The rules from AdGuard’s and your custom filters are converted into ones comprehensible by Safari and are integrated into 6 Safari extensions: +K blokování reklam, slídičů a obtěžujících prvků na webových stránkách používá AdGuard pravidla filtrování. Pravidla z filtrů AdGuardu a vašich vlastních filtrů jsou převedena na pravidla srozumitelná pro Safari a jsou integrována do 6 rozšíření Safari: - AdGuard – General - AdGuard – Privacy @@ -24,9 +24,9 @@ K blokování reklam, slídičů a obtěžujících prvků na webových stránk - AdGuard – Custom - AdGuard – Other -Každé rozšíření pro blokování obsahu může obsahovat až 150 000 aktivních pravidel filtrování. Počet pravidel ve většině skupin filtrů nepřesahuje 150 000. Pokud však aktivujete příliš mnoho jazykově specifických nebo vlastních filtrů, můžete tento limit překročit. V takových případech budou náhodná pravidla, která překročí limit, automaticky zakázána, což může vést k nesprávnému blokování. **We strongly recommend activating only the filters you need**. +Každé rozšíření pro blokování obsahu může obsahovat až 150 000 aktivních pravidel filtrování. Počet pravidel ve většině skupin filtrů nepřesahuje 150 000. Pokud však aktivujete příliš mnoho jazykově specifických nebo vlastních filtrů, můžete tento limit překročit. V takových případech budou náhodná pravidla, která překročí limit, automaticky zakázána, což může vést k nesprávnému blokování. **Důrazně doporučujeme aktivovat pouze ty filtry, které potřebujete**. -There is also one more extension responsible for other features: _AdGuard for Safari_, which adds the AdGuard icon next to the search bar in Safari and allows using advanced rules to block complex ads. +K dispozici je také další rozšíření, které je zodpovědné za další funkce: _AdGuard pro Safari_, které přidává ikonu AdGuard vedle vyhledávací lišty a umožňuje používání pokročilejších pravidel k blokování záludnějších reklam. ![Safari extensions](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/check-extensions.png) @@ -34,43 +34,43 @@ Více informací o jednotlivých rozšířeních najdete níže. ## Rozšíření blokování obsahu -_AdGuard General_ applies rules from filters that you can find in _Settings_ → _Filters_ → _Ad blocking_ and _Language-specific_. Toto rozšíření se zaměřuje na komplexní blokování reklam a obsahuje filtry pro reklamy v konkrétních jazycích. +_AdGuard General_ použije pravidla z filtrů, které najdete v _Nastavení_ → _Filtry_ → _Blokování reklam_ a _Jazykově specifické_. Toto rozšíření se zaměřuje na komplexní blokování reklam a obsahuje filtry pro reklamy v konkrétních jazycích. -_AdGuard Privacy_ applies rules from filters located in _Filters_ → _Privacy_. Blokuje sledovací mechanismy a zajišťuje, že vaše aktivita při prohlížení zůstane v soukromí. +_AdGuard Privacy_ použije pravidla z filtrů umístěných v sekci _Filtry_ → _Soukromí_. Blokuje sledovací mechanismy a zajišťuje, že vaše aktivita při prohlížení zůstane v soukromí. -_AdGuard Social_ applies rules from filters that can be found in _Filters_ → _Social Widgets_ and _Filters_ → _Annoyances_. It blocks popups, social media buttons, online assistant windows, and other elements on webpages that you might find annoying. +_AdGuard Social_ použije pravidla z filtrů, které lze nalézt v sekci _Filtry_ → _Sociální widgety_ a _Filtry_ → _Obtěžování_. Blokuje vyskakovací okna, tlačítka sociálních médií, okna online asistentů a další prvky na webech, které by vám mohly vadit. -_AdGuard Security_ applies rules from filters under _Filters_ → _Security_. Toto rozšíření identifikuje a blokuje potenciálně škodlivé prvky a chrání uživatele před škodlivým obsahem. +_AdGuard Security_ použije pravidla z filtrů v sekci _Filtry_ → _Zabezpečení_. Toto rozšíření identifikuje a blokuje potenciálně škodlivé prvky a chrání uživatele před škodlivým obsahem. -_AdGuard Other_ applies rules from filters that don’t fall under the above-mentioned categories and that are located in _Filters_ → _Other_: _Filter unblocking search ads and self-promotion_, _AdGuard DNS filter_, and _AdGuard Experimental filter_. +_AdGuard Other_ použije pravidla z filtrů, které nespadají do výše uvedených kategorií a které se nacházejí v sekci _Filtry_ → _Ostatní_: _Filtr odblokování reklam ve vyhledávání a vlastní propagace_, _Filtr AdGuard DNS_ a _Experimentální filtr AdGuardu_. -_AdGuard Custom_ applies rules from filters that you add on your own to _Custom filters_. +_AdGuard Custom_ použije pravidla z filtrů, které si sami přidáte do sekce _Vlastní filtry_. -User rules and allowlist rules are included in every extension. +Uživatelská pravidla a pravidla seznamu povolených jsou součástí každého rozšíření. ## AdGuard pro Safari -_AdGuard for Safari_ activates the AdGuard icon next to the search bar. It’s useful if you want to quickly set up protection for a specific website or block ads manually. +_AdGuard pro Safari_ aktivuje ikonu AdGuardu vedle vyhledávací lišty. Je to užitečné, pokud chcete rychle nastavit ochranu na konkrétním webu nebo ručně blokovat reklamy. -_AdGuard for Safari_ extension also contains advanced rules that aren’t converted to the format supported by Safari. These include [CSS rules](/general/ad-filtering/create-own-filters#cosmetic-css-rules), [extended CSS selectors](/general/ad-filtering/create-own-filters#extended-css-selectors), and [scriptlets](/general/ad-filtering/create-own-filters#scriptlets), which allow AdGuard to block complex ads, such as those on YouTube. +Rozšíření _AdGuard pro Safari_ také obsahuje pokročilá pravidla, která nejsou převedena do formátu podporovaného prohlížečem Safari. Mezi ně patří [pravidla CSS](//general/ad-filtering/create-own-filters#cosmetic-css-rules), [rozšířené selektory CSS](/general/ad-filtering/create-own-filters#extended-css-selectors) a [skripty](//general/ad-filtering/create-own-filters#scriptlets), které umožňují AdGuardu blokovat složité reklamy, například na YouTube. ## Jak spravovat rozšíření Safari -1. Open Safari and click _Safari_ in the upper left corner of the screen to expand the menu. +1. Otevřete Safari a kliknutím na _Safari_ v levém horním rohu obrazovky rozbalte nabídku. ![Safari settings \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/safari/adguard-for-safari-settings1.png) -2. Click _Settings..._ +2. Klikněte na _Nastavení..._ -3. Select _Extensions_. +3. Vyberte _Rozšíření_. ![Extensions tab](https://cdn.adtidy.org/content/kb/ad_blocker/safari/adguard-for-safari-extensions1.png) ## Proč vyžaduje AdGuard pro Safari oprávnění -When enabling the _AdGuard for Safari_ extension, you might notice that it requires **access to webpage content** and **access to browsing history**. Here’s why it needs these permissions: +Při povolování rozšíření _AdGuard pro Safari_ si můžete všimnout, že vyžaduje **přístup k obsahu webových stránek** a **přístup k historii prohlížení**. Zde je důvod, proč potřebuje tato oprávnění: -- Access to webpage content is required for manual ad blocking and advanced blocking rules to work correctly +- Pro správnou funkci ručního blokování reklam a pokročilých pravidel blokování je nutný přístup k obsahu webové stránky - Přístup k historii prohlížení je nutný pro kontrolu stavu ochrany na webových stránkách a určení, která pokročilá pravidla by měla být použita -Tyto údaje nepoužíváme pro žádné jiné účely a ani je s nikým nesdílíme. For more info, you can consult our [Privacy policy](https://adguard.com/privacy.html). +Tyto údaje nepoužíváme pro žádné jiné účely a ani je s nikým nesdílíme. Další informace najdete v našich [Zásadách ochrany osobních údajů](https://adguard.com/privacy.html). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/installation.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/installation.md index c6970119bd0..1386501aed6 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/installation.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/installation.md @@ -11,66 +11,66 @@ Tento článek je o AdGuardu Mini pro Mac, který chrání pouze váš prohlíž ## Požadavky na systém -Requires macOS 12 or later. +Vyžaduje macOS 12 nebo novější. -## How to install AdGuard Mini for Mac +## Jak nainstalovat AdGuard Mini pro Mac -AdGuard Mini for Mac is a free app present in the Mac App Store. To install it on your Mac, do the following: +AdGuard Mini pro Mac je aplikace zdarma dostupná v App Store pro Mac. Chcete-li ji nainstalovat do Macu, postupujte takto: -1. Open the App Store and find _AdGuard Mini_ app there. +1. Otevřete App Store a vyhledejte tam aplikaci _AdGuard Mini_. ![AdGuard Mini in App Store](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/mini-in-app-store.png) -2. Press _Get_ → _Install_ → _Open_. +2. Stiskněte _Získat_ → _Instalovat_ → _Otevřít_. -3. In the opened AdGuard Mini window, accept EULA and Privacy policy. Here you can also choose to help us improve the extension by sending anonymized usage data. Then click _Continue_. +3. V otevřeném okně AdGuard Mini přijměte smlouvu EULA a zásady ochrany osobních údajů. Zde se také můžete rozhodnout, zda nám pomůžete vylepšit rozšíření zasláním anonymizovaných údajů o používání. Poté klikněte na _Pokračovat_. ![Onboarding](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/first-open.png) Zakazuje prohlížeči Google Chrome odesílat informace o verzi a modifikaci s požadavky na domény Google (včetně DoubleClick a Google Analytics). - If you choose to share app usage data with AdGuard, the extension will collect anonymized information such as UI interactions and session identifiers. This consent is optional and can be withdrawn at any time. All collected data is fully anonymized, used only internally, and never shared with third parties. + Pokud se rozhodnete sdílet údaje o používání aplikace s AdGuardem, rozšíření bude shromažďovat anonymizované informace, jako jsou interakce s uživatelským rozhraním a identifikátory relací. Tento souhlas je dobrovolný a lze jej kdykoli odvolat. Všechny shromážděné údaje jsou zcela anonymizovány, používány pouze interně a nikdy nejsou sdíleny s třetími stranami. ::: -4. Click _Open settings_. +4. Klikněte na _Otevřít nastavení_. ![Open settings](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/open-settings.png) -5. Check the checkboxes for all seven AdGuard extensions. +5. Zaškrtněte políčka u všech sedmi rozšíření AdGuardu. ![Checked extensions](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/check-extensions.png) -6. To allow AdGuard Mini to work on all websites, click the _AdGuard for Safari_ extension and then _Always Allow on Every Website..._. +6. Chcete-li povolit aplikaci AdGuard Mini na všech webových stránkách, klikněte na rozšíření _AdGuard pro Safari_ a poté na _Vždy povolit na všech webových stránkách..._. ![Always allow button](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/always-allow-button.png) -7. In the notification that appears, click _Always Allow on Every Website..._ again. +7. V zobrazeném oznámení klikněte znovu na _Vždy povolit na všech webových stránkách..._. ![Always allow notification](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/always-allow.png) -After you complete these steps, AdGuard Mini for Mac will start functioning in Safari. +Po dokončení těchto kroků začne AdGuard Mini pro Mac fungovat v prohlížeči Safari. -## How to uninstall AdGuard Mini for Mac +## Jak odinstalovat AdGuard Mini pro Mac -To uninstall AdGuard Mini for Mac, do the following: +Chcete-li odinstalovat AdGuard Mini pro Mac postupujte takto: 1. Ukončete aplikaci. 2. Klikněte na _Safari_ v nabídce v levém horním rohu. -3. Klikněte na _Nastavení…_ → _Rozšíření_. You will see a list of extensions, AdGuard Mini has seven. +3. Klikněte na _Nastavení…_ → _Rozšíření_. Zobrazí se seznam rozšíření, AdGuard Mini jich má sedm. -4. Uncheck all checkboxes and press _Uninstall_ below any of them. +4. Zrušte zaškrtnutí všech políček a stiskněte _Odinstalovat_ pod kterýmkoli z nich. ![Unchecked extensions](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/unchecked-extensions.png) -5. In the notification that appears, press _Show in Finder_. +5. V zobrazeném oznámení stiskněte _Zobrazit ve Finderu_. ![Uninstall notification](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/show-in-finder.png) -6. Right-click _AdGuard Mini_ and choose _Move to trash_. +6. Klikněte pravým tlačítkem na _AdGuard Mini_ a vyberte možnost _Přesunout do koše_. ![Move to trash](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/move-to-trash.png) - AdGuard Mini for Mac will be removed from your device. + AdGuard Mini pro Mac bude z vašeho zařízení odebrán. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/solving-problems/rule-limit.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/solving-problems/rule-limit.md index a26b34708ec..bfec68d22c0 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/solving-problems/rule-limit.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/solving-problems/rule-limit.md @@ -11,9 +11,9 @@ Tento článek je o AdGuardu Mini pro Mac, který chrání pouze váš prohlíž ## Limity pravidel pro blokování obsahu v Safari -AdGuard Mini for Mac uses the Content Blocking API to apply filtering rules to pages in the Safari browser. V současné době je pro každé rozšíření blokování obsahu povoleno maximálně 150 000 pravidel. +AdGuard Mini pro Mac používá rozhraní API pro blokování obsahu k použití pravidel filtrování na stránky v prohlížeči Safari. V současné době je pro každé rozšíření blokování obsahu povoleno maximálně 150 000 pravidel. -AdGuard Mini for Mac has 6 content blockers: +AdGuard Mini pro Mac má 6 blokátorů obsahu: - AdGuard – General - AdGuard – Privacy @@ -24,13 +24,13 @@ AdGuard Mini for Mac has 6 content blockers: Celkem tak vznikne 900000 pravidel filtrování. -However, **one extension can contain only up to 150,000 rules**. Pokud tento limit překročíte, některá pravidla se neuplatní. To může vést k nesprávnému blokování. +Nicméně **jedno rozšíření může obsahovat až 150000 pravidel**. Pokud tento limit překročíte, některá pravidla se neuplatní. To může vést k nesprávnému blokování. ## Jak zkontrolovat překročení limitu pravidel -1. Open AdGuard Mini app. -2. Go to _Settings_ → _Safari extensions_. -3. Below each extension, you can see the enabled filters and the number of active rules. +1. Otevřete aplikaci AdGuard Mini. +2. Přejděte do _nastavení_ → _rozšíření Safari_. +3. Pod každým rozšířením můžete vidět povolené filtry a počet aktivních pravidel. ![Extensions tab](https://cdn.adtidy.org/content/kb/ad_blocker/mini_mac/extensions.png) Pokud je v blokátoru obsahu povoleno více než 150 000 pravidel, může být nutné zakázat některé filtry nebo uživatelská pravidla. Přejděte na _Filtry_, vyberte problematickou kategorii a zakažte filtry nebo uživatelská pravidla, která nepotřebujete. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/solving-problems/solving-problems.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/solving-problems/solving-problems.md index 5b3708a662c..c43c4aa040f 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/solving-problems/solving-problems.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-mini-for-mac/solving-problems/solving-problems.md @@ -9,10 +9,10 @@ Tento článek je o AdGuardu Mini pro Mac, který chrání pouze váš prohlíž ::: -Here are some problems you may encounter and workarounds, as well as guides and instructions you may need: +Zde jsou uvedeny některé problémy, se kterými se můžete setkat, řešení, průvodci a pokyny, které můžete potřebovat: -- [Rule limit issues](/adguard-mini-for-mac/solving-problems/rule-limit.md) -- [Filtering doesn’t work and ads aren’t blocked](/adguard-mini-for-mac/solving-problems/ads-not-blocked.md) -- [Filtering doesn’t stop when AdGuard Mini is disabled](/adguard-mini-for-mac/solving-problems/filters-after-disable.md) -- [How to collect logs in AdGuard Mini for Mac](/adguard-mini-for-mac/solving-problems/logs.md) -- [AdGuard Mini doesn’t work in private tabs on macOS Sonoma](/adguard-mini-for-mac/solving-problems/private-sonoma.md) +- [Problémy s limitem počtu pravidel](/adguard-mini-for-mac/solving-problems/rule-limit.md) +- [Filtrování nefunguje a reklamy nejsou zablokovány](/adguard-mini-for-mac/solving-problems/ads-not-blocked.md) +- [Filtrování se neukončí, když je AdGuard Mini vypnutý](/adguard-mini-for-mac/solving-problems/filters-after-disable.md) +- [Jak sbírat logy v AdGuard Mini pro Mac](/adguard-mini-for-mac/solving-problems/logs.md) +- [AdGuard Mini nefunguje v soukromých kartách na macOS Sonoma](/adguard-mini-for-mac/solving-problems/private-sonoma.md) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index d047ecb0701..9166be3e3d8 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ Následující modifikátory jsou nejjednodušší a nejčastěji používané. | Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard Mini pro Mac][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ V následujících příkladech se předpokládá, že požadavky jsou odesílá :::caution Omezení -V [AdGuardu pro Chrome MV3][ext-mv3] nejsou podporovány domény s `regexp` a `any_tld_domain`. +V [AdGuardu pro Chrome MV3][ext-mv3] nejsou podporovány domény s `regexp` a `any_tld_domain` a modifikátory `$removeparam`. AdGuard pro iOS a AdGuard pro Safari podporují modifikátor `$domain`, ale má některá omezení. Pro více informací navštivte [sekci SafariConverterLib](#safari-converter--basic--supported-with-limitations). @@ -630,7 +630,7 @@ kde: 1. V Rozšíření prohlížeče AdGuard je modifikátor `$header` kompatibilní poze s [`$csp`](#csp-modifier), [`$removeheader`](#removeheader-modifier) (pouze hlavičky odpovědí), [`$important`](#important-modifier), [`$badfilter`](#badfilter-modifier), [`$domain`](#domain-modifier), [`$third-party`](#third-party-modifier), [`$match-case`](#match-case-modifier) s [content-type modifiers](#content-type-modifiers) jako [`$script`](#script-modifier) a [`$stylesheet`](#stylesheet-modifier). Pravidla s jinými modifikátory jsou považována za neplatná a budou vyřazena. -1. In AdGuard Browser Extension MV3, regular expressions in the `$header` modifier values are not supported. +1. V Rozšíření prohlížeče AdGuard MV3 nejsou podporovány regulární výrazy v hodnotách modifikátoru `$header`. ::: @@ -2670,6 +2670,7 @@ Pravidla `$removeparam` lze také zakázat pravidly výjimek `$document` a `$url [AdGuard pro Chrome MV3][ext-mv3] má některá omezení: - Regulární výrazy, negace a pravidla seznamu povolených nejsou podporovány. +- Generická pravidla se uplatňují před specifickými pravidly a přesměrování se provádí pouze jednou. To může zabránit použití následných nebo konkrétnějších přesměrování. - Skupina podobných `$removeparam` budou sloučena do jedné. Příklad: ```bash @@ -2737,6 +2738,7 @@ Pravidla `$removeparam` lze také zakázat pravidly výjimek `$document` a `$url 1. Pravidla s modifikátorem `$removeparam` lze použít [**pouze v důvěryhodných filtrech**](#trusted-filters). 1. Pravidla `$removeparam` jsou kompatibilní se [základními modifikátory](#basic-rules-basic-modifiers), [modifikátory typu obsahu](#content-type-modifiers) a s modifikátory `$important` a `$app`. Pravidla s jinými modifikátory jsou považována za neplatná a budou vyřazena. +1. Ačkoli je modifikátor `$domain` klasifikován jako základní, není kompatibilní s pravidly `$removeparam` v rozšíření Manifest V3. 1. Pravidla `$removeparam`, která neobsahují žádné [modifikátory typu obsahu](#content-type-modifiers), budou odpovídat pouze požadavkům, jejichž typem obsahu je `document`. ::: @@ -2944,7 +2946,7 @@ Sledovací odkazy se nyní automaticky vyčistí a umožní přímou navigaci na Pravidla s modifikátorem `$urltransform` lze použít [**pouze v důvěryhodných filtrech**](#trusted-filters). -`$urltransform` rules without [content-type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. +Pravidla `$urltransform`, která neobsahují žádné [modifikátory typu obsahu](#content-type-modifiers), budou odpovídat pouze požadavkům, jejichž typem obsahu je `document`. ::: @@ -2952,7 +2954,7 @@ Pravidla s modifikátorem `$urltransform` lze použít [**pouze v důvěryhodný Pravidla s modifikátorem `$urltransform` jsou podporována AdGuardem pro Windows, Mac, Android a Linux s [CoreLibs][] v1.15 nebo novější. -`$urltransform` rules with [content-type modifiers](#content-type-modifiers) are supported starting from [CoreLibs][] v1.19 or later. In earlier versions, content-type modifiers were not allowed with `$urltransform`. +`$urltransform` pravidla s [modifikátory typu obsahu](#content-type-modifiers) jsou podporována od [CoreLibs][] v1.19 nebo novější. V dřívějších verzích nebyly modifikátory typu obsahu povoleny s `$urltransform`. ::: @@ -4676,7 +4678,7 @@ Modifikátor `$path` podporuje regulární výrazy [stejným způsobem](#regexp- #### Syntaxe Path-in-domain {#path-in-domain-syntax} -For cosmetic rules, you can use a simplified path-in-domain syntax by specifying the path directly in the domain part of the rule instead of using the `$path` modifier. +U kosmetických pravidel můžete použít zjednodušenou syntaxi cesta v doméně tak, že zadáte cestu přímo v doménové části pravidla místo použití modifikátoru `$path`. **Syntaxe** @@ -4693,11 +4695,11 @@ targets = [target0, target1[, ...[, targetN]]] - `domain1.com,example.org/cesta##.banner` — platí pro všechny stránky na `domain1.com` a pouze pro `/path` stránky na `example.org` - `/example\.org\/article\d+/##.ad` — skrývá reklamy na stránkách článků s číselnými ID -Path-in-domain syntax works with all types of cosmetic rules (`##`, `#@#`, `#$#`, `$$`, `$@$`, `#%#`, `#@%#`) +Syntaxe cesty v doméně funguje se všemi typy kosmetických pravidel (`##`, `#@#`, `#$#`, `$$`, `$@$`, `#%#`, `#@%#`) :::info Kompatibilita -Path-in-domain syntax has been introduced in [CoreLibs][] v1.20. +Syntaxe Path-in-domain byla zavedena v [CoreLibs][] v1.20. ::: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index 318c587f415..1adc82717c7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ Um den Schutz zu deaktivieren, geben Sie ein: adguard-cli stop ``` -Dieser Befehl stoppt nicht nur den Proxy, sondern auch die Weiterleitung des Datenverkehrs zu ihm. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Schutzstatus prüfen @@ -45,101 +45,155 @@ adguard-cli status ![Status/Schutz stoppen \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) -## Aktualisierungen +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + +## Updates ### Auf Aktualisierungen prüfen -Um auf Aktualisierungen zu prüfen, geben Sie ein: +To check for updates, enter: ```sh adguard-cli check-update ``` -### AdGuard für Linux aktualisieren +### Update AdGuard for Linux -Um AdGuard für Linux zu aktualisieren, geben Sie ein: +To update AdGuard for Linux, enter: ```sh adguard-cli update ``` -### Skriptausgabe aktualisieren +### Update script output -Um die Ausgabe des Aktualisierungsskripts anzuzeigen, geben Sie ein: +To view the update script output, enter: ```sh adguard-cli update -v ``` -## AdGuard für Linux konfigurieren +## Configure AdGuard for Linux + +Use the `config` command to configure AdGuard for Linux. Subcommands: -Verwenden Sie den Befehl `config`, um AdGuard für Linux zu konfigurieren. Unterbefehle: +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) -- `show`: Die aktuelle Konfiguration in `proxy.yaml` anzeigen + ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) - ![Aktuelle Einrichtung \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) +- `set `: Configure an option in `proxy.yaml` + - `listen_ports.http_proxy`: HTTP listening port + - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `set`: Eine Option in `proxy.yaml` konfigurieren - - `listen_ports.http_proxy`: HTTP-Lauschport - - `proxy_mode`: Proxy-Modus (`manual` oder `auto`) +- `get `: Get the current status of a setting -- `get`: Den aktuellen Status der oben genannten Optionen abrufen +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note -Der Automatikmodus kann nur verwendet werden, wenn folgende Voraussetzungen erfüllt sind: +The Automatic mode can only be used if the following requirements are met: -- `iptables` ist installiert und wird ausgeführt (entweder `nft` oder `legacy`) -- `iptables` unterstützt die `nat`-Tabelle sowohl für IPv4 als auch für IPv6 -- `iptables` unterstützt die `REDIRECT`- und `QUEUE`-Ketten sowohl für IPv4 als auch für IPv6 -- Das Paket `sudo` wurde installiert +- `iptables` is installed and running (either `nft` or `legacy`) +- `iptables` supports the `nat` table for both IPv4 and IPv6 +- `iptables` supports the `REDIRECT` and `QUEUE` chains for both IPv4 and IPv6 +- The `sudo` package is installed ::: -## Filter verwalten +## Manage filters + +Use the `filters` command to configure AdGuard for Linux. Subcommands: + +- `list`: List installed and added filters + + - `--all`: View all filters + + ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) + +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter + + ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) + +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter -Verwenden Sie den Befehl `filters`, um AdGuard für Linux zu konfigurieren. Unterbefehle: +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). -- `list`: Liste der installierten Filter +## Manage DNS filters - - `--all`: Alle Filter anzeigen +Use the `dns filters` command to manage DNS filter lists. Subcommands: - ![Filterliste \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter -- `install`: Einen Filter installieren. Geben Sie die URL des Filters ein, den Sie installieren möchten +DNS filter updates are handled by `adguard-cli check-update`. -- `enable`: Einen Filter aktivieren. Geben Sie den Namen oder die ID des Filters ein +## Manage userscripts - ![Filter aktivieren \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) +Use the `userscripts` command to manage userscripts. Subcommands: -- 'disable': Einen Filter deaktivieren. Geben Sie den Namen oder die ID des Filters ein +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- 'update': Filter aktualisieren +Userscripts are updated by `adguard-cli check-update`. -## Lauschadresse des Proxyservers im manuellen Proxymodus ändern +## Changing the proxy server listen address in manual proxy mode -Standardmäßig lauscht der Proxyserver auf `127.0.0.1` — die Adresse der Loopback-Netzwerkschnittstelle. -Es gibt zwei Möglichkeiten, den Proxyserver an einer anderen Schnittstelle lauschen zu lassen: +By default, the proxy server listens on `127.0.0.1` — the address of the loopback network interface. +There are two ways to make the proxy server listen on a different interface: -1. Führen Sie `adguard-cli config set listen_address
` aus, wobei `
` die Adresse ist, auf die gelauscht werden soll. -2. Konfigurationsdatei direkt bearbeiten: - - Um den Speicherort der Konfigurationsdatei zu ermitteln, führen Sie `adguard-cli config show | grep "Config location"` aus. - - Suchen Sie nach dem Schlüssel `listen_address` und setzen Sie dessen Wert entsprechend. Um auf allen verfügbaren Netzwerkschnittstellen zu lauschen, setzen Sie die Listen-Adresse auf `0.0.0.0` oder `::`. +1. Run `adguard-cli config set listen_address
` where `
` is the address to listen on. +2. Edit the config file directly: + - To determine the location of the config file, run `adguard-cli config show | grep "Config location"`. + - Look for the `listen_address` key and set its value accordingly. To listen on all available network interfaces, set the listen address to `0.0.0.0` or `::`. -Wenn die Lauschadresse auf einen anderen Wert als `127.0.0.1` eingestellt ist, ist eine Authentifizierung des Proxy-Clients erforderlich. AdGuard CLI startet nicht, wenn keine Proxy-Authentifizierung konfiguriert ist: +If the listen address is set to anything other than `127.0.0.1`, then proxy client authentication is required. AdGuard CLI will not start unless proxy authentication is configured: -- Wenn Sie `adguard-cli config set listen_address
` ausführen, wobei `
` nicht `127.0.0.1` ist, wird AdGuard CLI nach einem Benutzernamen und Passwort fragen, wenn die Proxy-Authentifizierung nicht bereits konfiguriert ist. -- Wenn Sie die Konfigurationsdatei direkt bearbeiten, suchen Sie nach dem Schlüssel `listen_auth`. Setzen Sie den Unterschlüssel `enabled` auf `true` und geben Sie Werte für `username` und `password` ein. +- When running `adguard-cli config set listen_address
` where `
` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured. +- When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values. -## Ausgehenden Proxy konfigurieren +## Configure outbound proxy -Sie können `outbound_proxy` konfigurieren, wenn Sie möchten, dass AdGuard CLI einen anderen Proxy-Server verwendet. +You can configure `outbound_proxy` if you want AdGuard CLI to work through another proxy server. -Es gibt zwei Möglichkeiten, dies zu konfigurieren: +There are two ways to configure it: -### 1. Über URL konfigurieren (empfohlen) +### 1. Configure via URL (recommended) -Anstatt jede Option Schritt für Schritt festzulegen, können Sie alle Parameter in einer einzigen Zeile mithilfe einer URL festlegen: +Instead of setting each option step by step, you can set all parameters in a single line using a URL: ```sh adguard-cli config set outbound_proxy https://user:pass@host:port @@ -147,25 +201,25 @@ adguard-cli config set outbound_proxy https://user:pass@host:port :::info -Unterstützte Modi sind HTTP, HTTPS, SOCKS4 und SOCKS5. +Supported modes are HTTP, HTTPS, SOCKS4, and SOCKS5. ::: -Sie können `outbound_proxy` auch schnell aktivieren oder deaktivieren: +You can also quickly enable or disable `outbound_proxy`: ```sh adguard-cli config set outbound_proxy false ``` -Oder löschen Sie schnell die Einstellungen: +Or quickly clear the settings: ```sh adguard-cli config set outbound_proxy "" ``` -### 2. Eigene Parameter festlegen +### 2. Configure individual parameters -Die Möglichkeit, bestimmte Parameter anzupassen, ist ebenfalls verfügbar: +The ability to adjust specific parameters is also available: ```sh adguard-cli config set outbound_proxy.enabled true @@ -175,13 +229,13 @@ adguard-cli config set outbound_proxy.username user adguard-cli config set outbound_proxy.password pass ``` -Zertifikatsüberprüfung für HTTPS-Proxys deaktivieren: +Disable certificate verification for HTTPS proxies: ```sh adguard-cli config set outbound_proxy.trust_any_certificate true ``` -SOCKS5-Proxy für UDP-Datenverkehr aktivieren: +Enable SOCKS5 proxy for UDP traffic: ```sh adguard-cli config set outbound_proxy.udp_through_socks5_enabled true @@ -189,21 +243,21 @@ adguard-cli config set outbound_proxy.udp_through_socks5_enabled true :::note -Wenn Ihr SOCKS5-Proxy UDP nicht unterstützt, können Verbindungen fehlschlagen. +If your SOCKS5 proxy does not support UDP, connections may fail. ::: -## AdGuard CLI-Konfiguration pro App +## Per-app AdGuard CLI configuration -Benutzer müssen das Filtern für bestimmte Browser oft manuell aktivieren. AdGuard für Linux unterstützt die **Konfiguration pro App**, sodass Sie Einstellungen oder Regeln individuell für jede Anwendung anwenden können, anstatt sie systemweit zu übernehmen. +Users often need to enable filtering manually for certain browsers. AdGuard for Linux supports **per-app configuration**, allowing you to apply settings or rules individually to each application instead of system-wide. -Weitere Informationen finden Sie im Abschnitt `apps` in `proxy.yaml`. +For details, refer to the `apps` section in `proxy.yaml`. -Eine Reihe vorkonfigurierter Einträge für gängige Webbrowser ist standardmäßig in `browsers.yaml` enthalten. +A set of pre-configured entries for popular web browsers is included by default in `browsers.yaml`. -### Überprüfung der aktuellen Konfiguration +### Checking the current configuration -Um die aktuelle Konfiguration von `outbound_proxy` anzuzeigen, geben Sie Folgendes ein: +To view the current `outbound_proxy` configuration, enter: ```sh adguard-cli config show outbound_proxy @@ -211,23 +265,23 @@ adguard-cli config show outbound_proxy :::info Kompatibilität -Die Konfiguration von `outbound_proxy` über URL ist ab AdGuard für Linux v1.1.26 Nightly und v1.1 Stable Release verfügbar. +Configuring `outbound_proxy` via URL is available starting from AdGuard for Linux v1.1.26 nightly and v1.1 stable release. ::: -## Einstellungen exportieren und importieren +## Export and import settings -Mit der Export-/Importfunktion können Sie Ihre AdGuard-CLI-Konfiguration sichern und auf demselben oder einem anderen System wiederherstellen. Dazu gehören Filter, Proxy-Einstellungen und andere Konfigurationseistellungen. +The export/import functionality allows you to backup your AdGuard CLI configuration and restore it on the same or different system. This includes filters, proxy settings, and other configuration options. -### Einstellungen exportieren +### Export settings -Um die aktuellen AdGuard-CLI-Einstellungen in ein ZIP-Archiv zu exportieren, verwenden Sie: +To export current AdGuard CLI settings to a ZIP archive, use: ```sh adguard-cli export-settings ``` -Sie können den Ausgabepfad mit dem Parameter `-o` oder `--output` angeben. Dies kann entweder ein bestimmter Dateipfad oder ein Ordner sein: +You can specify the output path using the `-o` or `--output` flag. This can be either a specific file path or a directory: ```sh # Export to a specific file @@ -237,14 +291,14 @@ adguard-cli export-settings -o "/path/to/settings.zip" adguard-cli export-settings -o "/path/to/directory" ``` -Wenn kein Ausgabepfad angegeben ist, werden die Einstellungen unter einem Standardnamen in das Arbeitsverzeichnis exportiert. Nach erfolgreichem Export zeigt der Befehl den vollständigen Pfad an, in dem das Archiv erstellt wurde. +If no output path is specified, the settings will be exported to the working directory with a standard name. After successful export, the command will display the full path where the archive was created. -### Einstellungen importieren +### Import settings -Um AdGuard CLI-Einstellungen aus einem ZIP-Archiv zu importieren, verwenden Sie: +To import AdGuard CLI settings from a ZIP archive, use: ```sh adguard-cli import-settings -i "/path/to/settings.zip" ``` -Die Option `-i` oder `--input` ist erforderlich und gibt den Pfad zum zu importierenden Archiv mit den Einstellungen an. +The `-i` or `--input` flag is required and specifies the path to the settings archive to import. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 4a2bbb061db..ac63d36aa38 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc Das Modul _Netzwerk_ ist der Netzwerkfilterung gewidmet, und hier finden Sie zusätzliche netzwerkbezogene Optionen. Zwei davon sind standardmäßig aktiviert: _Datenverkehrsfilterung aktivieren_ und _HTTPS filtern_. Dies sind wichtige zusätzliche Vorsichtsmaßnahmen, um Ihren Webspace besser zu filtern. Die meisten Websites verwenden jetzt HTTPS, und dies gilt auch für die Werbung. Von vielen Websites, wie youtube.com, facebook.com und x.com, ist es unmöglich, Werbung ohne HTTPS-Filterung zu entfernen. Lassen Sie also die Funktion _HTTPS filtern_ aktiviert, es sei denn, Sie haben einen triftigen Grund, dies nicht zu tun. -![Netzwerkeinstellungen \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In diesem Modul können Sie das Kontrollkästchen _AdGuard als HTTP-Proxy verwenden_ aktivieren, um AdGuard als regulären HTTP-Proxy zu verwenden, der den gesamten Datenverkehr filtert, der ihn durchläuft. Sie können auch die Funktion _Websites mit EV-Zertifikaten filtern_ aktivieren. Extended Validation (EV) SSL-Zertifikate bieten eine stärkere Sicherheitsgarantie; die Inhaber solcher Websites müssen ein gründliches und weltweit standardisiertes Identitätsprüfungsverfahren durchlaufen, das durch EV-Richtlinien definiert ist. Daher werden Websites mit solchen Zertifikaten vertraut und nicht gefiltert. Schließlich gibt es noch einen Abschnitt mit Proxy-Einstellungen. Dort können Sie angeben, welchen Proxyserver AdGuard verwenden soll, um Filter zu aktualisieren, neue Versionen zu erhalten usw. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -Der letzte Abschnitt ist AdGuard VPN gewidmet, einem nützlichen Tool, das Sicherheit und Anonymität beim Surfen im Internet bietet. Sie können es herunterladen, indem Sie auf die Schaltfläche _Herunterladen_ klicken, oder Sie können die AdGuard VPN-Website aufrufen, indem Sie auf die Schaltfläche _Homepage_ klicken. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -Wie funktioniert AdGuard VPN? Ohne auf technische Details einzugehen, kann gesagt werden, dass VPN einen sicheren verschlüsselten Tunnel zwischen einem Gerät und einem entfernten VPN-Server herstellt. Auf diese Weise bleibt der Datenschutz gewahrt und damit auch die Anonymität, denn ein fremder Beobachter sieht die IP-Adresse des VPN-Servers und nicht die tatsächliche IP-Adresse. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**Was AdGuard VPN leistet:** +**What AdGuard VPN does:** -- verbirgt Ihren tatsächlichen Aufenthaltsort und hilft Ihnen, anonym zu bleiben -- ändert Ihre IP-Adresse, um Ihre Daten vor Verfolgung zu schützen -- verschlüsselt Ihren Datenverkehr, um ihn für Dritte unlesbar zu machen -- lässt Sie konfigurieren, wo VPN verwendet werden soll und wo nicht (Ausschlussfunktion) +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -Weitere Informationen über AdGuard VPN finden Sie in der [AdGuard VPN Wissensdatenbank](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index c1dce511c9a..096f60231cf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ Die folgenden Modifikatoren sind die einfachsten und am häufigsten verwendeten. | Modifikator \ Produkte | [CoreLibs-Apps][cl-apps] | [AdGuard für Chromium][ext-chr] | [AdGuard für Chrome MV3][ext-mv3] | [AdGuard für Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard Mini für Mac][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Beispiel: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index 159d80cbfeb..1a9a1da9c65 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ Para deshabilitar la protección, ingresa: adguard-cli stop ``` -Este comando no solo detiene el proxy, sino que también detiene el tráfico de redirección hacia él. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Comprobar el estado de protección @@ -45,45 +45,61 @@ adguard-cli status ![Estado/Detener protección \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) -## Actualizaciones +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + +## Updates ### Buscar actualizaciones -Para buscar actualizaciones, ingresa: +To check for updates, enter: ```sh adguard-cli check-update ``` -### Actualizar AdGuard para Linux +### Update AdGuard for Linux -Para actualizar AdGuard para Linux, ingresa: +To update AdGuard for Linux, enter: ```sh adguard-cli update ``` -### Actualizar la salida del script +### Update script output -Para ver la salida del script de actualización, ingresa: +To view the update script output, enter: ```sh adguard-cli update -v ``` -## Configurando o AdGuard para Linux +## Configure AdGuard for Linux + +Use the `config` command to configure AdGuard for Linux. Subcommands: -Usa el comando `config` para configurar AdGuard para Linux. Subcomandos: +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) -- `show`: Muestra la configuración actual en `proxy.yaml` + ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) - ![Configuración actual \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) +- `set `: Configure an option in `proxy.yaml` + - `listen_ports.http_proxy`: HTTP listening port + - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `set`: Configurar una opción en `proxy.yaml` - - `listen_ports.http_proxy`: puerto HTTP de escucha - - `proxy_mode`: Modo proxy (`manual` u `auto`) +- `get `: Get the current status of a setting -- `get`: Obtener el estado actual de las opciones anteriores +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -96,40 +112,78 @@ The Automatic mode can only be used if the following requirements are met: ::: -## Administrar filtros +## Manage filters + +Use the `filters` command to configure AdGuard for Linux. Subcommands: + +- `list`: List installed and added filters + + - `--all`: View all filters + + ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) + +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter + + ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) + +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter -Usa el comando `filters` para configurar AdGuard para Linux. Subcomandos: +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). -- `list`: Listar filtros instalados +## Manage DNS filters - - `--all`: Ver todos los filtrados +Use the `dns filters` command to manage DNS filter lists. Subcommands: - ![Lista de filtros \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter -- `install`: Instalar un filtro. Ingrese la URL del filtrado que deseas instalar +DNS filter updates are handled by `adguard-cli check-update`. -- `enable`: Habilitar un filtro. Introduce el nombre o ID del filtro +## Manage userscripts - ![Habilitar filtros \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) +Use the `userscripts` command to manage userscripts. Subcommands: -- `disable`: Deshabilitar un filtro. Introduce el nombre o ID del filtro +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update`: Actualiza los filtros +Userscripts are updated by `adguard-cli check-update`. -## Cambiando la dirección de escucha del proxy en modo proxy manual +## Changing the proxy server listen address in manual proxy mode -De forma predeterminada, el proxy escucha en `127.0.0.1` — la dirección de la interfaz de red de loopback invertido. -Hay dos formas de hacer que el proxy escuche en una interfaz diferente: +By default, the proxy server listens on `127.0.0.1` — the address of the loopback network interface. +There are two ways to make the proxy server listen on a different interface: -1. Ejecuta `adguard-cli config set listen_address ` donde `` es la dirección a la que escuchar. -2. Edita el archivo de configuración directamente: - - Para determinar la ubicación del archivo de configuración, ejecuta `adguard-cli config show | grep "Config location"`. - - Busca la clave `listen_address` y establece su valor en consecuencia. Para escuchar en todas las interfaces de red disponibles, establece la dirección de escucha en `0.0.0.0` o `::`. +1. Run `adguard-cli config set listen_address
` where `
` is the address to listen on. +2. Edit the config file directly: + - To determine the location of the config file, run `adguard-cli config show | grep "Config location"`. + - Look for the `listen_address` key and set its value accordingly. To listen on all available network interfaces, set the listen address to `0.0.0.0` or `::`. -Si la dirección de escucha está configurada en algo diferente a `127.0.0.1`, se requiere la autenticación del cliente proxy. AdGuard CLI no se iniciará a menos que se configure la autenticación del proxy: +If the listen address is set to anything other than `127.0.0.1`, then proxy client authentication is required. AdGuard CLI will not start unless proxy authentication is configured: -- Al ejecutar `adguard-cli config set listen_address
` donde `
` no es `127.0.0.1`, AdGuard CLI solicitará un nombre de usuario y una contraseña si la autenticación del proxy no está configurada. -- Al editar el archivo de configuración directamente, busca la clave `listen_auth`. Establece la subclave `enabled` en `true`, y `username` y `password` en valores no vacíos. +- When running `adguard-cli config set listen_address
` where `
` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured. +- When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values. ## Configure outbound proxy diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 0dc961cd68c..9a652fb1281 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ Este artículo trata sobre AdGuard para Windows, un bloqueador de anuncios multi El _módulo_ de _red_ está dedicado al filtrado de _redes_ y aquí encontrarás opciones adicionales relacionadas con la _red_. Dos de ellos están habilitados de forma predeterminada: _Habilitar filtrado de tráfico_ y _Filtrar HTTPS_. Estas son precauciones adicionales importantes para filtrar mejor tu internet. La mayoría de los sitios web utilizan ahora HTTPS y lo mismo se aplica a la publicidad. En muchos sitios web, como youtube.com, facebook.com y x.com, es imposible eliminar anuncios sin el filtrado HTTPS. Así que mantén habilitada la función _Filtrar HTTPS_ a menos que tengas una buena razón para no hacerlo. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) En este módulo, puedes marcar la casilla de verificación _Usar AdGuard como proxy HTTP_ para usar AdGuard como un proxy HTTP normal que filtrará todo el tráfico que pasa a través de él. También puedes habilitar la función _Filtrar sitios web con certificados EV_. Los certificados SSL de validación extendida (EV) ofrecen una garantía de seguridad más sólida; los propietarios de dichos sitios web deben pasar un proceso de verificación de identidad exhaustivo y estandarizado a nivel mundial definido por las directrices EV. Esta es la razón por la que algunos usuarios confían en sitios web con dichos certificados y prefieren no filtrarlos. Por fin, hay una sección con configuración de proxy. Allí puedes especificar qué servidor proxy AdGuard debe utilizar para actualizar los filtros, obtener nuevas versiones, etc. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -La última sección está dedicada a AdGuard VPN, una herramienta ideal que brinda seguridad y anonimato cada vez que navegas por Internet. Puedes descargarlo haciendo clic en el botón _Descargar_ o ir al sitio web de AdGuard VPN haciendo clic en el botón _Página de inicio_. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -¿Cómo funciona AdGuard VPN? Sin entrar en detalles técnicos, podemos decir que la VPN crea un túnel cifrado seguro entre la computadora o dispositivo móvil del usuario y un servidor VPN remoto. De esta manera, se preserva la privacidad de los datos, así como el anonimato del usuario, porque un observador externo ve la dirección IP del servidor VPN y no la dirección IP verdadera del usuario. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**Qué hace AdGuard VPN:** +**What AdGuard VPN does:** -- oculta tu paradero real y te ayuda a permanecer en el anonimato -- cambia tu dirección IP para proteger tus datos del seguimiento -- cifra tu tráfico para hacerlo ilegible para terceros -- te permite configurar dónde usar la VPN y dónde no usarla (función de exclusiones) +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -Para obtener más información sobre AdGuard VPN, consulta la [Base de conocimientos de AdGuard VPN](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 9fcad184a7a..573d3e262e3 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard para Chromium][ext-chr] | [AdGuard para Chrome MV3][ext-mv3] | [AdGuard para Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-----------------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index e223b9090df..c1a8b701681 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ Pour désactiver la protection, saisissez : adguard-cli stop ``` -Cette commande arrête le proxy, mais elle empêche également le trafic d'y être redirigé. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Vérifier l'état de protection @@ -45,45 +45,61 @@ adguard-cli status ![État/Arrêter la protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) -## Mises à jour +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + +## Updates ### Vérification des mises à jour -Pour vérifier les mises à jour, saisissez : +To check for updates, enter: ```sh adguard-cli check-update ``` -### Mettre à jour AdGuard pour Linux +### Update AdGuard for Linux -Pour mettre à jour AdGuard pour Linux, saisissez : +To update AdGuard for Linux, enter: ```sh adguard-cli update ``` -### Mettre à jour la sortie du script +### Update script output -Pour voir la sortie du script de mise à jour, il faut saisir : +To view the update script output, enter: ```sh adguard-cli update -v ``` -## Configuration d'AdGuard pour Linux +## Configure AdGuard for Linux + +Use the `config` command to configure AdGuard for Linux. Subcommands: -Utilisez la commande `config` pour configurer AdGuard pour Linux. Sous-commandes : +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) -- `afficher`: Afficher la configuration actuelle dans `proxy.yaml` + ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) - ![Configuration actuelle \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) +- `set `: Configure an option in `proxy.yaml` + - `listen_ports.http_proxy`: HTTP listening port + - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `définir`: Configurer une option dans `proxy.yaml` - - `listen_ports.http_proxy`: Port d'écoute HTTP - - `proxy_mode`: Mode proxy (`manuel` ou `auto`) +- `get `: Get the current status of a setting -- `get` : Obtenir l'état actuel des options ci-dessus +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -96,40 +112,78 @@ The Automatic mode can only be used if the following requirements are met: ::: -## Gestion des filtres +## Manage filters + +Use the `filters` command to configure AdGuard for Linux. Subcommands: + +- `list`: List installed and added filters + + - `--all`: View all filters + + ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) + +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter + + ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) + +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter -Utilisez la commande `filters` pour configurer AdGuard pour Linux. Sous-commandes : +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). -- `list` : Liste des filtres installés +## Manage DNS filters - - `--all`: Afficher tous les filtres +Use the `dns filters` command to manage DNS filter lists. Subcommands: - ![Liste des filtres \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter -- `install` : Installer un filtre. Saisissez l'URL du filtre que vous souhaitez installer +DNS filter updates are handled by `adguard-cli check-update`. -- `activer`: Activer un filtre. Saisissez le nom ou l'ID du filtre +## Manage userscripts - ![Activer les filtres \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) +Use the `userscripts` command to manage userscripts. Subcommands: -- `désactiver`: Désactiver un filtre. Saisissez le nom ou l'ID du filtre +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update` : Mise à jour des filtres +Userscripts are updated by `adguard-cli check-update`. -## Modification de l'adresse d'écoute du serveur proxy en mode proxy manuel +## Changing the proxy server listen address in manual proxy mode -Par défaut, le proxy écoute sur `127.0.0.1` — l'adresse de l'interface réseau de bouclage local. -Il y a deux façons de faire écouter le proxy sur une interface différente : +By default, the proxy server listens on `127.0.0.1` — the address of the loopback network interface. +There are two ways to make the proxy server listen on a different interface: -1. Exécutez `adguard-cli config set listen_address
` où `
` est l'adresse à écouter. -2. Modifiez directement le fichier de configuration : - - Pour déterminer l'emplacement du fichier de configuration, exécutez `adguard-cli config show | grep "Config location"`. - - Recherchez la clé `listen_address` et définissez sa valeur en conséquence. Pour écouter sur toutes les interfaces réseau disponibles, définissez l'adresse d'écoute sur `0.0.0.0` ou `::`. +1. Run `adguard-cli config set listen_address
` where `
` is the address to listen on. +2. Edit the config file directly: + - To determine the location of the config file, run `adguard-cli config show | grep "Config location"`. + - Look for the `listen_address` key and set its value accordingly. To listen on all available network interfaces, set the listen address to `0.0.0.0` or `::`. -Si l'adresse d'écoute est définie sur autre chose que `127.0.0.1`, alors l'authentification du client proxy est obligatoire. AdGuard CLI ne démarrera pas à moins que l'authentification du proxy ne soit configurée : +If the listen address is set to anything other than `127.0.0.1`, then proxy client authentication is required. AdGuard CLI will not start unless proxy authentication is configured: -- Lors de l'exécution de `adguard-cli config set listen_address
` où `
` n'est pas `127.0.0.1`, AdGuard CLI demandera un nom d'utilisateur et un mot de passe si l'authentification proxy n'est pas déjà configurée. -- Lorsque vous modifiez directement le fichier de configuration, recherchez la clé `listen_auth`. Définissez la sous-clé `enabled` à `true`, et `username` et `password` à des valeurs non vides. +- When running `adguard-cli config set listen_address
` where `
` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured. +- When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values. ## Configure outbound proxy diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 78b22cdd0f3..1c048943a42 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ Cet article parle de AdGuard pour Windows, un bloqueur de contenus multifonction Le module _Réseau_ est dédié au filtrage réseau, et vous y trouverez des options supplémentaires liées au réseau. Deux d'entre elles sont activées par défaut : _Activer le filtrage du trafic_ et _Filtrer HTTPS_. Ce sont des précautions supplémentaires importantes pour mieux filtrer votre espace web. La plupart des sites web utilisent désormais HTTPS, et il en va de même pour la publicité. Sur de nombreux sites, comme youtube.com, facebook.com, et x.com, il est impossible de supprimer les publicités sans filtrage HTTPS. Il est donc recommandé de garder l'option _Filtrer HTTPS_ activée, sauf si vous avez une bonne raison de ne pas le faire. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) Dans ce module, vous pouvez cocher la case _Utiliser AdGuard comme proxy HTTP_ pour utiliser AdGuard comme un proxy HTTP classique, qui filtrera tout le trafic passant par lui. Vous pouvez également activer la fonctionnalité _Filtrer les sites web avec des certificats EV_. Les certificats SSL à Validation Étendue (EV) offrent une garantie de sécurité renforcée ; les propriétaires de ces sites doivent passer un processus de vérification d'identité rigoureux et standardisé au niveau mondial, défini par les directives EV. C'est pourquoi certains utilisateurs font confiance aux sites disposant de tels certificats et préfèrent ne pas les filtrer. Enfin, il y a une section avec les paramètres de proxy. Vous pouvez y spécifier quel serveur proxy AdGuard doit utiliser pour mettre à jour les filtres, obtenir de nouvelles versions, et ainsi de suite. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -La dernière section est dédiée à AdGuard VPN — un outil idéal qui offre sécurité et anonymat à chaque fois que vous naviguez sur Internet. Vous pouvez le télécharger en cliquant sur le bouton _Télécharger_ ou accéder au site web d'AdGuard VPN en cliquant sur le bouton _Page d'accueil_. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -Comment fonctionne AdGuard VPN ? Sans entrer dans les détails techniques, on peut dire que le VPN crée un tunnel sécurisé et crypté entre l'ordinateur ou le mobile de l'utilisateur et un serveur VPN distant. De cette façon, la confidentialité des données est préservée, ainsi que l'anonymat de l'utilisateur, car un observateur tiers voit l'adresse IP du serveur VPN et non celle de l'utilisateur réel. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**Ce que fait AdGuard VPN :** +**What AdGuard VPN does:** -- cache votre localisation réelle et vous aide à rester anonyme -- change votre adresse IP pour protéger vos données contre le suivi -- chiffre votre trafic pour le rendre illisible par des tiers -- vous permet de configurer où utiliser le VPN et où ne pas l'utiliser (fonction d'exclusions) +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -Pour obtenir plus d'informations sur AdGuard VPN, consultez la [base de connaissances d'AdGuard VPN](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index d6c6e0c7e3a..f4dcbd52a31 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-------------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index d529f22fab9..d6f450188be 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Tartalomblokkoló][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:----------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index 34f88b58b6b..8210905bfe8 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ Per disabilitare la protezione, inserire: adguard-cli stop ``` -Questo comando non solo ferma il proxy ma ferma anche il traffico dal reindirizzare a esso. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Controlla lo stato della protezione @@ -45,45 +45,61 @@ adguard-cli status ![Stato/Ferma protezione \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) -## Aggiornamenti +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + +## Updates ### Controlla gli aggiornamenti -Per controllare gli aggiornamenti, inserisci: +To check for updates, enter: ```sh adguard-cli check-update ``` -### Aggiorna AdGuard per Linux +### Update AdGuard for Linux -Per aggiornare AdGuard per Linux, inserisci: +To update AdGuard for Linux, enter: ```sh adguard-cli update ``` -### Aggiorna il risultato del codice +### Update script output -Per vedere il risultato del codice di aggiornamento, inserisci: +To view the update script output, enter: ```sh adguard-cli update -v ``` -## Configura AdGuard per Linux +## Configure AdGuard for Linux + +Use the `config` command to configure AdGuard for Linux. Subcommands: -Usa il comando `config` per configurare AdGuard per Linux. Sotto-comandi: +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) -- `show`: Mostra la configurazione corrente in `proxy.yaml` + ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) - ![Impostazione corrente \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) +- `set `: Configure an option in `proxy.yaml` + - `listen_ports.http_proxy`: HTTP listening port + - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `set`: Configura un'opzione in `proxy.yaml` - - `listen_ports.http_proxy`: porta HTTP di ascolto - - `proxy_mode`: Modalità proxy (`manuale` o `automatico`) +- `get `: Get the current status of a setting -- `get`: Ottieni lo stato attuale delle opzioni soprastanti +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -96,40 +112,78 @@ The Automatic mode can only be used if the following requirements are met: ::: -## Gestisci i filtri +## Manage filters + +Use the `filters` command to configure AdGuard for Linux. Subcommands: + +- `list`: List installed and added filters + + - `--all`: View all filters + + ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) + +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter + + ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) + +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter -Usa il comando `filters` per configurare AdGuard per Linux. Sotto-comandi: +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). -- `list`: Elenca i filtri installati +## Manage DNS filters - - `--all`: Vedi tutti i filtri +Use the `dns filters` command to manage DNS filter lists. Subcommands: - ![Lista filtri \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter -- `install`: installa un filtro. Inserisci l'URL del filtro che desideri installare +DNS filter updates are handled by `adguard-cli check-update`. -- `enable`: Abilita un filtro. Inserisci il nome o l'ID del filtro +## Manage userscripts - ![Abilita filtri \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) +Use the `userscripts` command to manage userscripts. Subcommands: -- `disable`: disabilita un filtro. Inserisci il nome o l'ID del filtro +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update`: aggiorna i filtri +Userscripts are updated by `adguard-cli check-update`. -## Modifica dell'indirizzo di ascolto del server proxy in modalità proxy manuale +## Changing the proxy server listen address in manual proxy mode -Per impostazione predefinita, il server proxy ascolta su `127.0.0.1` — l'indirizzo dell'interfaccia di rete di loopback. -Ci sono due modi per far ascoltare il server prossimo su un'interfaccia diversa: +By default, the proxy server listens on `127.0.0.1` — the address of the loopback network interface. +There are two ways to make the proxy server listen on a different interface: -1. Esegui `adguard-cli config set listen_address
` dove `
` è l'indirizzo su cui ascoltare. -2. Modifica il file di configurazione direttamente: - - Per determinare il luogo del file di configurazione, esegui `adguard-cli config show | grep "Config location"`. - - Cerca la chiave `listen_address` e imposta il suo valore come desiderato. Per ascoltare su tutte le interfacce di rete disponibili, impostare l'indirizzo di ascolto come `0.0.0.0` o `::`. +1. Run `adguard-cli config set listen_address
` where `
` is the address to listen on. +2. Edit the config file directly: + - To determine the location of the config file, run `adguard-cli config show | grep "Config location"`. + - Look for the `listen_address` key and set its value accordingly. To listen on all available network interfaces, set the listen address to `0.0.0.0` or `::`. -Se l'indirizzo di ascolto è impostato su qualcosa di diverso da `127.0.0.1`, allora l'autenticazione del client proxy è obbligatoria. AdGuard CLI non si avvierà a meno che l'autenticazione del proxy non sia configurata: +If the listen address is set to anything other than `127.0.0.1`, then proxy client authentication is required. AdGuard CLI will not start unless proxy authentication is configured: -- Quando si esegue `adguard-cli config set listen_address
` dove `
` non è `127.0.0.1`, AdGuard CLI chiederà un nome utente e una parola d'accesso se l'autenticazione proxy non è già configurata. -- Quando si modifica il file di configurazione direttamente, cercare la chiave `listen_auth`. Imposta la sottochiave `enabled` su `true`, e `username` e `password` su valori non vuoti. +- When running `adguard-cli config set listen_address
` where `
` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured. +- When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values. ## Configure outbound proxy diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index f3ce40d1462..51e3136a1d8 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ Questo articolo riguarda AdGuard per Windows, un blocca-inserzioni multifunziona Il modulo _Rete_ è dedicato al filtraggio di rete e qui troverai le opzioni aggiuntive correlate alla rete. Due di esse sono abilitate come predefinite: _Abilita il filtraggio del traffico_ e _Filtra HTTPS_. Queste sono importanti precauzioni aggiuntive, per meglio filtrare il tuo spazio web. Gran parte dei siti, a oggi, usa HTTPS, il che si applica anche alle inserzioni. Da molti siti web, come youtube.com, facebook.com e x.com, è impossibile rimuovere le inserzioni senza il filtraggio HTTPS. Quindi, mantieni la funzione _Filtra HTTPS_ abilitata, a meno che tu non abbia una valida ragione per non farlo. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In questo modulo puoi selezionare la casella di controllo _Usa AdGuard come proxy HTTP_ per usare AdGuard come proxy HTTP regolare, che filtra tutto il traffico che lo attraversa. Inoltre, puoi abilitare la funzione _Filtra siti web con i certificati EV_. I certificati SSL a Validazione Estesa (EV) offrono una maggiore garanzia di sicurezza; i proprietari di tali siti web devono superare un duro processo di verifica dell'identità standardizzato e a livello globale, definito dalle linee guida EV. Per questo, alcuni utenti si fidano dei siti web con tali certificati e preferiscono non filtrarli. Infine, esiste una sezione con le impostazioni proxy. Lì, puoi specificare quale server proxy dovrebbe essere usato da AdGuard per aggiornare i filtri, ottenere le nuove versioni e così via. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -L'ultima sezione è dedicata ad AdGuard VPN: uno strumento ideale che fornisce sicurezza e anonimato ogni volta che navighi nella rete globale. Puoi scaricarla cliccando il pulsante _Scarica_ o visita il sito web di AdGuard VPN, cliccando il pulsante _Pagina iniziale_. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -Come funziona AdGuard VPN? Senza entrare nei dettagli tecnici, possiamo dire che la VPN crea un tunnel crittografato e sicuro tra il computer dell'utente o il dispositivo mobile e un server VPN remoto. Così, è preservata la riservatezza dei dati, nonché l'anonimato dell'utente, poiché un osservatore di terze parti vede l'indirizzo IP del server VPN e non l'effettivo IP dell'utente. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**Cosa fa AdGuard VPN:** +**What AdGuard VPN does:** -- nasconde la tua posizione reale e ti aiuta a rimanere anonimo -- modifica il tuo indirizzo IP per proteggere i tuoi dati dal tracciamento -- crittografa il tuo traffico per renderlo illeggibile a terze parti -- ti consente di configurare dove usare la VPN e dove no (funzionalità di esclusione) +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -Per ottenere ulteriori informazioni su AdGuard VPN, approfondisci nelle [Nozioni di base di AdGuard VPN](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 55ad294e819..0c7cc02480d 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard Mini per Mac][ext-saf] | [Blocco contenuti AdGuard][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:----------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index 437a856c74e..8067db0953c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ This command attempts to configure a redirection to the proxy. adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,11 +45,19 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### フィルタ更新を確認する -更新があるかどうかをチェックするには、以下を入力します： +To check for updates, enter: ```sh adguard-cli check-update @@ -57,7 +65,7 @@ adguard-cli check-update ### Update AdGuard for Linux -AdGuard for Linux をアップデートするには、以下を入力します： +To update AdGuard for Linux, enter: ```sh adguard-cli update @@ -65,25 +73,33 @@ adguard-cli update ### Update script output -更新スクリプトの出力を表示するには、以下を入力します： +To view the update script output, enter: ```sh adguard-cli update -v ``` -## AdGuard for Linux を設定する +## Configure AdGuard for Linux -AdGuard for Linuxを設定するには、`config` コマンドを使用します。 サブコマンドは以下のとおりです： +Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: `proxy.yaml` の現在の構成を表示する +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: `proxy.yaml` でオプションを設定する +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - - `proxy_mode`: プロキシモード（`manual`または`auto`） + - `proxy_mode`: Proxy mode (`manual` or `auto`) + +- `get `: Get the current status of a setting -- `get`: 上記オプションの現在の状態を取得する +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -96,25 +112,63 @@ The Automatic mode can only be used if the following requirements are met: ::: -## フィルターを管理する +## Manage filters -AdGuard for Linuxを設定するには、`filters` コマンドを使用します。 サブコマンドは以下のとおりです： +Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: インストールされているフィルタ一覧を表示する +- `list`: List installed and added filters - - `--all`: すべてのフィルタを表示 + - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: フィルタをインストールする （インストールしたいフィルタのURLを入力してください。） +- `add`: Add a built-in filter by ID or name -- `enable`: フィルタを有効にする （フィルタの名前またはIDを入力してください。） +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) -- `disable`: フィルタを無効にする （フィルタの名前またはIDを入力してください。） +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update`: フィルタを更新する +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index f1249c94791..78c85113b99 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ sidebar_position: 4 この「ネットワーク」モジュールはネットワークフィルタリング専用のもので、ネットワーク関連の追加オプションがあります。 このうち、「トラフィックフィルタリングを有効にする」と「HTTPS をフィルタリングする」は、デフォルトで有効になっています。 これらは、あなたのウェブスペースをより良くフィルタリングするための重要な追加予防措置です。 現在、ほとんどのウェブサイトがHTTPSを使用しており、広告も同様です。 youtube.com、facebook.com、x.comなど多くのウェブサイトでは、HTTPSフィルタリングなしでは広告を削除することができません。 そのため、特別な理由がない限り、「HTTPSをフィルタリングする」機能は有効にしておいてください。 -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) このモジュールでは、「HTTPプロキシとしてAdGuardを使用する」チェックボックスをオンにすると、AdGuardを通常のHTTPプロキシとして使用し、通過するすべてのトラフィックをフィルタリングできます。 「EV証明書を持つウェブサイトをフィルタリング」オプションを有効にすることもできます。 EV (Extended Validation) SSL証明書は、ウェブサイトの所有者がEVガイドラインで定義されている国際標準化された徹底的な身元確認プロセスに合格したことを保証します。 これは、このような証明書を持つウェブサイトを信頼してフィルタリングをしないようなユーザーがいる理由でもあります。 最後に、プロキシ設定のセクションがあります。 そこで、AdGuard がフィルタの更新や新バージョンの取得などに使用するプロキシサーバーを指定できます。 +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -最後のセクションは AdGuard VPN に関するものです。AdGuard VPN は、インターネットを閲覧するたびにセキュリティと匿名性を提供する理想的なツールです。 「ダウンロード」ボタンをクリックしてダウンロードするか、「ホームページ」ボタンをクリックして AdGuard VPN のウェブサイトにアクセスしてください。 +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -そもそも、AdGuard VPN の仕組みは何なのか？ 技術的な詳細は省きますが、VPNは、ユーザーのコンピュータまたはモバイル端末とリモートVPNサーバーの間に安全な暗号化トンネルを作成すると言えます。 これにより、データと個人情報のプライバシーが保たれるだけでなく、オンライン上の第三者にはユーザーの実際のIPではなく、VPNサーバーのIPアドレスが見えるので、ユーザーの位置情報も隠されます。 +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**AdGuard VPN の機能:** +**What AdGuard VPN does:** -- あなたの本当の居場所を隠し、匿名性を保てるようにします。 -- IPアドレスを変更することで、トラッキングからデータ・個人情報を保護します。 -- トラフィック（通信）を暗号化し、詐欺師やハッカーが通信内容にアクセスできないようにします。 -- VPNを使用するとしない場所を設定できます（「VPN対象外リスト「機能） +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -AdGuard VPN についての詳しい情報は、[AdGuard VPN ナレッジベース](https://adguard-vpn.com/kb/)をご覧ください。 +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 8502b646ee6..6648bb74ae2 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md index 1d74b5b9a3f..ad43e710171 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md @@ -15,7 +15,7 @@ AdGuard가 Firefox에서 HTTPS 트래픽을 성공적으로 필터링하기 위 :::note -이 방법은 Firefox Nightly 90.0a1 이상 버전에서만 사용될 수 있습니다. Firefox의 베타 및 일반 버전이 v90에 도달하면 이 방법을 해당 버전에도 적용할 수 있습니다. +이 방법은 Android용 Firefox 90.0 이상 버전에서 사용할 수 있습니다. ::: diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index ec9f795ffbb..c0795e54641 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ adguard-cli start adguard-cli stop ``` -이 명령은 프록시를 중지할 뿐만 아니라 트래픽이 프록시로 리디렉션되는 것도 중지합니다. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### 보호 상태 확인 @@ -45,45 +45,61 @@ adguard-cli status ![상태/보호 중지 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) -## 업데이트 +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + +## Updates ### 업데이트 확인 -업데이트를 확인하려면 다음을 입력합니다. +To check for updates, enter: ```sh adguard-cli check-update ``` -### Linux용 AdGuard 업데이트 +### Update AdGuard for Linux -Linux용 AdGuard를 업데이트하려면 다음을 입력합니다. +To update AdGuard for Linux, enter: ```sh adguard-cli update ``` -### 스크립트 출력 업데이트 +### Update script output -업데이트 스크립트 출력을 보려면 다음을 입력합니다. +To view the update script output, enter: ```sh adguard-cli update -v ``` -## Linux용 AdGuard 구성 +## Configure AdGuard for Linux + +Use the `config` command to configure AdGuard for Linux. Subcommands: -`config` 명령을 사용하여 Linux용 AdGuard를 구성합니다. 하위 명령: +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) -- `show`: `proxy.yaml`의 현재 설정 표시 + ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) - ![현재 설정 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) +- `set `: Configure an option in `proxy.yaml` + - `listen_ports.http_proxy`: HTTP listening port + - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `set`: `proxy.yaml`에서 옵션 설정 - - `listen_ports.http_proxy`: HTTP 수신 포트 - - `proxy_mode`: 프록시 모드(`manual` 또는 `auto`) +- `get `: Get the current status of a setting -- `get`: 위 옵션의 현재 상태 확인 +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -96,40 +112,78 @@ The Automatic mode can only be used if the following requirements are met: ::: -## 필터 관리 +## Manage filters + +Use the `filters` command to configure AdGuard for Linux. Subcommands: + +- `list`: List installed and added filters + + - `--all`: View all filters + + ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) + +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter + + ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) + +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter -`filters` 명령을 사용하여 Linux용 AdGuard를 구성합니다. 하위 명령: +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). -- `list`: 설치된 필터 목록 +## Manage DNS filters - - `--all`: 모든 필터 보기 +Use the `dns filters` command to manage DNS filter lists. Subcommands: - ![필터 목록 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter -- `install`: 필터 설치 설치하려는 필터의 URL을 입력합니다. +DNS filter updates are handled by `adguard-cli check-update`. -- `enable`: 필터 활성화 필터의 이름이나 ID를 입력합니다. +## Manage userscripts - ![필터 활성화 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) +Use the `userscripts` command to manage userscripts. Subcommands: -- `disable`: 필터 비활성화 필터의 이름이나 ID를 입력합니다. +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update`: 필터 업데이트 +Userscripts are updated by `adguard-cli check-update`. -## 수동 프록시 모드에서 프록시 서버 수신 주소 변경 +## Changing the proxy server listen address in manual proxy mode -기본적으로 프록시 서버는 `127.0.0.1`(루프백 네트워크 인터페이스 주소)를 감시합니다. -프록시 서버가 다른 인터페이스를 감시하도록 설정할 수 있습니다. 두 가지 방법이 있습니다. +By default, the proxy server listens on `127.0.0.1` — the address of the loopback network interface. +There are two ways to make the proxy server listen on a different interface: -1. `adguard-cli config set listen_address
` 명령어를 실행하세요. 여기서 `
`는 감시할 주소입니다. -2. 구성 파일을 직접 편집합니다. - - 구성 파일의 위치를 확인하려면 `adguard-cli config show | grep "Config location"`를 실행합니다. - - `listen_address` 키를 찾아서 그에 맞는 값을 설정합니다. 사용 가능한 모든 네트워크 인터페이스에서 수신하려면 수신 주소를 `0.0.0.0` 또는 `::`으로 설정합니다. +1. Run `adguard-cli config set listen_address
` where `
` is the address to listen on. +2. Edit the config file directly: + - To determine the location of the config file, run `adguard-cli config show | grep "Config location"`. + - Look for the `listen_address` key and set its value accordingly. To listen on all available network interfaces, set the listen address to `0.0.0.0` or `::`. -수신 주소가 `127.0.0.1`이 아닌 다른 주소로 설정된 경우 프록시 클라이언트 인증이 필요합니다. 프록시 인증이 구성되지 않으면 AdGuard CLI가 시작되지 않습니다. +If the listen address is set to anything other than `127.0.0.1`, then proxy client authentication is required. AdGuard CLI will not start unless proxy authentication is configured: -- `adguard-cli config set listen_address
`를 실행할 때 `
`가 127.0.0.1이 아닌 경우, AdGuard CLI는 프로xy 인증이 아직 설정되지 않았다면 사용자 이름과 비밀번호를 요청합니다. -- 구성 파일을 직접 편집할 때는 `listen_auth` 키를 찾습니다. `enabled` 하위 키를 `true`로 설정하고, `username`과 `password`를 비어 있지 않은 값으로 설정합니다. +- When running `adguard-cli config set listen_address
` where `
` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured. +- When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values. ## Configure outbound proxy diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index b3fed38586a..776a2a38c0e 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ sidebar_position: 4 네트워크\* 모듈은 네트워크 필터링 전용 모듈로, 여기에서 네트워크 관련 추가 옵션을 찾을 수 있습니다. 이 중 두 가지(**트래픽 필터링 활성화** 및 **HTTPS 프로토콜 필터링**)는 기본적으로 활성화되어 있습니다. 이는 웹 공간을 더 잘 필터링하기 위한 중요한 추가 예방 조치입니다. 대부분의 웹 사이트와 광고 네트워크는 현재 HTTPS를 사용하고 있습니다. youtube.com, facebook.com, x.com과 같은 많은 웹사이트에서 HTTPS 필터링 없이는 광고를 제거하는 것이 불가능합니다. 따라서 **HTTPS 프로토콜 필터링** 기능을 사용하도록 설정하는 것이 좋습니다. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) 이 모듈에서 **AdGuard를 HTTP 프록시로 사용** 확인란을 선택하면 AdGuard를 통과하는 모든 트래픽을 필터링하는 일반 HTTP 프록시로 사용할 수 있습니다. **EV 인증서가 있는 웹사이트를 필터링** 기능을 활성화할 수도 있습니다. EV(Extended Validation) SSL 인증서는 더 강력한 안전 보장을 제공하며, 해당 웹사이트 소유자는 EV 가이드라인에 정의된 철저하고 전 세계적으로 표준화된 신원 확인 프로세스를 통과해야 합니다. 그렇기 때문에 일부 사용자는 이러한 인증서가 있는 사이트를 신뢰하고 필터링하지 않기로 선택합니다. 마지막으로 프록시 설정 섹션이 있습니다. 여기에서 필터 업데이트, 새 버전 가져오기 등에 AdGuard가 사용할 프록시 서버를 지정할 수 있습니다. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -마지막 섹션에서는 인터넷 서핑 시 보안과 익명성을 제공하는 도구인 AdGuard VPN을 소개합니다. AdGuard VPN을 다운로드하려면 **다운로드** 버튼을 클릭하거나 **홈페이지** 버튼을 클릭하여 공식 웹사이트로 이동하세요. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -AdGuard VPN은 어떻게 작동하나요? VPN은 사용자의 컴퓨터 또는 모바일 기기와 원격 VPN 서버 사이에 암호화된 보안 터널을 생성합니다. 따라서 실제 사용자 IP가 아닌 VPN 서버의 IP 주소가 표시되기 때문에 데이터 기밀성과 사용자 익명성이 유지됩니다. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**AdGuard VPN의 기능:** +**What AdGuard VPN does:** -- 실제 위치를 숨기고 익명성을 유지합니다. -- 추적기로부터 데이터를 보호하기 위해 IP 주소를 변경합니다. -- 트래픽을 암호화하여 제3자가 읽을 수 없도록 합니다. -- VPN을 사용하는 사이트와 사용하지 않는 사이트를 구성할 수 있습니다 (예외 목록). +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -AdGuard VPN에 대한 자세한 내용은 [AdGuard VPN 지식 창고](https://adguard-vpn.com/kb/)를 참조하세요. +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index e8161707dad..44daf9d6f16 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index 52c87cd34ae..99e1a2e1f68 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ Para desativar a proteção, digite: adguard-cli stop ``` -Este comando não apenas interrompe o proxy, mas também impede o tráfego de ser redirecionado para ele. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Verificar status da proteção @@ -45,45 +45,61 @@ adguard-cli status ![Status/Parar proteção \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) -## Atualizações +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + +## Updates ### Verificar atualizações -Para verificar se há atualizações, digite: +To check for updates, enter: ```sh adguard-cli check-update ``` -### Atualizar o AdGuard para Linux +### Update AdGuard for Linux -Para atualizar o AdGuard para Linux, digite: +To update AdGuard for Linux, enter: ```sh adguard-cli update ``` -### Atualizar saída do script +### Update script output -Para visualizar o output do script de atualização, digite: +To view the update script output, enter: ```sh adguard-cli update -v ``` -## Configurando o AdGuard para Linux +## Configure AdGuard for Linux + +Use the `config` command to configure AdGuard for Linux. Subcommands: -Use o comando `config` para configurar o AdGuard para Linux. Subcomandos: +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) -- `show`: Mostra a configuração atual em `proxy.yaml` + ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) - ![Configuração atual \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) +- `set `: Configure an option in `proxy.yaml` + - `listen_ports.http_proxy`: HTTP listening port + - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `set`: Configura uma opção em `proxy.yaml` - - `listen_ports.http_proxy`: Porta de escuta HTTP - - `proxy_mode`: Modo de proxy (`manual` ou `auto`) +- `get `: Get the current status of a setting -- `get`: Obtém o status atual das opções acima +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -96,40 +112,78 @@ The Automatic mode can only be used if the following requirements are met: ::: -## Gerenciamento de filtros +## Manage filters + +Use the `filters` command to configure AdGuard for Linux. Subcommands: + +- `list`: List installed and added filters + + - `--all`: View all filters + + ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) + +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter + + ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) + +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter -Use o comando `filters` para configurar o AdGuard para Linux. Subcomandos: +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). -- `list`: Listar filtros instalados +## Manage DNS filters - - `--all`: Ver todos os filtros +Use the `dns filters` command to manage DNS filter lists. Subcommands: - ![Lista de filtros \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter -- `instalar`: Instalar um filtro. Digite a URL da filtragem que você deseja instalar +DNS filter updates are handled by `adguard-cli check-update`. -- `enable`: Ativa um filtro. Digite o nome ou ID do filtro +## Manage userscripts - ![Ativar filtros \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) +Use the `userscripts` command to manage userscripts. Subcommands: -- `disable`: Desabilita um filtro. Digite o nome ou ID do filtro +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update`: Atualiza os filtros +Userscripts are updated by `adguard-cli check-update`. -## Alterando o endereço de escuta do proxy no modo manual +## Changing the proxy server listen address in manual proxy mode -Por padrão, o servidor do proxy escuta em `127.0.0.1` — o endereço da interface de rede de loopback. -Existem duas maneiras de fazer o proxy ouvir em uma interface diferente: +By default, the proxy server listens on `127.0.0.1` — the address of the loopback network interface. +There are two ways to make the proxy server listen on a different interface: -1. Execute `adguard-cli config set listen_address ` onde `` é o endereço para escutar. -2. Editar o arquivo de configuração diretamente: - - Para determinar a localização do arquivo de configuração, execute `adguard-cli config show | grep "Config location"`. - - Procure a chave `listen_address` e defina seu valor adequadamente. Para escutar em todas as interfaces de rede disponíveis, defina o endereço de escuta como `0.0.0.0` ou `::`. +1. Run `adguard-cli config set listen_address
` where `
` is the address to listen on. +2. Edit the config file directly: + - To determine the location of the config file, run `adguard-cli config show | grep "Config location"`. + - Look for the `listen_address` key and set its value accordingly. To listen on all available network interfaces, set the listen address to `0.0.0.0` or `::`. -Se o endereço de escuta estiver definido para qualquer coisa diferente de `127.0.0.1`, então a autenticação do cliente proxy é obrigatória. O AdGuard CLI não será iniciado, a menos que a autenticação do proxy esteja configurada: +If the listen address is set to anything other than `127.0.0.1`, then proxy client authentication is required. AdGuard CLI will not start unless proxy authentication is configured: -- Ao executar `adguard-cli config set listen_address
` onde `
` não é `127.0.0.1`, o AdGuard CLI solicitará um nome de usuário e uma senha se a autenticação do proxy não estiver configurada. -- Ao editar o arquivo de configuração diretamente, procure pela chave `listen_auth`. Defina a sub-chave `enabled` como `true`, e `username` e `password` como valores não vazios. +- When running `adguard-cli config set listen_address
` where `
` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured. +- When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values. ## Configure outbound proxy diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 37ff9e1a2ae..23859d3cce0 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ Este artigo aborda o AdGuard para Windows, um bloqueador de anúncios multifunci O módulo _Rede_ é dedicado à filtragem de rede, e aqui você encontrará opções adicionais relacionadas à rede. Dois deles estão habilitados por padrão: _Habilitar filtragem de tráfego_ e _Filtrar HTTPS_. Estas são precauções extras importantes para filtrar melhor o seu espaço web. A maioria dos sites agora usa HTTPS, e o mesmo se aplica à publicidade. Em muitos sites, como youtube.com, facebook.com e x.com, é impossível excluir anúncios sem Filtragem HTTPS. Portanto, mantenha o recurso _Filtrar HTTPS_ ativado, a menos que você tenha um bom motivo para não fazê-lo. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) Neste módulo você pode selecionar a caixa de verificação _Usar AdGuard como proxy HTTP_ para usar o AdGuard como um proxy HTTP regular que filtrará todo o tráfego que passa por ele. Você também pode ativar o recurso _Filtrar sites com certificados EV_. Os certificados SSL de validação estendida (EV) oferecem uma garantia de segurança mais forte; os proprietários de tais sites devem passar por um processo de verificação de identidade completo e padronizado globalmente, definido pelas diretrizes de EV. É por isso que alguns usuários confiam em sites com esses certificados e preferem não filtrá-los. Por fim, há uma seção com configurações de proxy. Lá você pode especificar qual servidor proxy o AdGuard deve usar para atualizar filtros, obter novas versões e assim por diante. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -A última seção é dedicada ao AdGuard VPN — uma ferramenta ideal que oferece segurança e anonimato sempre que você navega na Internet. Você pode baixá-lo clicando no botão _Download_ ou acessando o site do AdGuard VPN clicando no botão _Homepage_. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -Como funciona o AdGuard VPN? Sem entrar em detalhes técnicos, podemos dizer que a VPN cria um túnel criptografado seguro entre o computador ou dispositivo móvel do usuário e um servidor VPN remoto. Desta forma, a privacidade dos dados é preservada, bem como o anonimato do usuário, porque um observador terceiro vê o endereço IP do servidor VPN e não o IP real do usuário. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**O que o AdGuard VPN faz:** +**What AdGuard VPN does:** -- esconde sua localização real e ajuda você a permanecer anônimo -- altera seu endereço IP para proteger seus dados contra rastreamento -- criptografa seu tráfego para torná-lo ilegível para terceiros -- permite que você configure onde usar e onde não usar a VPN (recurso de exclusões) +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -Para obter mais informações sobre o AdGuard VPN, acesse a [base de conhecimento do AdGuard VPN](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 474f9ecc049..de391502c64 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ Os seguintes modificadores são os mais simples e frequentemente usados. Basicam | Modificador \ Produtos | [Aplicativos do CoreLibs][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-------------------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index e31dfa934e8..4291a773b47 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ Este artigo aborda o AdGuard para Windows, um bloqueador de anúncios multifunci The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 934a67af490..29137651e53 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index d8c0cd83bbe..ad67f7e1641 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Căutare actualizări @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index d734e647eea..9f66682d0f4 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ Acest articol se referă la AdGuard pentru Windows, un blocant de reclame multif Modulul _Rețea_ este dedicat filtrării rețelei, și aici veți găsi opțiuni suplimentare legate de rețea. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Acestea sunt măsuri suplimentare importante pentru a filtra mai bine spațiul dumneavoastră web. Majoritatea site-urilor web folosesc acum HTTPS, iar același lucru se aplică și publicității. De pe multe site-uri, cum ar fi youtube.com, facebook.com și x.com, este imposibil să ștergeți reclamele fără filtrarea HTTPS. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) În acest modul, puteți selecta caseta de bifat _Utilizați AdGuard ca proxy HTTP_ pentru a folosi AdGuard ca un proxy HTTP obișnuit care va filtra tot traficul care trece prin el. De asemenea, puteți activa funcția _Filtrare site-uri cu certificate EV_. Certificatele SSL Validare Extinsă (EV) oferă o garanție mai bună; proprietarii acestor site-uri trebuie să treacă printr-un proces riguros și standardizat la nivel global de verificare a identității definit în liniile directoare EV. Care este motivul pentru care unii utilizatori au încredere în site-urile cu astfel de certificate și preferă să nu le filtreze. În cele din urmă, există o secțiune dedicată setărilor proxy. Acolo puteți specifica ce server proxy ar trebui să folosească AdGuard pentru a actualiza filtrele, a obține versiunile noi și așa mai departe. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -Ultima secțiune este dedicată AdGuard VPN - un instrument ideal care oferă securitate și anonimat de fiecare dată când răsfoiți Internetul. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -Cum funcționează AdGuard VPN? Fără a intra în detalii tehnice, putem spune că VPN creează un tunel securizat criptat între computerul utilizatorului sau aparatul mobil și un server VPN la distanță. În acest mod, intimitatea datelor este păstrată, la fel ca și anonimatul utilizatorului, deoarece un observator terț vede adresa IP a serverului VPN și nu adresa IP reală a utilizatorului. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**Ce poate face AdGuard VPN:** +**What AdGuard VPN does:** -- ascunde unde te afli cu adevărat și te ajută să rămâi anonim -- îți schimbă adresa IP pentru a-ți proteja datele de monitorizare -- criptează traficul pentru a-l face ilizibil pentru terți +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties - lets you configure where to use VPN and where not to (exclusions feature) -Pentru a obține mai multe informații despre AdGuard VPN, adânciți-vă în [Baza de cunoștințe AdGuard VPN](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 7119b9733d7..b7ad8fbf956 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ Următoarele modificatoare sunt cele mai simple și utilizate frecvent. Basicall | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Exemplu: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index c4756f9e86b..20503cc0c6f 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ adguard-cli start adguard-cli stop ``` -Эта команда не только останавливает работу прокси-сервера, но и прекращает перенаправление трафика на него. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Проверить статус защиты @@ -45,45 +45,61 @@ adguard-cli status ![Статус/Отключить защиту \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) -## Обновления +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + +## Updates ### Проверить обновления -Чтобы проверить наличие обновлений, введите: +To check for updates, enter: ```sh adguard-cli check-update ``` -### Обновление AdGuard для Linux +### Update AdGuard for Linux -Чтобы обновить AdGuard для Linux, введите: +To update AdGuard for Linux, enter: ```sh adguard-cli update ``` -### Вывод скрипта обновления +### Update script output -Чтобы просмотреть вывод скрипта обновления, введите: +To view the update script output, enter: ```sh adguard-cli update -v ``` -## Настройте AdGuard для Linux +## Configure AdGuard for Linux + +Use the `config` command to configure AdGuard for Linux. Subcommands: -Используйте команду `config` для настройки AdGuard для Linux. Подкоманды: +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) -- `show`: показать текущую конфигурацию в `proxy.yaml` + ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) - ![Текущая настройка \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) +- `set `: Configure an option in `proxy.yaml` + - `listen_ports.http_proxy`: HTTP listening port + - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `set`: настроить параметр в `proxy.yaml` - - `listen_ports.http_proxy`: порт прослушивания HTTP - - `proxy_mode`: режим прокси-сервера (`manual` или `auto`) +- `get `: Get the current status of a setting -- `get`: получить текущий статус указанных выше опций +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -96,50 +112,88 @@ The Automatic mode can only be used if the following requirements are met: ::: -## Управлять фильтрами +## Manage filters + +Use the `filters` command to configure AdGuard for Linux. Subcommands: + +- `list`: List installed and added filters + + - `--all`: View all filters + + ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) + +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter + + ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) + +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter -Используйте команду `filters` для настройки AdGuard для Linux. Подкоманды: +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). -- `list`: список установленных фильтров +## Manage DNS filters - - `--all`: просмотреть все фильтры +Use the `dns filters` command to manage DNS filter lists. Subcommands: - ![Список фильтров \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter -- `install`: установить фильтр. Введите URL-адрес фильтра, который хотите установить +DNS filter updates are handled by `adguard-cli check-update`. -- `enable`: включить фильтр. Введите имя или ID фильтра +## Manage userscripts - ![Включить фильтры \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) +Use the `userscripts` command to manage userscripts. Subcommands: -- `disable`: отключить фильтр. Введите имя или ID фильтра +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update`: обновить фильтры +Userscripts are updated by `adguard-cli check-update`. -## Изменение адреса прослушивания прокси-сервера в режиме ручной настройки прокси +## Changing the proxy server listen address in manual proxy mode -По умолчанию прокси-сервер прослушивает `127.0.0.1` — адрес сетевого интерфейса loopback. -Можно сделать так, чтобы прокси-сервер слушал другой интерфейс. Есть два способа: +By default, the proxy server listens on `127.0.0.1` — the address of the loopback network interface. +There are two ways to make the proxy server listen on a different interface: -1. Выполните команду `adguard-cli config set listen_address
`, где `
` — адрес для прослушивания. -2. Отредактируйте файл конфигурации напрямую: - - Чтобы определить местоположение файла конфигурации, выполните команду `adguard-cli config show | grep "Config location"`. - - Найдите ключ `listen_address` и установите его значение соответствующим образом. Чтобы прослушивать все доступные сетевые интерфейсы, установите значение `0.0.0.0` или `::` для адреса прослушивания. +1. Run `adguard-cli config set listen_address
` where `
` is the address to listen on. +2. Edit the config file directly: + - To determine the location of the config file, run `adguard-cli config show | grep "Config location"`. + - Look for the `listen_address` key and set its value accordingly. To listen on all available network interfaces, set the listen address to `0.0.0.0` or `::`. -Если в качестве адреса прослушивания задано значение, отличное от `127.0.0.1`, — требуется аутентификация прокси-клиента. AdGuard CLI не запустится, если не настроена аутентификация прокси: +If the listen address is set to anything other than `127.0.0.1`, then proxy client authentication is required. AdGuard CLI will not start unless proxy authentication is configured: -- При запуске `adguard-cli config set listen_address
`, где `
` не 127.0.0.1, AdGuard CLI запросит имя пользователя и пароль, если прокси-аутентификация ещё не настроена. -- При редактировании файла конфигурации напрямую найдите ключ `listen_auth`. Установите для подключа `enabled` значение `true`, а для `username` и `password` \` — непустые значения. +- When running `adguard-cli config set listen_address
` where `
` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured. +- When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values. -## Настроить исходящий прокси +## Configure outbound proxy -Вы можете настроить `outbound_proxy`, если хотите, чтобы AdGuard CLI работал через другой прокси-сервер. +You can configure `outbound_proxy` if you want AdGuard CLI to work through another proxy server. -Есть два способа настройки: +There are two ways to configure it: -### 1. Настроить через URL (рекомендуется) +### 1. Configure via URL (recommended) -Вместо того чтобы настраивать каждую опцию пошагово, вы можете задать все параметры в одной строке, используя URL: +Instead of setting each option step by step, you can set all parameters in a single line using a URL: ```sh adguard-cli config set outbound_proxy https://user:pass@host:port @@ -147,25 +201,25 @@ adguard-cli config set outbound_proxy https://user:pass@host:port :::info -Поддерживаемые режимы: HTTP, HTTPS, SOCKS, и SOCKS5. +Supported modes are HTTP, HTTPS, SOCKS4, and SOCKS5. ::: -Вы также можете быстро включить или отключить `outbound_proxy`: +You can also quickly enable or disable `outbound_proxy`: ```sh adguard-cli config set outbound_proxy false ``` -Или быстро очистить настройки: +Or quickly clear the settings: ```sh adguard-cli config set outbound_proxy "" ``` -### 2. Настроить отдельные параметры +### 2. Configure individual parameters -Также есть возможность настроить отдельные параметры: +The ability to adjust specific parameters is also available: ```sh adguard-cli config set outbound_proxy.enabled true @@ -175,13 +229,13 @@ adguard-cli config set outbound_proxy.username user adguard-cli config set outbound_proxy.password pass ``` -Отключить проверку сертификата для HTTPS-прокси: +Disable certificate verification for HTTPS proxies: ```sh adguard-cli config set outbound_proxy.trust_any_certificate true ``` -Включить прокси SOCKS5 для UDP-трафика: +Enable SOCKS5 proxy for UDP traffic: ```sh adguard-cli config set outbound_proxy.udp_through_socks5_enabled true @@ -189,21 +243,21 @@ adguard-cli config set outbound_proxy.udp_through_socks5_enabled true :::note -Если ваш прокси SOCKS5 не поддерживает UDP, соединения могут не работать. +If your SOCKS5 proxy does not support UDP, connections may fail. ::: -## Настройка AdGuard CLI для каждого приложения +## Per-app AdGuard CLI configuration -Пользователям часто приходится вручную включать фильтрацию для определённых браузеров. AdGuard для Linux поддерживает **конфигурацию для каждого приложения**, позволяя применять настройки или правила индивидуально к каждому приложению, а не ко всей системе. +Users often need to enable filtering manually for certain browsers. AdGuard for Linux supports **per-app configuration**, allowing you to apply settings or rules individually to each application instead of system-wide. -За подробностями обратитесь к разделу `apps` в файле `proxy.yaml`. +For details, refer to the `apps` section in `proxy.yaml`. -Набор преднастроенных записей для популярных интернет-браузеров включён в файл `browsers.yaml` по умолчанию. +A set of pre-configured entries for popular web browsers is included by default in `browsers.yaml`. -### Проверка текущей конфигурации +### Checking the current configuration -Чтобы просмотреть текущую конфигурацию `outbound_proxy`, введите: +To view the current `outbound_proxy` configuration, enter: ```sh adguard-cli config show outbound_proxy @@ -211,7 +265,7 @@ adguard-cli config show outbound_proxy :::info Совместимость -Настройка `outbound_proxy` через URL доступна, начиная с AdGuard для Linux 1.1.26 nightly и стабильной версии 1.1. +Configuring `outbound_proxy` via URL is available starting from AdGuard for Linux v1.1.26 nightly and v1.1 stable release. ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index fe9cf5dc101..cb6b98101bb 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ sidebar_position: 4 Модуль _Сеть_ посвящён сетевой фильтрации, и здесь вы найдёте дополнительные параметры, связанные с сетью. Два из них включены по умолчанию: _Включить фильтрацию трафика_ и _Фильтровать HTTPS_. Это важная дополнительная мера предосторожности для лучшей фильтрации интернет-пространства. Большинство сайтов теперь используют HTTPS, то же самое относится и к рекламным сетям. На многих сайтах, таких как youtube.com, facebook.com и x.com, невозможно заблокировать рекламу без HTTPS-фильтрации. Поэтому оставьте функцию _Фильтровать HTTPS_ включённой, если у вас нет веской причины не делать этого. -![Настройки сети \*mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) В этом модуле вы можете установить флажок «Использовать AdGuard как HTTP-прокси», чтобы использовать AdGuard в качестве обычного HTTP-прокси, который будет фильтровать весь проходящий через него трафик. Вы также можете включить функцию _Фильтровать сайты с EV-сертификатами_. EV-сертификаты (от англ. Extended Validation — «расширенная валидация») дают более надёжную гарантию; владельцы таких сайтов должны пройти подробный и всемирно стандартизированный процесс проверки личности, определённый руководящими принципами EV. Именно поэтому некоторые пользователи доверяют сайтам с такими сертификатами и предпочитают не фильтровать их. Наконец, есть раздел с настройками прокси. Там вы можете указать, какой прокси-сервер AdGuard должен использовать для обновления фильтров или получения новых версий. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -Последний раздел посвящён AdGuard VPN — идеальному инструменту, обеспечивающему безопасность и анонимность каждый раз, когда вы выходите в интернет. Вы можете скачать его, нажав на кнопку _Скачать_, или перейти на сайт AdGuard VPN, нажав на кнопку _Сайт_. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -Как работает AdGuard VPN? VPN создаёт безопасный зашифрованный туннель между компьютером или мобильным устройством пользователя и удалённым VPN-сервером. Таким образом, сохраняется конфиденциальность данных и анонимность пользователя, поскольку сторонний наблюдатель видит IP-адрес VPN-сервера, а не фактический IP-адрес пользователя. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**Что делает AdGuard VPN:** +**What AdGuard VPN does:** -- скрывает ваше реальное местоположение и помогает оставаться анонимными -- изменяет ваш IP-адрес, чтобы защитить данные от отслеживания -- шифрует ваш трафик, делая его недоступным для третьих сторон -- позволяет настроить, где использовать VPN, а где нет (функция исключений) +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -Чтобы получить больше информации об AdGuard VPN, ознакомьтесь [с Базой знаний AdGuard VPN](https://adguard-vpn.com/kb/). +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 80da7aa2e0d..75ec5cdfbed 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ Wildcard-символы поддерживаются для TLD-доменов | Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard для Chrome MV3][ext-mv3] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,7 +2670,8 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Регулярные выражения, отрицание и правила белого списка не поддерживаются. -- Группа похожих правил `$removeparam` будет объединена в одно. Пример: +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. +- Group of similar `$removeparam` rules will be combined into one. Пример: ```bash ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index 1970730029c..e74fedc55bd 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ Korumayı devre dışı bırakmak için şunu yazın: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,11 +45,19 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) -## Güncellemeler +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + +## Updates ### Güncellemeleri denetleyin -Güncellemeleri denetlemek için şunu yazın: +To check for updates, enter: ```sh adguard-cli check-update @@ -57,7 +65,7 @@ adguard-cli check-update ### Update AdGuard for Linux -Linux için AdGuard'ı güncellemek için şunu yazın: +To update AdGuard for Linux, enter: ```sh adguard-cli update @@ -71,19 +79,27 @@ To view the update script output, enter: adguard-cli update -v ``` -## Linux için AdGuard'ı yapılandırma +## Configure AdGuard for Linux -Linux için AdGuard'ı yapılandırmak için `config` komutunu kullanın. Alt komutlar: +Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -98,23 +114,61 @@ The Automatic mode can only be used if the following requirements are met: ## Manage filters -Use the `filters` command to configure AdGuard for Linux. Alt komutlar: +Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Yüklemek istediğiniz filtrenin URL'sini girin +- `add`: Add a built-in filter by ID or name -- `enable`: Enable a filter. Filtrenin adını veya kimliğini girin +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) -- `disable`: Disable a filter. Filtrenin adını veya kimliğini girin +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update`: Update filters +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode @@ -122,8 +176,8 @@ By default, the proxy server listens on `127.0.0.1` — the address of the loopb There are two ways to make the proxy server listen on a different interface: 1. Run `adguard-cli config set listen_address
` where `
` is the address to listen on. -2. Yapılandırma dosyasını doğrudan düzenleyin: - - Yapılandırma dosyasının konumunu belirlemek için `adguard-cli config show | grep "Config location"` komutunu çalıştırın. +2. Edit the config file directly: + - To determine the location of the config file, run `adguard-cli config show | grep "Config location"`. - Look for the `listen_address` key and set its value accordingly. To listen on all available network interfaces, set the listen address to `0.0.0.0` or `::`. If the listen address is set to anything other than `127.0.0.1`, then proxy client authentication is required. AdGuard CLI will not start unless proxy authentication is configured: @@ -131,7 +185,7 @@ If the listen address is set to anything other than `127.0.0.1`, then proxy clie - When running `adguard-cli config set listen_address
` where `
` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured. - When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values. -## Giden proxy'yi yapılandırma +## Configure outbound proxy You can configure `outbound_proxy` if you want AdGuard CLI to work through another proxy server. @@ -147,7 +201,7 @@ adguard-cli config set outbound_proxy https://user:pass@host:port :::info -Desteklenen modlar HTTP, HTTPS, SOCKS4 ve SOCKS5'tir. +Supported modes are HTTP, HTTPS, SOCKS4, and SOCKS5. ::: @@ -157,13 +211,13 @@ You can also quickly enable or disable `outbound_proxy`: adguard-cli config set outbound_proxy false ``` -Veya ayarları hızlıca temizleyin: +Or quickly clear the settings: ```sh adguard-cli config set outbound_proxy "" ``` -### 2. Bireysel parametreleri yapılandırma +### 2. Configure individual parameters The ability to adjust specific parameters is also available: @@ -175,13 +229,13 @@ adguard-cli config set outbound_proxy.username user adguard-cli config set outbound_proxy.password pass ``` -HTTPS proxy'leri için sertifika doğrulamayı devre dışı bırakın: +Disable certificate verification for HTTPS proxies: ```sh adguard-cli config set outbound_proxy.trust_any_certificate true ``` -UDP trafiği için SOCKS5 proxy'sini etkinleştirin: +Enable SOCKS5 proxy for UDP traffic: ```sh adguard-cli config set outbound_proxy.udp_through_socks5_enabled true @@ -189,15 +243,15 @@ adguard-cli config set outbound_proxy.udp_through_socks5_enabled true :::note -SOCKS5 proxy'niz UDP'yi desteklemiyorsa, bağlantılar başarısız olabilir. +If your SOCKS5 proxy does not support UDP, connections may fail. ::: -## Uygulama başına AdGuard CLI yapılandırması +## Per-app AdGuard CLI configuration -Kullanıcıların genellikle belirli tarayıcılar için filtrelemeyi elle etkinleştirmesi gerekir. Linux için AdGuard, **uygulama başına yapılandırmayı** destekleyerek ayarları veya kuralları sistem genelinde uygulamak yerine her uygulamaya ayrı ayrı uygulamanıza olanak tanır. +Users often need to enable filtering manually for certain browsers. AdGuard for Linux supports **per-app configuration**, allowing you to apply settings or rules individually to each application instead of system-wide. -Ayrıntılar için `proxy.yaml` dosyasındaki `apps` bölümüne bakın. +For details, refer to the `apps` section in `proxy.yaml`. A set of pre-configured entries for popular web browsers is included by default in `browsers.yaml`. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index b176431d11c..d7168b75558 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ Bu makale, cihazınızı sistem düzeyinde koruyan çok işlevli bir reklam enge _Ağ_ modülü ağ filtrelemeye ayrılmıştır ve burada ağla ilgili ek seçenekler bulacaksınız. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Bunlar, web alanınızı daha iyi filtrelemek için önemli olağanüstü önlemlerdir. Çoğu site artık HTTPS kullanıyor ve aynı durum reklamcılık için de geçerli. Youtube.com, facebook.com ve x.com gibi birçok siteden HTTPS filtreleme olmadan reklamları kaldırmak imkansızdır. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. Ayrıca _EV sertifikalarına sahip siteleri filtrele_ özelliğini de etkinleştirebilirsiniz. Genişletilmiş Doğrulama (EV) SSL Sertifikaları daha güçlü bir güvenlik garantisi sunar; bu tür sitelerin sahipleri EV yönergeleri tarafından tanımlanan kapsamlı ve küresel olarak standartlaştırılmış bir kimlik doğrulama sürecinden geçmek zorundadır. Bazı kullanıcıların bu tür sertifikalara sahip sitelere güvenmelerinin ve bunları filtrelememeyi tercih etmelerinin nedeni budur. Son olarak, proxy ayarlarının bulunduğu bir bölüm vardır. Burada, filtreleri güncellemek, yeni sürümleri edinmek, vb. için AdGuard'ın hangi proxy sunucusunu kullanması gerektiğini belirleyebilirsiniz. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -Son bölüm, internette her gezindiğinizde güvenlik ve anonimlik sağlayan ideal bir araç olan AdGuard VPN'e ayrılmıştır. _İndir_ düğmesine tıklayarak indirebilir veya _Ana Sayfa_ düğmesine tıklayarak AdGuard VPN sitesine gidebilirsiniz. +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -AdGuard VPN nasıl çalışır? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**AdGuard VPN ne yapar:** +**What AdGuard VPN does:** -- gerçek yerinizi gizler ve anonim kalmanıza yardımcı olur -- verilerinizi izlemekten korumak için IP adresinizi değiştirir +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking - encrypts your traffic to make it unreadable to third parties -- VPN'nin nerede kullanılacağını ve nerede kullanılmayacağını yapılandırmanıza olanak tanır (istisnalar özelliği) +- lets you configure where to use VPN and where not to (exclusions feature) To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index e5c82a3254a..0d23304528a 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Temel olarak, s | Modifier \ Products | [CoreLibs apps][cl-apps] | [Chromium için AdGuard][ext-chr] | [Chrome MV3 için AdGuard][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:------------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Örnek: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index 7c18d7ee900..4427a12fc0b 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ adguard-cli start adguard-cli stop ``` -此命令不仅停用代理，而且还停止流量重定向到代理。 +This command not only stops the proxy but also stops the traffic from redirecting to it. ### 检查保护状态 @@ -45,45 +45,61 @@ adguard-cli status ![状态/停用保护 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) -## 更新 +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + +## Updates ### 检查更新 -要检查更新，请输入以下命令： +To check for updates, enter: ```sh adguard-cli check-update ``` -### 更新 AdGuard Linux 版 +### Update AdGuard for Linux -要更新 Linux 版 AdGuard，请输入以下命令： +To update AdGuard for Linux, enter: ```sh adguard-cli update ``` -### 更新脚本输出 +### Update script output -要查看更新脚本的输出，请输入以下命令： +To view the update script output, enter: ```sh adguard-cli update -v ``` -## 配置 AdGuard Linux 版 +## Configure AdGuard for Linux + +Use the `config` command to configure AdGuard for Linux. Subcommands: -使用 `config` 命令配置 Linux 版 AdGuard。 子命令： +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) -- `show`：显示 `proxy.yaml` 中的当前配置 + ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) - ![当前设置 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) +- `set `: Configure an option in `proxy.yaml` + - `listen_ports.http_proxy`: HTTP listening port + - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `set`：在 `proxy.yaml` 中配置选项 - - `listen_ports.http_proxy`：HTTP 协议监听端口 - - `proxy_mode`：代理模式（`manual` 或 `auto`) +- `get `: Get the current status of a setting -- `get`：获取上述选项的当前状态 +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -96,40 +112,78 @@ The Automatic mode can only be used if the following requirements are met: ::: -## 管理过滤器 +## Manage filters + +Use the `filters` command to configure AdGuard for Linux. Subcommands: + +- `list`: List installed and added filters + + - `--all`: View all filters + + ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) + +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter + +- `enable`: Enable a filter. Enter the name or ID of the filter + + ![Enable filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) + +- `disable`: Disable a filter. Enter the name or ID of the filter + +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter -使用 `filters` 命令配置 Linux 版 AdGuard。 子命令： +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). -- `list`：列出已安装的过滤器 +## Manage DNS filters - - `--all`：查看所有过滤器 +Use the `dns filters` command to manage DNS filter lists. Subcommands: - ![过滤列表 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter -- `install`：安装过滤器。 请输入您要安装的过滤器 URL +DNS filter updates are handled by `adguard-cli check-update`. -- `enable`：启用过滤器。 输入过滤器的名称或 ID +## Manage userscripts - ![启用过滤器 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/built-in-filters.png) +Use the `userscripts` command to manage userscripts. Subcommands: -- `disable`：禁用过滤器。 输入过滤器的名称或 ID +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript -- `update`：更新过滤器 +Userscripts are updated by `adguard-cli check-update`. -## 在手动代理模式下更改代理服务器监听地址 +## Changing the proxy server listen address in manual proxy mode -默认情况下，代理服务器监听 `127.0.0.1`（循环网络接口的地址）。 -有两种方法可以让代理在不同的界面上侦听： +By default, the proxy server listens on `127.0.0.1` — the address of the loopback network interface. +There are two ways to make the proxy server listen on a different interface: -1. 运行 `adguard-cli config set listen_address
`，其中`
` 是要监听的地址。 -2. 编辑配置文件： - - 要确定配置文件的位置，请运行 `adguard-cli config show | grep "Config location"`。 - - 查找 `listen_address` 键并相应设置其值。 要在所有可用网络接口上监听，请将监听地址设置为 `0.0.0.0` 或 `::`。 +1. Run `adguard-cli config set listen_address
` where `
` is the address to listen on. +2. Edit the config file directly: + - To determine the location of the config file, run `adguard-cli config show | grep "Config location"`. + - Look for the `listen_address` key and set its value accordingly. To listen on all available network interfaces, set the listen address to `0.0.0.0` or `::`. -若监听地址设置为除 `127.0.0.1` 之外的任何值，则需启用代理客户端认证。 AdGuard CLI 不会启动，除非配置代理认证： +If the listen address is set to anything other than `127.0.0.1`, then proxy client authentication is required. AdGuard CLI will not start unless proxy authentication is configured: -- 当执行 `adguard-cli config set listen_address
` 且 `
` 不为 `127.0.0.1` 时，若未配置代理认证，AdGuard CLI 将提示输入用户名和密码。 -- 编辑配置文件时，请查找 `listen_auth` 键。 将 `enabled` 子键设置为 `true`，并将 `username` 和 `password` 设置为非空值。 +- When running `adguard-cli config set listen_address
` where `
` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured. +- When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values. ## Configure outbound proxy diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 2b96c9de9e7..15c804ac7c9 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,23 +11,41 @@ sidebar_position: 4 「_网络_」模块专用于网络过滤，用户可以找到其他与网络相关的选项。 其中两项默认启动：「开启流量过滤」和「过滤 HTTPS」。 这都是重要的额外预防措施，可以更好地过滤网络空间。 当前大部分网站使用 HTTPS，广告亦是如此。 在许多网站上，例如 youtube.com、facebook.com 和 x.com，如果没有 HTTPS 过滤就无法删除广告。 因此除非用户有充分的理由不开启它，否则请保持开启「过滤 HTTPS」功能。 -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) 用户也可选中此模块内的复选框「AdGuard 用作 HTTP 代理」以将 AdGuard 用作常规的 HTTP 代理过滤经由它的所有流量。 用户还可以开启「用 EV 证书过滤网站」功能。 扩展验证（EV）SSL 证书提供更强大的安全保障；此类网站的所有者必须通过 EV 指南定义的彻底的全球标准化身份验证过程。 这就是一些用户信任具有此类证书的网站并且不愿过滤它们的原因。 最后是代理设置部分。 用户可以在此处指定 AdGuard 更新过滤器，获取新版本等所用的代理服务器。 +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN -最后一部分专门介绍 AdGuard VPN。这是一个理想的工具，用户在每次上网时都能享受安全性和匿名性。 点击「_下载_」按钮进行下载，或者点击「_主页_」按钮访问 AdGuard VPN 网站。 +The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. -AdGuard VPN 工作原理是什么？ 在不讨论技术细节的情况下，可以说 VPN 在用户的计算机或移动设备与远程 VPN 服务器之间创建一个安全的加密隧道。 通过这种方式，数据隐私得以保护，同时用户的匿名性也得以维持，因为第三方观察者只能看到 VPN 服务器的 IP 地址，而非用户的真实 IP 地址。 +How does AdGuard VPN work? Without going into technical details, we can say that VPN creates a secure encrypted tunnel between the user's computer or mobile device and a remote VPN server. In this way, data privacy is preserved, as well as the anonymity of the user, because a third-party observer sees the IP address of the VPN server and not the actual user's IP. -**AdGuard VPN 能做什么：** +**What AdGuard VPN does:** -- 隐藏用户的真实位置帮助保持匿名性 -- 更改用户的 IP 地址避免他人跟踪个人数据 -- 加密用户的流量防止第三方访问个人数据 -- 让用户自己配置在哪里启用或禁用 VPN（排除项功能） +- hides your real whereabouts and helps you stay anonymous +- changes your IP address to protect your data from tracking +- encrypts your traffic to make it unreadable to third parties +- lets you configure where to use VPN and where not to (exclusions feature) -要了解更多关于 AdGuard VPN 的信息，请转到 [AdGuard VPN 知识库](https://adguard-vpn.com/kb/)。 +To get more information about AdGuard VPN, dive into the [AdGuard VPN Knowledge Base](https://adguard-vpn.com/kb/). diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 43564b58708..bc07f9458e1 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard 内容拦截器][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-----------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md new file mode 100644 index 00000000000..d1e6bdd8101 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/ads-not-blocked-in-opera.md @@ -0,0 +1,15 @@ +--- +title: Ad blocking issues on search websites in Opera +sidebar_position: 3 +--- + +If AdGuard Browser Extension fails to block ads on search websites in Opera, either automatically or manually, it means that the extension does not have permission to access search page results. + +To grant the required permission: + +![Allow access to search page results](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/allow-access.png) + +1. Click the cube icon next to the address bar → _Manage extensions..._. +2. Find AdGuard AdBlocker in the list of installed extensions and tick the box next to _Allow access to search page results_. + +Once this is done, ads on search websites will be blocked as expected. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md index dc7c082af51..8825926086f 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md @@ -33,7 +33,7 @@ To disable protection, enter: adguard-cli stop ``` -This command not only stops the proxy but also stops the trafic from redirecting to it. +This command not only stops the proxy but also stops the traffic from redirecting to it. ### Check protection status @@ -45,6 +45,14 @@ adguard-cli status ![Status/Stop protection \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png) +### Restart protection + +To restart the proxy server and reapply settings, enter: + +```sh +adguard-cli restart +``` + ## Updates ### Check for updates @@ -75,15 +83,23 @@ adguard-cli update -v Use the `config` command to configure AdGuard for Linux. Subcommands: -- `show`: Show the current configuration in `proxy.yaml` +- `show []`: Show the current configuration in `proxy.yaml` (or a specific section) ![Current setup \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png) -- `set`: Configure an option in `proxy.yaml` +- `set `: Configure an option in `proxy.yaml` - `listen_ports.http_proxy`: HTTP listening port - `proxy_mode`: Proxy mode (`manual` or `auto`) -- `get`: Get the current status of the above options +- `get `: Get the current status of a setting + +- `list-add [...]`: Add one or more values to a list setting + +- `list-remove `: Remove a value from a list setting + +- `reset `: Reset a setting to its default value + +- `reset --all`: Reset all settings to their default values :::note @@ -100,13 +116,17 @@ The Automatic mode can only be used if the following requirements are met: Use the `filters` command to configure AdGuard for Linux. Subcommands: -- `list`: List installed filters +- `list`: List installed and added filters - `--all`: View all filters ![Filter list \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/filter-list.png) -- `install`: Install a filter. Enter the URL of the filter you want to install +- `add`: Add a built-in filter by ID or name + +- `install`: Install a filter. Enter the URL of the filter you want to install or local file + - `--trusted`: Mark the custom filter as trusted + - `--title`: Set a custom title for the filter - `enable`: Enable a filter. Enter the name or ID of the filter @@ -114,7 +134,41 @@ Use the `filters` command to configure AdGuard for Linux. Subcommands: - `disable`: Disable a filter. Enter the name or ID of the filter -- `update`: Update filters +- `remove`: Remove an internal or custom filter by ID + +- `set-trusted`: Mark a custom filter as trusted or untrusted + +- `set-title`: Set a custom title for a custom filter + +Filter updates are handled by `adguard-cli check-update` (the `filters update` subcommand forwards to it). + +## Manage DNS filters + +Use the `dns filters` command to manage DNS filter lists. Subcommands: + +- `list`: List installed and added DNS filters + - `--all`: View all DNS filters +- `add`: Add a built-in DNS filter by ID or name +- `install`: Install a custom DNS filter from a URL or local file + - `--title`: Set a custom title for the filter +- `enable`: Enable a DNS filter. Enter the name or ID of the filter +- `disable`: Disable a DNS filter. Enter the name or ID of the filter +- `remove`: Remove a DNS filter by ID +- `set-title`: Set a custom title for a DNS filter + +DNS filter updates are handled by `adguard-cli check-update`. + +## Manage userscripts + +Use the `userscripts` command to manage userscripts. Subcommands: + +- `list`: Show installed userscripts +- `install`: Install a userscript from a URL +- `remove`: Remove a userscript +- `enable`: Enable a userscript +- `disable`: Disable a userscript + +Userscripts are updated by `adguard-cli check-update`. ## Changing the proxy server listen address in manual proxy mode diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md index 54bcb9787c7..5945618ea9c 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/network.md @@ -11,12 +11,30 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote The _Network_ module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many websites, like youtube.com, facebook.com, and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. -![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings.png) +![Network Settings \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/network/network_settings_2.png) In this module you can select the checkbox _Use AdGuard as an HTTP proxy_ to use AdGuard as a regular HTTP proxy which will filter all traffic passing through it. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL Certificates offer a stronger safety guarantee; owners of such websites have to pass a thorough and globally standardized identity verification process defined by EV guidelines. Which is the reason why some users trust websites with such certificates and prefer not to filter them. At last, there is a section with proxy settings. There you can specify which proxy server AdGuard should use to update filters, get new versions, and so on. +### SockFilter and other network drivers + +In _Network_, you can also enable traffic filtering and choose which driver to use: SockFilter, WFP, or TDI. + +**WFP** (Windows Filtering Platform) is a powerful driver, but it may present stability risks, such as [occasional system crashes (BSOD)](https://github.com/AdguardTeam/AdguardForWindows/issues/5792) for some users. + +The **TDI** driver is also available, but it is outdated and may cause [filtering issues in some versions of Google Chrome](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). [A temporary workaround exists](https://adguard.com/kb/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142/), but it’s not a reliable long-term solution. + +**SockFilter** is an _experimental_, lightweight kernel-mode network driver that works at the socket level (TCP/UDP). Instead of inspecting or modifying packets as they travel through the full Windows networking stack, a sock filter intercepts socket calls (e.g., connect, send, receive, bind) at a higher, more stable abstraction level. This makes it ideal for applications that need to monitor or control network activity without deep packet processing. + +Currently, SockFilter Right is still unstable, and you may encounter bugs. When fully tested and implemented, SockFilter has the potential to bring several advantages over other drivers: + +- **It operates at a higher, socket-level layer**: SockFilter works with socket operations rather than raw packets, making it less complex and more stable than WFP's low-level packet filtering. +- **No interference with other network drivers**: Because it sits above VPN, firewall, and antivirus WFP filters, it avoids filter-ordering problems and compatibility conflicts common in the WFP stack. +- **Greatly reduced risk of NETIO-related BSODs**: SockFilter doesn't run inside the NETIO packet pipeline, so it avoids the typical crash scenarios caused by WFP callouts mishandling buffers, classification results, or packet memory. + +When it comes to disadvantages, SockFilter driver sees only socket-level operations and does not capture traffic generated by other kernel drivers or components that bypass the standard Winsock API. From a low-level networking perspective, this can be viewed as a limitation, since the driver cannot access raw packets or inspect non-socket traffic. However, for an ad-blocking application, this behavior is not just acceptable but optimal. All relevant traffic from browsers and user-mode applications goes through standard sockets, and that's exactly what we need to control. At the same time, ignoring low-level driver traffic removes unnecessary complexity, avoids compatibility issues, and keeps the system stable. + ### AdGuard VPN The last section is dedicated to AdGuard VPN — an ideal tool that provides security and anonymity each time you browse the Internet. You can download it by clicking the _Download_ button or go to the AdGuard VPN website by clicking the _Homepage_ button. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 750e1d3a216..85a494bad91 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -389,7 +389,7 @@ The following modifiers are the most simple and frequently used. Basically, they | Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard Mini for Mac][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | | [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | | [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | | [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -579,7 +579,7 @@ In the following examples it is implied that requests are sent from `http://exam :::caution Limitations -In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries are not supported. +In [AdGuard for Chrome MV3][ext-mv3], `regexp` and `any_tld_domain` entries and the `$removeparam` modifier are not supported. AdGuard for iOS and AdGuard for Safari support the `$domain` modifier but have some limitations. For more details, see the [SafariConverterLib section](#safari-converter--basic--supported-with-limitations). @@ -2670,6 +2670,7 @@ With these rules, specified UTM parameters will be removed from any request save [AdGuard for Chrome MV3][ext-mv3] has some limitations: - Regular expressions, negation and allowlist rules are not supported. +- Generic rules are applied before specific rules, and redirection occurs only once. This may prevent subsequent or more specific redirects from applying. - Group of similar `$removeparam` rules will be combined into one. Example: ```bash @@ -2737,6 +2738,7 @@ With these rules, specified UTM parameters will be removed from any request save 1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). 1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Although `$domain` is classified as a basic modifier, it's not compatible with `$removeparam` rules in the Manifest V3 extension. 1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. :::