I know this is an outrageously bad idea, I don’t need convincing. I am just looking for some more information and discussion on what exactly the exposure and surveillance risk is.

I’m asking both for my own education (I am still very green to networking), and to better explain to people in my life if and why they should care.

  1. Is it true that traffic can be tracked and logged by ISP through DNS lookups, as these routers are preconfigured to use their internal dns service?

  2. If this is changed (like base.dns.mullvad.net), how much does this actually mitigate the risk here?

  3. What about when a VPN (mullvad) is also being used at all times? Would it then be “overly paranoid” to fear this untrusted box all the traffic goes through?

I personally take a conservative approach to things like this and assume it’s an unacceptable risk, but I don’t really understand what the truth is.

Thank you in advance for your time and thoughts.

EDIT: I’m asking about US and US adjacent areas

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 days ago
    1. Yes, kinda. So if you use the default DNS servers on your ISP provided modem than the DNS requests are likely forwarded to a sever controlled by the ISP. Now, something to keep in mind they can see you do a lookup of DuckDuckGo.com but they can not see what you are searching. HTTPS protects you there

    2. A little, by default a DNS request is performed in clear text, so some ISP may intercept those requests and redirect them to servers they control. Yes there have been reports of this with Verizon. Good news there are 2 technologies that you can use to protect yourself. They are DNS over TLS (DoT) or DNS over HTTPS (DoH). Many applications support one of those technologies to secure your DNS traffic.

    3. Using a host based VPN may protect you from ISP DNS snooping. Depends on how you configured it.

  • Treczoks@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 days ago

    Even if you set your own preferred DNS server, the router can simply spoof it, and route the DNS request to their own servers. But for that, you can use SSL for DNS.

    In general, the ISP could basically read everything you route through them that has not been encrypted. And even then, they know how much to talked with which web site.

    • Negligent_Embassy@links.hackliberty.orgOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      2 days ago

      I see.

      Just to make sure I understand, how does the situation change if the DNS resolver is set at the browser or OS level (DNS over HTTPS)

      Thank you for your response.

      • Treczoks@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        2 days ago

        Then the ISP can only see that you are contacting certain machines (and from there guess you want to avoid their DNS server). But apart from blocking that service, they can’t really do anything.

  • Maple Engineer@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 days ago

    I always put a firewall that I own inside the ISP router. Right now I’m using an old ASA 5505 but I’m considering upgrading to a Firewalla Gold. I slay segment my network so that it phones and notebooks are on one network and the TV and Xbox and other things that I have no control over on another.

      • Maple Engineer@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        3 days ago

        I’m on SpaceX. I have their latest terminal.

        I used to be in Bell Canada and before that a local ISP. I’ve always had a firewall inside the ISP router because I work in information security and don’t want anyone inside my network. My high network can reach my low network but my low network can’t reach my high network.

  • OneCardboardBox@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    If you’re always using a VPN, that’s not necessarily a privacy threat on your VPN’d device, but any other device on the network that doesn’t have a VPN could be exposing itself to the ISP.

    Also, you’re at the mercy of whatever firmware updates your ISP issues for the router. Hopefully they remember to support your box when the next CVE is discovered…

    We are forced to keep an ISP router/gateway combo in our home because it has certificates necessary to authenticate our subscription. However, behind that router we have the “real” router with settings and firmware updates that we control. The ISP router is just a hop between our router and the outside world. Everything on our network only connects to the router we control.