Hello
i try to use squid (6.10) with opnsense 24.x on freebsd 13-2-Release-p11.
It produces a "segmentation fault" at start and restart but the process
runs.
The "segmentation fault" occurs even with squid -k parse.
A "service squid reload" runs OK, but a "service squid restart" produces
On Mon, Jul 22, 2024 at 12:12 PM Anton Kornexl
wrote:
> Hello
>
> i try to use squid (6.10) with opnsense 24.x on freebsd 13-2-Release-p11.
>
> It produces a "segmentation fault" at start and restart but the process
> runs.
>
> The "segmentation fault" occurs even with squid -k parse.
>
> A "s
Hello, Jonathan,
> curl http://localhost:3128/squid-internal-mgr/info
> Where would I place the password?
I use the following configuration:
http_access allow localhost manager
cachemgr_passwd redacted config
The command to read the current running config is:
curl localhost:3128/squid-internal
Hello,
I have tested the two installations further
Opnsense 23.x with squid 6.6 on freebsd 13.2-Release-p9 produces the
same segmentation fault, but it does not popup as red window in the
dashboard.
I have set "debug_options ALL,5" in squid.conf:
I have found the following lines in cache.lo
Thanks for the info
I tried it and this also failed. Dang
Shell Output - curl localhost:3128/squid-internal-mgr/info -u :redacted
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0
Also I have tested
curl 127.0.0.1:3128/squid-internal-mgr -u :redacted
curl localhost:3128/squid-internal-mgr -u :redacted
curl hostname_here:3128/squid-internal-mgr -u :redacted (per bug notes use
hostname in place of localhost)
and testing with no password same commands lock up the system wit
Can you try supplying a username to curl? It's also common practice to
put flags ('-u user:redacted') before arguments (the URL)
On Mon, Jul 22, 2024 at 5:12 PM Jonathan Lee wrote:
>
> Thanks for the info
>
> I tried it and this also failed. Dang
>
> Shell Output - curl localhost:3128/squid-inter
That would require a username for the cachemgr_password account right? I have
no usernames set up for this.
How does one add a username for this directive ?
> On Jul 22, 2024, at 11:13, Francesco Chemolli wrote:
>
> Can you try supplying a username to curl? It's also common practice to
> put f
Not really, no. Username is not considered, it's just to make sure
that curl sends all the data
On Mon, Jul 22, 2024 at 7:21 PM Jonathan Lee wrote:
>
> That would require a username for the cachemgr_password account right? I have
> no usernames set up for this.
>
> How does one add a username fo
Ok thanks let me boot that environment and test again, my concern is that is
looks like it is attempting it from my WAN side address that is my wan address
and not the loopback
> On Jul 22, 2024, at 11:22, Francesco Chemolli wrote:
>
> Not really, no. Username is not considered, it's just to
Tested thanks for the reply and idea access denied and tested with a firewall
rule to approve everything to port 80 same result with or without mgr_passord
configured, it is like the page is missing in Squid 6.6 or something
Shell Output - curl localhost:3128/squid-internal-mgr/info -u admin:re
On 20/07/24 03:19, Alex Rousskov wrote:
On 2024-07-19 09:20, Rafał Stanilewicz wrote:
Thank you. It worked.
Glad to hear that!
Seconded.
I incorrectly assumed all dependencies would be captured by aptitude
build-dep squid and ./configure.
AFAIK that is a correct assumption for Debia
12 matches
Mail list logo
