Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - me

#1
I´ve checked the console while booting.  It hangs some minutes trying starting squid.
there are no errors but squid doesn´t start automatically...

I´ve changed my root password and removed the # sign.
Now squid starts normally... very strange..

I don´t think that changing the password has fixed the problem - maybe the problem occurs just randomly
#2
Yes ssh and gui login work but not local console...

Thanks for the keymap hint. Looks like that´s the problem.
#3
If you use a # sign in Password, you can´t Login to console.
#4
sorry...

QuoteCan you stop squid via Dashboard (or it's already stopped) and check for open port 3128 via Firewall : Diagnostics : Sockets

After rebooting opnsense I can´t stop squid via Dashboard because it´s already stopped
Port 3128 is open

If I change the listening interface to WAN and than back to LAN squids starts normally.
After rebooting opnsense I´ve the same problem again.

#5
I´ve restored an older Version from backup and get the same error now.

If I set the listening interface to another one and then back to LAN squid starts without Problems.

I really don´t know what´s going on there...
#6
yes - unfortunately it doesn´t help
#7
After updating to 18.7 web and ftp proxy don´t start.

squid log:
could not bind port 3128 address already in use
could not bind port 2121 address already in use

How can we fix it?
#8
17.1 Legacy Series / Wrong subnetmask in squid.conf
April 28, 2017, 11:39:02 AM
Hi,

i have configured an alias ip on LAN Interface.
The Problem is that now there is a wrong subnetmask in squid.conf.

It looks like this:
acl localnet src 192.168.20.5/192.168.20.5 but it should be 192.168.20.5/24.

opnsense 17.1.5

regards