Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disconnecting from Ethernet while your Mac is in sleep mode results in AdGuard being unable to filter local content #599

Closed
dnovitskyi opened this issue Sep 26, 2019 · 6 comments

Comments

@dnovitskyi
Copy link

Steps to reproduce

  1. use a wired Ethernet network connection
  2. activate the sleep mode of your Macintosh
  3. remove the Ethernet cable from your Macintosh
  4. wake your Macintosh up from sleep
  5. after five seconds connect the Ethernet cable again to the computer
  6. open local pages
  7. the error with AdGuard for Mac should appear

Expected behavior

AdGuard should filter local content without depending on internet connection

Actual behavior

Filtering breaks

Screenshot: Certificate

Customer ID

2250582

Your environment

  • Environment name and version: (e.g. Chrome 59): macOS Mojave, Google Chrome
  • Any specific potentially conflicting software installed: (e.g. antiviruses, firewalls, traffic counters, cleaners) none detected
@Stillness-2
Copy link
Member

Stillness-2 commented Sep 26, 2019

@akmLaVx At this point AdGuard doesn't filter any local network traffic by default. I don't understand how it filtered before disconnecting the ethernet. :)

@nexttoyou
Copy link

@akmLaVx At this point AdGuard doesn't filter any local network traffic by default. I don't understand how it filtered before disconnecting the ethernet. :)

That’s a quite theoretical question. As it just happens as described, the answer most probably would be that while AdGuard might not filter local connections specifically it is still acting on a networking level, otherwise it could not work system wide at all.

Besides this, are you using link aggregation or an ethernet interface via Thunderbolt? If not, you most probably will never have the problem described.

@ameshkov
Copy link
Member

ameshkov commented Oct 6, 2019

@Stillness-2 "local" is not about "localhost", this is just a local network connection

@ameshkov ameshkov added this to the 2.3 milestone Oct 6, 2019
@stale
Copy link

stale bot commented Dec 5, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Wontfix label Dec 5, 2019
@ameshkov ameshkov removed this from the 2.4 milestone Apr 27, 2020
@adguard-bot adguard-bot added this to the 2.4 milestone Apr 27, 2020
@ameshkov
Copy link
Member

The issue will go away with release 2.5 anyway as we're going to start using NetworkExtensions instead of kernel extensions

@nexttoyou
Copy link

Sigh … Well, it even happens here with using a standard Ethernet connection (instead of slower link aggregations via Thunderbolt etc.) after sleep/wake up. As we have a dual stack connection (fixed IPv4 and IPv6 addresses) I already deactivated IPv6 entirely because I found out that after changing from IPv4 to IPv6 (seems to happen automatically from time to time) this also renders AdGuard non-functional. So switching it off and on again (™ "The IT Crowd") looks like my destiny for some more time. Quite surprisingly this never ever happened with Little Snitch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants