Hey IP-Fire Community, I had some problems with my Proxy but thanks to the very good documentation on the IP-Fire i had it under control. After the Upgrade to 183/184 i had some Proxy/squid Problems. Under command in shell Squid -k parse there seems all fine. But no sites will open after a while…

Hello to all! Thanks for the help! I found the Problem and figured it out. The Problem was the Asix Ethernet Chip, that makes the Problem with the Proxy. I switched from Asix to Intel Ethernet Chip. The Cache-Manager wouldnt help because it only cache unencrypted data. But most of the Internet i…

TBH, I am not sure as it is years ago that I ran into the problem. For a start, just monitor a single PC’s source IP and then narrow it down: tcpdump -nni green0 host 111.222.333.444 My grey cells seem to also remember the proxy log was helpful and contained a lot of escaped characters. AFAIK, if…

I’m not really interested in the cache part so much as the URL filter, so I set both cache sizes to 0 and the min and max object size to 0. Is there a better way to run a proxy without a cache for the URL Filter? I’m curious to see if zero cache means that Squid won’t crash again. Is it possible …

When @nickh wrote that maybe the internal SSD is not fast enough to save the cache on the Disk, my thoughts were the same to put the Disk Cache to Zero. Im testing some Scenario. This will be one of them. Maybe it will work better. And when it is really possible to work like this, then maybe it is …

When I was using squid, it was with v3.5.20. Not having a fast-enough SSD just slowed the internet connection. It did not cause any crashing of squid itself. I am trying to remember my tcpdump diagnosis. I seem to remember I was trying to see if there was a traffic storm so the tcpdump query was no…

Since setting the cache to zero, my memory usage has stayed flat at around 50 mb and I’ve seen no spikes. URL filtering still seems to be working, so it’s probably a cache issue that, like others mentioned, started with CU 183.

[image] Sergio: The Problem was the Asix Ethernet Chip, that makes the Problem with the Proxy. I switched from Asix to Intel Ethernet Chip. Hi @sergio There has been a problem in the kernel driver for the asix based chips since CU185. https://community.ipfire.org/t/cu-186-testing-ax88179-us…

[image] Adolf Belka: There has been a problem in the kernel driver for the asix based chips since CU185. The mentioned bug was introduced in core186 so it has only affected the testing-tree systems. It also has nothing to do with squid. Early core186 installations doesn’t got a ethernet link …

Sorry @arne_f you are correct, my mention that it came in on CU185 is incorrect. My apologies for my error. Everyone please ignore my comments re the ASIX. I replied, getting triggered by the ASIX mention and obviously not reading closely enough.

@arne_f I have this Version Edimax EU-4306 .

Hmmm… I also have an ASIX AX88179 powering my RED network. It is also crashing even with a purely RAM cache. I’m not sure how the ethernet driver could cause Squid to crash,. but is it confirmed this is the cause? Is CU186 expected to fix this issue? Do I need to go ahead and replace my adapter?…

IPFire Community

Proxy crash / Squid issue

Network Web Proxy, URL Filter & Update Accelerator

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled