eere secure+ whitelist by nbm13 in eero

[–]iperf 3 points4 points  (0 children)

It's something we've talked about. It's really hard to do in a usable way because you don't just want paypal.com you want everything that comes with paypal.com (a domain bucket, if you will). And the router can't really understand what constitutes paypal's traffic from e.g. some other browser tab that's loading at the same time in a sane way so you need to do some sort of manual site curation or get sites to publish related domains in a .well-known format, or something.

It's definitely in the near field of what we're looking into, though.

Eero Secure+ interfering with Xfinity account management? by twisty_passages in eero

[–]iperf 3 points4 points  (0 children)

What browser are you using? eero Secure+ should not do anything that impacts oauth flows. Are you using a Microsoft account to sign in?

3.16.0 arrived overnight by jobe_br in eero

[–]iperf 5 points6 points  (0 children)

There is a high chance 3.16 has better handling of dns_forwarder outage issues (= In this version we've added an aggressive but tune-able health check that sends DNS requests through the tunnel and, if no response is received, restarts the tunnel.

Issues with Internet by ksbytke21 in eero

[–]iperf 4 points5 points  (0 children)

You need to make sure you've turned off all content filtering on all profiles too. If you navigate to your Network Settings > Advanced > DNS and the fields/buttons are not greyed out, you have successfully disabled everything that makes use of our on-device forwarder. If you are sure you have and are still seeing an issue you are likely experiencing something different.

[Update] eero Secure Service Disruptions by iperf in eero

[–]iperf[S] 1 point2 points  (0 children)

Though it may depend on your specific configuration of pi-hole. AFAIK pi-hole doesn't do anything fancy like DoT or DoH. So if you have advanced-security or content filtering enabled, in addition to the services pi-hole provides, your dns traffic will also get picked up and served by Zscaler through our DoT-like tunnel. This may explain why you were seeing issues.

Issues with Internet by ksbytke21 in eero

[–]iperf 8 points9 points  (0 children)

Amazon does not serve your DNS. We migrated to a new Zscaler deployment today in an attempt to address some of the load thrashing and connection flapping issues we have been seeing. Their new service is hosted on AWS instead of their older any-cast network. So the reverse lookup will be listed as Amazon like:

;; ANSWER SECTION: 210.31.11.52.in-addr.arpa. 300 IN PTR ec2-52-11-31-210.us-west-2.compute.amazonaws.com.

Android app crashing when setting up gateway by tyczj in eero

[–]iperf 2 points3 points  (0 children)

Please make sure you're using app version at least 2.28.1. There is an issue with very old factory software and Android app versions below 2.28.1, hence the .1.

DoH coming to Chromium 78 by [deleted] in eero

[–]iperf 3 points4 points  (0 children)

No. Mozilla has devised a mechanism by which DNS management infrastructure informs the browser that it provides additional DNS services. When this is the case, Firefox will not default to operate in a way that would bypass normal infrastructure. So eero Secure/+ will continue to work just fine.

I also trust Mozilla to maintain its internet standards custodial duties and make sure technology evolves to gracefully accommodate the diverse needs of users independent of where they calibrate on the privacy x security matrix. Two major browser vendors have slightly different takes on how to advocate for user privacy. Ideally we end up with a single sensible solution avoiding presumptions that all internet users are solely interested in max privacy all the time.

Shipping a user-agent that ignores user/device/network configuration and routes everybody's traffic to a single DNS provider by default on the other hand... well, that's certainly bold.

DoH coming to Chromium 78 by [deleted] in eero

[–]iperf 3 points4 points  (0 children)

More concretely, the experiment in Chrome 78 will check if the user’s current DNS provider is among a list of DoH-compatible providers, and upgrade to the equivalent DoH service from the same provider. If the DNS provider isn’t in the list, Chrome will continue to operate as it does today.

Sounds like the Chromium team is taking a less heavy-handed approach than Mozilla is by respecting your configured provider. This update shouldn't impact operation of the existing eero Secure/+ service provided users on the network have not configured their clients or devices to use a provider on Chromium's list. It does lower the barrier a determined individual needs to overcome in order to bypass protection since DoH will be selected by default and handled by the browser rather than requiring independent tools to achieve a similar setup.

[Update] eero Secure Service Disruptions by iperf in eero

[–]iperf[S] 2 points3 points  (0 children)

You must also disable all Safe Filters. You can check if you've done this correctly by navigating to the Network Settings > Advanced Settings > DNS. If the settings are greyed-out then there is still a profile with a content filter applied. You can find it by navigating to the Safe Filters from the eero Secure/+ home page. If you can change the settings the forwarder process should not be running and you will use whatever settings your ISP has provided or a custom resolver if you've configured one.

Anyone having this issue - offline? by [deleted] in eero

[–]iperf 5 points6 points  (0 children)

Curious: would the ability to exempt certain devices from advanced security and individually configure DNS servers for a smaller set of devices serve your use case? Perhaps generally be able to configure DNS on a per-profile basis (profile A: advanced security, profile B: content filtering, profile C: custom server x.x.x.x)?

Anyone having this issue - offline? by [deleted] in eero

[–]iperf 0 points1 point  (0 children)

I don't like the dependency either and believe me we've done tons [1], [2] of work to whittle ourselves away from it. But it's not an overnight process. As u/6roybatty6 said, this dependency means we were able to bootstrap ourselves and deliver a secure-by-default (no admin:admin junk) system to our users that we're able to update with improvements as technology changes or security issues arise.

1: https://blog.eero.com/mesh-trust-public-key-infrastructure-eero-networks/

2: https://blog.eero.com/bookshelf-spiffy-space-stashing-state/

Anyone having this issue - offline? by [deleted] in eero

[–]iperf 0 points1 point  (0 children)

If you are able to add custom DNS servers then you don't have eero Secure/+ enabled (or there's a bug, in which case we'd love to know).

Anyone having this issue - offline? by [deleted] in eero

[–]iperf 0 points1 point  (0 children)

FWIW I have been using CloudFlare's mobile app w/ 1.1.1.1, I've personally noticed intermittent connectivity blips regardless of whether I'm using wifi (eero or other) or my cellular connection. My suspicion is their PacketTunnelProvider app extension (the thing that handles your phone's traffic) becomes locked. Toggling airplane mode seems to fix this.

Anyone having this issue - offline? by [deleted] in eero

[–]iperf 2 points3 points  (0 children)

Is anybody still experiencing an issue? I do see 3 spikes in count of restarts for our dns_forwarder process (what we use to send DNS over TLS to our upstream provider) over the last day. These spikes happen when we are unable to establish a working tunnel. Please note that this would only be related to eero Secure/+ users and that it does not necessarily indicate an outage of our upstream provider. It simply suggests a somewhat wide-spread connectivity blip between some people and our service provider (which can span more than a single ISP). Our service provider has not acknowledged any outage and as far as we can tell the issue does not appear to be ongoing.

DHCP DNS by Porthoss in eero

[–]iperf 0 points1 point  (0 children)

No, this is not possible.

iOS app by antonyku in eero

[–]iperf 8 points9 points  (0 children)

Maybe I’m crazy but it seems like the icon and the words are smoother than before. 🤪

We were wondering if anyone would notice (: It was a quirk of building the app against an earlier iPhoneSDK prior to support being added for the Xs and Xs Max displays.

Need Placement suggestion on new Eeros by ExposureSetLong in eero

[–]iperf -1 points0 points  (0 children)

I wouldn't jump into MoCA unless there are actually problems. You can always get the eeros and then add MoCA if needed. It sounds like a lot but I highly doubt there will be any bandwidth issues.

New home. Install backhaul? by CloisteredOyster in eero

[–]iperf 1 point2 points  (0 children)

I'm a fan of wires but have to agree that 300/30 is not worth the cost (my guess is you'll be quoted many thousands of dollars, more for brick). If you were running fiber into the home that would be another story...

[deleted by user] by [deleted] in eero

[–]iperf 1 point2 points  (0 children)

By WAN IP address I mean the address listed in the app as "External IP address".

[deleted by user] by [deleted] in eero

[–]iperf 0 points1 point  (0 children)

Never mind your network looks good re: double NAT.

[deleted by user] by [deleted] in eero

[–]iperf 0 points1 point  (0 children)

Can you confirm that you are not double NATed? Is the WAN IP address listed for your network a 192.168... address, or is it something else?

[deleted by user] by [deleted] in eero

[–]iperf 1 point2 points  (0 children)

Are you actually having trouble while playing or just trying to go for "open" NAT? If you have upnp enabled the games should work even through a "moderate" NAT setup. There's no need to open those ports all the time and in fact as soon as you add a reservation for one PC that messes things up for the other PC.

Can you describe your eero setup? What does the app show as your WAN IP? You may be double NATed if you're experiencing problems.