Upstream proxy not working properly

[hadi57]

hi

my isp request me so my browser point to their proxy, so i tried 2 soulutions an none works.

1- in proxy server: upstream proxy settings,  a) i tic the box to forward requests to an upstream server.
b) put the proxy ip givin to me by my isp. c) put the port 8080. d) use the port 7 to connect to upstream proxy. e) put the username and password i use for my dsl router to access the internet, f) put the password.

so what is happening now is, when my client pass the captive portal page, a user name and password
box apears and wont go unless he/she put the username and password, the one i use for my dsl router. then the internet works fine.

2- if i cancel soutution 1- and point the browser of an xclient pc to use the proxy ip givin by my isp the captive portal page wont apear.

how to deal with this situation

appreciating your help

hadi57

[dvserg]

squid?
I add manually to squid.conf - this worked with parent squid or usergate proxy
'cache_peer 192.168.2.29 parent 8080 7 no-query'

[hadi57]

hi

can you tell me where i can find squid.conf please

thanks

[Guest]

find / -iname squid.conf

It should be in /usr/local/etc/ but the find command is extremely useful and is always your friend.

[hadi57]

hi

the find command was useful, thanks a lot.

[hadi57]

hi again

this is what i see in the log - authentication report if i use upstream proxy and it keeps going all day
Jun 4 14:37:56 squid[4963]: Squid Parent: child process 4965 started
Jun 4 14:37:43 squid[4900]: Squid Parent: child process 4902 exited due to signal 9
Jun 4 14:37:40 squid[4900]: Squid Parent: child process 4902 started
Jun 4 14:36:54 logportalauth[383]: CONCURRENT LOGIN - TERMINATING OLD SESSION: saadam, 00:15:00:4e:81:46, 192.163.1.244
Jun 4 14:36:54 logportalauth[383]: LOGIN: saadam, 08:00:46:2b:0d:fb, 192.163.1.200
Jun 4 14:35:24 squid[4100]: Squid Parent: child process 4422 started
Jun 4 14:35:21 squid[4100]: Squid Parent: child process 4379 exited due to signal 6
Jun 4 14:35:09 squid[4100]: Squid Parent: child process 4379 started
Jun 4 14:35:06 squid[4100]: Squid Parent: child process 4350 exited due to signal 6
Jun 4 14:34:54 squid[4100]: Squid Parent: child process 4350 started
Jun 4 14:34:51 squid[4100]: Squid Parent: child process 4341 exited due to signal 6
Jun 4 14:34:38 squid[4100]: Squid Parent: child process 4341 started
Jun 4 14:34:35 squid[4100]: Squid Parent: child process 4252 exited due to signal 6
Jun 4 14:34:22 squid[4100]: Squid Parent: child process 4252 started
Jun 4 14:34:19 squid[4100]: Squid Parent: child process 4103 exited due to signal 6
Jun 4 14:34:10 squid[4100]: Squid Parent: child process 4103 started
Jun 4 14:33:56 squid[3657]: Exiting due to repeated, frequent failures
Jun 4 14:33:56 squid[3657]: Squid Parent: child process 4060 exited due to signal 6
Jun 4 14:33:54 squid[3657]: Squid Parent: child process 4060 started
Jun 4 14:33:51 squid[3657]: Squid Parent: child process 4050 exited due to signal 6
Jun 4 14:33:50 squid[3657]: Squid Parent: child process 4050 started
Jun 4 14:33:47 squid[3657]: Squid Parent: child process 4044 exited due to signal 6
Jun 4 14:33:41 squid[3657]: Squid Parent: child process 4044 started
Jun 4 14:33:38 squid[3657]: Squid Parent: child process 4039 exited due to signal 6
Jun 4 14:33:35 squid[3657]: Squid Parent: child process 4039 started
Jun 4 14:33:32 squid[3657]: Squid Parent: child process 3951 exited due to signal 6
Jun 4 14:33:24 squid[3657]: Squid Parent: child process 3951 started
Jun 4 14:33:21 squid[3657]: Squid Parent: child process 3931 exited due to signal 6
Jun 4 14:33:08 squid[3657]: Squid Parent: child process 3931 started
Jun 4 14:33:05 squid[3657]: Squid Parent: child process 3910 exited due to signal 6
Jun 4 14:32:53 squid[3657]: Squid Parent: child process 3910 started
Jun 4 14:32:50 squid[3657]: Squid Parent: child process 3905 exited due to signal 6
Jun 4 14:32:49 squid[3657]: Squid Parent: child process 3905 started
Jun 4 14:32:46 squid[3657]: Squid Parent: child process 3894 exited due to signal 6
Jun 4 14:32:38 squid[3657]: Squid Parent: child process 3894 started
Jun 4 14:32:35 squid[3657]: Squid Parent: child process 3876 exited due to signal 6
Jun 4 14:32:23 squid[3657]: Squid Parent: child process 3876 started
Jun 4 14:32:20 squid[3657]: Squid Parent: child process 3706 exited due to signal 6
Jun 4 14:32:16 squid[3657]: Squid Parent: child process 3706 started
Jun 4 14:32:13 squid[3657]: Squid Parent: child process 3659 exited due to signal 6
Jun 4 14:32:12 squid[3657]: Squid Parent: child process 3659 started
Jun 4 14:32:05 squid[3331]: Exiting due to repeated, frequent failures

help is really appreciated

hadi57

[hadi57]

hi,

i did edit the file manualy, and use:

'cache_peer 192.168.2.29 parent 8080 7 no-query'

i end up with internet explorer, cant see the captive portal page to authenicate, (most of my clients have it), but when trying firefox, i can see the captive portal page, what's wrong now?

thanks for the help

hadi57

[dvserg]

@hadi57:

hi,

i did edit the file manualy, and use:

'cache_peer 192.168.2.29 parent 8080 7 no-query'

i end up with internet explorer, cant see the captive portal page to authenicate, (most of my clients have it), but when trying firefox, i can see the captive portal page, what's wrong now?

thanks for the help

hadi57

You set you self data? Or copy my string '1:1'?
Must be (i set this config for my situation - and this woked for me)
cache_peer you.self.parent.proxy parent parentPROXYport 7 no-query

[hadi57]

hi

yes i set my isp proxy and the setup came as follows

cache_peer 212.93.193.87 parent 8080 7 no-query. still a box asking for the user name and password to access the requested site appears.

if it is possible that my clients can see and pass the captive portal page when they point to the isp's proxy in the their browser, this would solve my problem as well.

but putting the isp proxy in the upstream solution is preferable.

thanks for your support