trafficserver VS Squid

in this code repository: https://github.com/apache/trafficserver

The LARGE majority of CDNs use either Apache Traffic Server (https://trafficserver.apache.org/) or Nginx for their cache webserver, so the mechanisms used are pretty easy to find if you look through the docs.

Apache Traffic Server (no relation to Apache itself) would be an excellent option: https://trafficserver.apache.org/

Although haproxy and nginx cover (for me) almost all use-cases I had to deal with (with OpenResty [1] as a backup), I see one place where ATS could shine: plugins. From examples [2], C API looks sane and well documented, and this is very important if you want to add some custom stuff inside your proxy server without losing your hair. And no, lua isn't the solution here ;)

Those who had to deal with nginx plugins, I feel your pain...

[1] https://openresty.org/en/

[2] https://github.com/apache/trafficserver/tree/master/example/...

> But I’m working on setting up a VPN at my house to tunnel all Netflix traffic through ...

On a technical point, you might be able to get away with just using Squid for the proxy, with pretty much default settings.

http://www.squid-cache.org

I used to use that years ago (not with Netflix though) running from a data centre, using an ssh (autossh) tunnel to reach it securely.

Worked pretty well, aside from the extra latency due to the packets having to go an extra half way around the world. ;)

I recommend trying a transparent proxy like Squid. There are many analytics tools for Squid logs. Squid can generate TLS certificates on the fly to inspect secure websites but you'll have to generate and install a CA certificate and key into Squid. You'll also have to import the CA certificate on any machine accessing the internet through the Squid proxy. Squid has the added bonus of caching content to speed up web browsing and reduce data usage.

I “invented” IPFS when I though “wouldn’t it be nice if we could combine Squid-Cache with BackupPC

A couple of dedicated server-side resource caching solutions have emerged over the years: Memcached, Varnish, Squid, etc. Other solutions are less focused on web resource caching and more generic, e.g., Redis or Hazelcast.

Web caching (more techical, probably not useful) there squid-cache

Also, the fact it is distributed by HTTP allow companies (and ISPs) to cache content in Squid servers (http://www.squid-cache.org/). And this is quite a feature!

If your router is compatible with custom firmware (Tomato or DD-WRT) you can flash it and use the logging features of those platforms. Otherwise no there isn't really an "app or software" that can do this, you need a piece of hardware that sits between the LAN devices and the internet connection. That can be a full-fledged computer, if you're willing to use it as firewall or router (pfSense), DNS server (PowerDNS) or proxy server (Squid).