Jump to content

"Compilation Of Tutorials, Guides, Tips & Updates"


dcs18

Recommended Posts

55 minutes ago, dcs18 said:

The actual reason why Simple DNSCrypt blocks blacklisted IDM domains before Windows Firewall Control (WFC) and even ahead of AdGuard, is the fact that it operates at a level deeper than either Windows Firewall Control (WFC) or AdGuardSimple DNSCrypt is present right at the very entry-point of the Network Adapter. 8)

 

Yep, by default SImpleDNSCrypt is monitoring the port responsible for dns requests(53) by monitoring process svchost.exe

AdGuard by default doesn't monitor that process.

So, a true comparison would involve filtering svchost through AdGuard and then seeing who blocks it first. :naughty:

Link to comment
Share on other sites


  • Replies 7.3k
  • Views 1.1m
  • Created
  • Last Reply
1 minute ago, Undertaker said:
59 minutes ago, dcs18 said:

The actual reason why Simple DNSCrypt blocks blacklisted IDM domains before Windows Firewall Control (WFC) and even ahead of AdGuard, is the fact that it operates at a level deeper than either Windows Firewall Control (WFC) or AdGuardSimple DNSCrypt is present right at the very entry-point of the Network Adapter. 8)

Yep, by default SImpleDNSCrypt is monitoring the port responsible for dns requests(53) by monitoring process svchost.exe

AdGuard by default doesn't monitor that process.

So, a true comparison would involve filtering svchost through AdGuard and then seeing who blocks it first. :naughty:

Although have had no time to audit either Simple DNSCrypt or svchost requests — have found the following ports (in toto) being monitored, so far:—

 

53
443
553
1053
2053
4434
5353

Link to comment
Share on other sites


It basically monitors port # 53 and upon failing to gain access for whatever be the reason, it pings the next port for availability . . . . . which in my personal opinion is not a bad idea since unless it gains access the internet connectivity is blocked, in any form (on the affected computer.)

Link to comment
Share on other sites


4 hours ago, dcs18 said:

It basically monitors port # 53 and upon failing to gain access for whatever be the reason, it pings the next port for availability . . . . . which in my personal opinion is not a bad idea since unless it gains access the internet connectivity is blocked, in any form (on the affected computer.)

That is strange because the parent program(the command line dnscrypt-proxy) is able to achieve this without any other port requirement(except ofc the default port 53). :think:

 

@vhick What is the IP range you want to block and for which program/app it is?

Link to comment
Share on other sites


Can someone confirm whether AdGuard is able to block itself from calling home using the following rule—

 

194.177.22.245^$network,important,app=AdguardSvc.exe

Link to comment
Share on other sites


43 minutes ago, dcs18 said:

Can someone confirm whether AdGuard is able to block itself from calling home using the following rule—

You can't filter AdGuard files/processes.

Link to comment
Share on other sites


knowledge-Spammer
5 hours ago, dcs18 said:

Can someone confirm whether AdGuard is able to block itself from calling home using the following rule—

 

194.177.22.245^$network,important,app=AdguardSvc.exe

But can block with firewaĺl i think

 

3 hours ago, dcs18 said:

Bloody scoundrels — wasted my time. 0pk6YBv.gif

No wasted time u have Learn

Link to comment
Share on other sites


On 2/24/2018 at 11:44 AM, dcs18 said:

The IP Address Tabs on the all-new Simple DNSCrypt are present but greyed out — looks as though they're being re-coded, as well.

The IP Address Tabs aren't available on the latest Simple DNSCrypt 0.5.2 either.

Link to comment
Share on other sites


On 2/24/2018 at 1:22 PM, Undertaker said:

Ain't that too many allowed? Why is DNSCryt even monitoring them? :eek:

Here's the reason:—

 

cEdqauD.png

Link to comment
Share on other sites


17 minutes ago, knowledge said:

8.20406  were is

 

Below : ;)

 

 

Link to comment
Share on other sites


44 minutes ago, knowledge said:

but on site it did say 8.20406  is missing ? were is 406 ?

 

 

LzgNgkF.png

Link to comment
Share on other sites


knowledge-Spammer

Maybe i miss see things i was sure was 406 but maybe i no see right  i was use tablet  my mistake  sorry

Link to comment
Share on other sites


On 9/25/2017 at 10:47 AM, Undertaker said:
On 9/25/2017 at 10:28 AM, Undertaker said:

In the meanwhile, have paired Acrylic DNS proxy with Dnscrypt-proxy for my system.

While earlier, SimpleDNScrypt was giving me ping times in excess of 80 ms; using DNScrypt-proxy(BikinHappy Singapore server) with Acrylic DNS proxy on my 1 Mbps connection(after FUP), the result are as follows:-

 

zyVzbw9.png

 

After playing around with Simple DNSCrypt, decide to combine it with Acrylic DNS Proxy — but, did not find any gains in ping times.

 

The Developers seem to have made improvements in Simple DNSCrypt's own DNS caching. yXZVmpE.gif

 

PmhrtgC.png

Link to comment
Share on other sites


3 hours ago, dcs18 said:

The Developers seem to have made improvements in Simple DNSCrypt's own DNS caching. yXZVmpE.gif

Yep DNSCrypt v2's DNS caching mechanism is at par with Acrylic DNS Proxy.

 

3 hours ago, dcs18 said:

After playing around with Simple DNSCrypt, decide to combine it with Acrylic DNS Proxy — but, did not find any gains in ping times.

How exactly did you set it up this combo? AFAIK, it's not possible to use the combo of Simple DNScrypt with Acrylic DNS Proxy.

 

 

Here's how my DNSCrypt-proxy paired with Acrylic DNS Proxy performed:-

 

https://i.imgur.com/ogSeePU.png

Link to comment
Share on other sites


I combined Acrylic DNS Proxy first with Simple DNSCrypt, on port # 53 and then on port # 40 — the combination worked on both the ports but on port # 40, I lost the full capabilities of Simple DNSCrypt.

Link to comment
Share on other sites


That is not how it works out.

How do you know the combination was working? The mere running of services(of both the program) is not an indication.

My guess is when you used the combo on port 53, only Simple DNSCrypt was working although Acrylic service maybe running in background and when you shifted to port 40(because Simple DNScrypt can't use local address:port), it failed.

Link to comment
Share on other sites


6 hours ago, Undertaker said:

How do you know the combination was working?

Due to my relatively higher internet speed my tests were not targeted toward Acrylic DNS Proxy as was my concern for traffic encryption with Simple DNSCrypt. ;)

Link to comment
Share on other sites


9 hours ago, dcs18 said:

my tests were not targeted toward Acrylic DNS Proxy

I don't quite understand the purpose of installing Acrylic then?

Because neither were your test targeted towards it nor the combo setup?

Link to comment
Share on other sites


  • Matrix locked this topic

Archived

This topic is now archived and is closed to further replies.

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...