What is a free Linux gateway with the function of viewing the URL of client requests?

Question

linux

You need a version of a Linux server with a web interface that can route Internet traffic through itself, with the following features:
* convenient monitoring of statistics on the use of network resources, you need to display a list of local machines with details on selected days, which sites were visited (preferably not just a domain name, namely the requested URL), which ports the traffic went to, the general statistics of a single local computer over a period of time
* preferably something like QoS, so that, if desired, it would be possible for individual computers to set their priority in the bandwidth of the gateway
* you need to be able to use the web interface block the local machine from receiving traffic until I allow it again
I saw something similar in my life in the Usergate program, but this is a very expensive product, and you need to install it in a budget organization (school), where the task is to identify "gluttonous" offices. So far, I have implemented the analytics in the dumbest way, I just connect via VNC to the computer, log in to the user account and look at the browser history, but I understand that the user, if he has a convolution, can clear the browser of any "uncomfortable" records. Therefore, registration of traffic up to the level of URL addresses is needed on the gateway itself.
Oh, and one more thing, now while I raised the gateway to IPFire, installed NtopNG on it, it seems to be not bad, but I don’t have enough of its capabilities, again, there is no option to see URL requests, I can’t figure out how to see statistics on the local computer for a certain period. So far, my example of the highest form of analytics is Usergate, but I'm sure there are free products out there that can reach it.

Answer 1

You need a Linux server version with a web interface

Horses mixed up in a bunch, people ...
Apparently, you need a proxy. True, there is no QoS in the proxy. And the ability to view urls in it will be limited - due to the ubiquitous implementation of https, which is just being implemented in order to resist such things. That is, you need a proxy with bumping. And there are no statistics in the proxy - it just gives it to the log, and the log can already be parsed on its own, as you like. But if you can turn on ELK for statistics (which is quite natural if you know how to cook it), then without bumping you will see frank bullshit in the log :)
Well, that is - the user went to https://mail.ru- Well, like to read the mail. Established an https connection with it. And then, being on this site, he switched to love.mail.ru - and now he is already sitting and "building his love"! And this will not be reflected in the log, because https.
Here's what you need to think about first. And bumping is your own certificates installed on clients. Nothing will work without this feature.

Answer 2

Any proxy + sending its logs to ELK. In kibana, you can build whatever reports you want - at least by IPs, at least by urls with domains.

Answer 3

Squid+SAMS2

Answer 4

Up to 40 users Ideco UTM is free. And so pfsense.

Answer 5

kerio read there were interesting solutions, + there you can do certificates for local wheelbarrows, but monitor all traffic