Messages

1

18.7 Legacy Series / Re: 18.7 web and ftp proxy not working

« on: August 01, 2018, 02:13:38 pm »

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

18.7 Legacy Series / Re: 18.7 console login doesn´t work if password includes #-sign

« on: August 01, 2018, 02:11:52 pm »

Yes ssh and gui login work but not local console...

Thanks for the keymap hint. Looks like that´s the problem.

3

18.7 Legacy Series / 18.7 console login doesn´t work if password includes #-sign

« on: August 01, 2018, 11:04:36 am »

If you use a # sign in Password, you can´t Login to console.

4

18.7 Legacy Series / Re: 18.7 web and ftp proxy not working

« on: August 01, 2018, 10:43:03 am »

sorry...

Can 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

18.7 Legacy Series / Re: 18.7 web and ftp proxy not working

« on: August 01, 2018, 10:34:32 am »

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

18.7 Legacy Series / Re: 18.7 web and ftp proxy not working

« on: August 01, 2018, 10:05:23 am »

yes - unfortunately it doesn´t help

7

18.7 Legacy Series / 18.7 web and ftp proxy not working

« on: August 01, 2018, 09:38:39 am »

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

« on: 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