Add description for "Filter HTTP/3" in AdGuard for Android #301
Conversation
sonya-orlova
commented
Sep 4, 2023
sonya-orlova
commented
- Small fix to "Log removed HTML events"
+ Small fix to "Log removed HTML events"
| @@ -35,7 +35,7 @@ Here you can list domains that will be forwarded directly to fallback upstreams | |||
|
|
|||
| #### Detect search domains | |||
|
|
|||
| If this option is enabled, AdGuard will detect search domains and automatically forward them to fallback upstreams. | |||
| This option makes AdGuard detect search domains and automatically forward them to fallback upstreams. | |||
There was a problem hiding this comment.
If this is enabled, AdGuard will detect search domains and automatically forward them to fallback upstreams.
| @@ -72,33 +72,33 @@ Here you can specify the maximum number of cached responses. Default value is 10 | |||
|
|
|||
| #### ECH blocking | |||
|
|
|||
| If enabled, AdGuard strips Encrypted Client Hello parameters from DNS responses. | |||
| This option makes AdGuard strip Encrypted Client Hello parameters from DNS responses. | |||
There was a problem hiding this comment.
If this is enabled, AdGuard will strip Encrypted Client Hello parameters from DNS responses.
|
|
||
| #### Ignore unavailable outbound proxy | ||
|
|
||
| Enable this feature to make AdGuard send DNS requests directly if the outbound proxy is unavailable. | ||
| This option makes AdGuard send DNS requests directly if the outbound proxy is unavailable. |
There was a problem hiding this comment.
If this is enabled, AdGuard will send DNS requests directly when the outbound proxy is unavailable.
|
|
||
| #### Try HTTP/3 for DNS-over-HTTPS upstreams | ||
|
|
||
| By default, all DNS requests for DNS-over-HTTPS are sent via HTTP/2 protocol. If enabled, AdGuard uses HTTP/3 to speed up DNS query resolution for DoH upstreams. | ||
| By default, all DNS requests for DNS-over-HTTPS are sent via HTTP/2 protocol. This option makes AdGuard use HTTP/3 to speed up DNS query resolution for DoH upstreams. |
There was a problem hiding this comment.
If this is enabled, AdGuard will use HTTP/3 to speed up DNS query resolution for DoH upstreams.
Otherwise, AdGuard will revert to its default behavior and use HTTP/2 to send all DNS requests for DNS-over-HTTPS.
|
|
||
| #### SERVFAIL failure response | ||
|
|
||
| Once enabled, AdGuard sends a SERVFAIL response to the client if all upstreams, including fallback ones, fail to reply. When this setting is disabled, no response is sent to the client. | ||
| This option makes AdGuard send a SERVFAIL response to the client if all upstreams, including fallback ones, fail to reply. When this setting is disabled, no response is sent to the client. |
There was a problem hiding this comment.
If this is enabled, AdGuard will send a SERVFAIL response to the client if all upstreams, including fallback ones, fail to reply. When this setting is disabled, no response is sent to the client.
|
|
||
| #### Packet capture (PCAP) | ||
|
|
||
| If enabled, AdGuard will create the special file name `timestamp.pcap` (for instance, 1682599851461.pcap). It contains all network packets transferred through the VPN. This file is located in the app cache directory and can be analyzed with the Wireshark program. | ||
| This option makes AdGuard create a file `timestamp.pcap` (for instance, 1682599851461.pcap) that lists all network packets transferred through the VPN and is located in the app cache directory. This file can be analyzed with the Wireshark program. |
There was a problem hiding this comment.
If this is enabled, AdGuard will create a file timestamp.pcap (for instance, 1682599851461.pcap) in the app cache directory. This file lists all network packets transferred through the VPN and can be analyzed with the Wireshark program.
|
|
||
| #### Include Wi-Fi gateway in VPN routes | ||
|
|
||
| If you want the gateway IP addresses to be added to VPN routes when on Wi-Fi, enable this feature. | ||
| This option adds the gateway IP addresses to VPN routes when on Wi-Fi. |
There was a problem hiding this comment.
If this is enabled, the gateway IP addresses will be added to to VPN routes when on Wi-Fi.
|
|
||
| #### IPv4 address | ||
|
|
||
| Here you can enter the IP address that will be used to create a TUN interface. By default, it is `172.18.11.218`. | ||
|
|
||
| #### Forcibly route LAN IPv4 | ||
|
|
||
| When enabled, AdGuard filters all LAN connections, including local IPv4 network traffic, even if the *Route all LAN IPv4 connections* option is enabled. | ||
| This option makes AdGuard filter all LAN connections, including local IPv4 network traffic, even if the *Route all LAN IPv4 connections* option is enabled. |
There was a problem hiding this comment.
If this is enabled, AdGuard will filter all LAN connections, including local IPv4 network traffic, even if the Route all LAN IPv4 connections option is enabled.
|
|
||
| #### Route all LAN IPv4 connections | ||
|
|
||
| Once enabled, AdGuard excludes LAN connections from filtering for simple networks. May not work for complex networks. Works only with the *Forcibly route LAN IPv4* option disabled. | ||
| This option makes AdGuard exclude LAN connections from filtering for simple networks. May not work for complex networks. Works only with the *Forcibly route LAN IPv4* option disabled. |
There was a problem hiding this comment.
If this is enabled, AdGuard will exclude LAN connections from filtering for simple networks. This may not work for complex networks. This setting only applies if Forcibly route LAN IPv4 is disabled.
| @@ -214,4 +218,4 @@ Here you can enter the IP address that will be used to create a TUN interface. B | |||
|
|
|||
| #### Detect Samsung Pay | |||
|
|
|||
| Korean users may encounter issues with Samsung Pay when AdGuard is enabled. Activate this feature to pause AdGuard's protection and use the Samsung Pay app seamlessly. | |||
| Korean users may encounter issues with Samsung Pay when AdGuard is enabled. This option pauses AdGuard's protection while Samsung Pay is used. | |||
There was a problem hiding this comment.
If this is enabled, AdGuard protection will be paused while Samsung Pay is in use. Some of our users require this feature as they experience issues with Samsung Pay when AdGuard is enabled.
|
These suggestions will be addressed in the next pull request |
Suggested changes from #301 plus one link
