Welcome, Guest. Please login or register.
Did you miss your activation email?
Saturday 09 November 2024, 12:45:22 pm

Login with username, password and session length

The Latest Endian Firewall is now available for download HERE
14250 Posts in 4377 Topics by 6515 Members
Latest Member: hulteends
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  EFW SMTP, HTTP, SIP, FTP Proxy Support
| | |-+  Automatically Detect Settings and proxy.pac not working
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Automatically Detect Settings and proxy.pac not working  (Read 22180 times)
cschuler
Jr. Member
*
Offline Offline

Posts: 2


« on: Tuesday 13 March 2012, 05:08:57 am »

I'm trying to setup Endian 2.5.1 proxy to work with automatically detect settings but can't get it to work.   Here is my setup.  

Endian is doing DHCP and my clients are getting addresses on green.  
Endian Firewall is not allowing port 80 traffic on green.
Proxy is turn on not transparent on green.

If I have automatically detect settings enabled in IE or Firefox I get nothing.  if I manually enter the proxy everything works and I can get .  

After looking around for a while I found in /var/log/httpd/error_log

Use of Uninitialized value in substitution (s///) at /home/httpd/html/proxy.pac line 160
Use of Uninitialized value in substitution (s///) at /home/httpd/html/proxy.pac line 163

those lines are
$config{'dst'} =~ s/&/\|/g;
$config{'useragents'} =~ s/&/\|/g;

I found a bug tracker at bugs.endian.com/view.php?id=2845#bugnotes that talks about this same issue (different line numbers but the same code) but this is from 2 years ago and version 2.3 but there is no answer on it.  

Any ideas how I can get auto detect proxy settings to work?  

Thanks

Curt
Logged
mangthjik
Full Member
***
Offline Offline

Posts: 21


« Reply #1 on: Tuesday 13 March 2012, 06:20:13 pm »

had you check the rule at firewall section ? 
source : green- blue
destination : red
allow : http
Logged
cschuler
Jr. Member
*
Offline Offline

Posts: 2


« Reply #2 on: Tuesday 13 March 2012, 10:07:52 pm »

Yes I have checked that.  Actually in my first post I said that I am not allowing port 80 on green.  This is because with a NON transparent proxy if you allow 80 on green/blue and the auto detect doesn't work the client gets on the internet without going through the proxy.  Basically it takes a long time for the auto detect to not work but then it just loads without trying to use a proxy. 

However my setup works just find if I manually put in the proxy settings.  It just doesn't get the proxy setting automatically with the auto detect settings.
Logged
msource
Jr. Member
*
Offline Offline

Posts: 5


« Reply #3 on: Monday 26 March 2012, 10:32:11 pm »

Hi, i had the same problems here. And for example, the Content Filter does not work with proxy.pac auto detect.

Could someone put proxy.pac to work?

Marcos Fernandes
Logged
nokia001
Jr. Member
*
Offline Offline

Posts: 7


« Reply #4 on: Friday 30 March 2012, 06:56:29 am »

Hi,

same problem here. Anything new?

Gerd
Logged
nokia001
Jr. Member
*
Offline Offline

Posts: 7


« Reply #5 on: Saturday 31 March 2012, 03:27:58 am »

Hi,

new install, restart efw befor proxy setup solved the problem for me.

gerd
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.063 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com