Squid Questions and Issue With Connection Quality
-
I had Squid running for the first time yesterday, but I started having connection/quality issues after it ran successfully for a few hours.
At first, a VLAN interface started preventing outbound traffic somewhere along the way. Disabling this interface in Squid allowed traffic to resume. When connecting to the AP, devices showed "limited connectivity" and "connected but no internet" messages. I left the VLAN1 deselected in Squid setup but left LAN enabled.
Later that night, I noticed that some of my devices were taking a long time to communicate on the LAN interface, or not at all. For example, my Nest speakers started saying there was a problem and they would not perform actions. When trying to control some Home Assistant lights. I started hav
-
PFBlocker is enabled but on VLAN1 I have used a manual DNS server so that people in the household have an isolated, but less restrictive experience. I keep my tinkering and home network hardware devices on the LAN. Does a manual DNS entry cause issues with Squid's proxy? I am curious why the VLAN would be affected differently but the LAN did not give the same messages? Everyone had to switch to the LAN temporarily to connect to the internet.
-
Not sure this would cause an issue, but I was testing ntopng for a few weeks previously but it did not do everything I wanted. I also had installed bandwidthd. Once squid was up and running, I realized I had what I needed and uninstalled the other two packages. I'd like to say that this is when the issue started but unfortunately I cannot. Do some of these packages interfere in any way?
-
I have the squid package set up with the defaults listed in netgate's docs. I only add a cert so that ssl splicing could occur. The CPU/RAM never seemed to go above 20% when watching.
Trying to learn as much as I can as part-time hobbyist and any help is appreciated. I know much of this is probably very generic compared to what you all are used to working with.
-