|
Title: Problem with http proxy configuration Post by: sunnet on Thursday 01 April 2010, 04:17:59 am I have an Endian Firewall 2.2 which works very well. I would like to upgrade to version 2.3 and am trying to configure it but when I open the browser, it not asks me for logon credentials. I created groups and users, but nothing, it open directly the page that shows me that the site is blocked. Where can I find informafioni for such a configuration, or is there someone who can help me?
Title: Re: Problem with http proxy configuration Post by: whoiam55 on Thursday 01 April 2010, 05:55:47 am If it say that site is blocked implies that you have selected a category in the content filter profile which clocking the site you want to open. Try selecting a few category to rule out the problematic one ;)
cheers! Title: Re: Problem with http proxy configuration Post by: sunnet on Thursday 01 April 2010, 07:01:32 pm Thank you, but my primary problem is that the EFW not asks me the logon for the browser.
Title: Re: Problem with http proxy configuration Post by: whoiam55 on Thursday 01 April 2010, 09:07:16 pm You need to enable authentication but you can't use transparent mode.
Title: Re: Problem with http proxy configuration Post by: gyp_the_cat on Thursday 01 April 2010, 09:08:22 pm Hi Sunnet,
If I understand correctly, try: Proxy - HTTP - Configuration - Authencation Required (http://gypthecat.com/images/hotlink/efwsupport.org/endian_http_authentication_01.png) It sounds like it could be on disabled at the moment allowing all traffic through. Gyp Title: Re: Problem with http proxy configuration Post by: koukobin on Friday 02 April 2010, 02:33:47 pm I had the same problem once in a new endian installation.
I had a message that i am not authenticated but i was using transparent proxy that does not need authentication. I realized that the problem was with the havp service (check the log files for havp). Specifically, havp couldn't find the files whitelist and blacklist in the folder /etc/havp . For a strange reason these files were not there (the links for these file because the original files are located in the folder /var/efw/havp). Havp cannot work without them even if they are empty. The service needs them to start (see the conf file of havp) I created them manually (touch /etc/havp/whitelist) and set the owner as nobody (chown nobody:nobody /etc/havp/whitelist) and then i restarted the havp service (/etc/init.d/havp restart). Finally i restarted the squid and the problem was solved. I hope this will help. |