Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Google Drive Uploads

    Traffic Shaping
    4
    5
    2.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      HammyHavoc
      last edited by

      Hey everybody,

      I followed what was said on this particular thread: https://forum.pfsense.org/index.php?topic=52795.0

      This rule didn't seem to do anything, so then I tried resetting the states on pfSense, still no change. I then tried outright blocking Google Drive to see if the hosts were right, followed by another state reset, yet the traffic still goes through, leading me to believe that the hosts mentioned in that thread are no longer current.

      I don't want to block Google Drive, but merely want to shape it so that if someone starts streaming from my Plex server then the backups of PCs, laptops etc aren't going to kill the viewing experience.

      Well aware that I can set the Google Drive limits on each machine individually in the desktop client, but I'd rather shape dynamically so I can fully utilize the WAN when streaming isn't happening.

      Hopefully somebody can help.
      Hamual

      1 Reply Last reply Reply Quote 0
      • H
        Harvy66
        last edited by

        The hosts may be valid, but firewalls do not see hosts, they only see IP addresses. This is why we call it TCP/IP and not TCP/DNS.

        The IPs you firewall gets for a DNS record could be completely different than that of a client. A single DNS record can have an unbounded number of IP addresses registered with it, but per request, you only get back a subset of those IPs. Simply put.

        This is about my limit of practical knowledge on the subject. I'm sure someone else will be able actually help you, but at least you have an idea of what the probablem probably is.

        1 Reply Last reply Reply Quote 0
        • N
          Nullity
          last edited by

          It might be easier to prioritize Plex traffic.

          Please correct any obvious misinformation in my posts.
          -Not a professional; an arrogant ignoramous.

          1 Reply Last reply Reply Quote 0
          • N
            nightanole
            last edited by

            Not to hijack a thread, but upgrading to 2.3 ended up blocking gdrive from connecting.  Connected directly to the cable modem works great.  It wont connect at all behind pfsense, dropbox and onedrive are not affected.  Im running a very min setup for psfsense since im a beginner.  Its setup like a consumer router from one cable modem, and the only thing else im running is a CODELQ traffic shaper to cut down on buffer bloat.

            1 Reply Last reply Reply Quote 0
            • N
              Nullity
              last edited by

              @nightanole:

              Not to hijack a thread, but upgrading to 2.3 ended up blocking gdrive from connecting.  Connected directly to the cable modem works great.  It wont connect at all behind pfsense, dropbox and onedrive are not affected.  Im running a very min setup for psfsense since im a beginner.  Its setup like a consumer router from one cable modem, and the only thing else im running is a CODELQ traffic shaper to cut down on buffer bloat.

              Use tcpdump or logs to confirm that pfSense is blocking. Unless you have a specific rule blocking outgoing packets, the packets should be passed and NATted like anything else.

              Please correct any obvious misinformation in my posts.
              -Not a professional; an arrogant ignoramous.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.