browolf Posted February 25, 2014 Posted February 25, 2014 (edited) I surmised we can enable lightspeed quite simply with our own proxies by disabling chaining or something similar. On the main staff proxy merely changing "never_direct allow all" to "always_direct allow all" works! (debian 7.2 with squid 2.7 stable 9) On the guest wireless, doing the above causes the error "connection refused". (debian 5.09 with squid 2.6 stable 5) - no idea why On the pupil isa 2006 server. adding an always direct rule or changing the last-default-rule to direct causes the error "•Error Code 10061: Connection refused " - no idea why anyone else had/solved proxy issues with lightspeed? Edited February 25, 2014 by browolf
Arcath Posted February 25, 2014 Posted February 25, 2014 Are your guest wireless/pupil network are on the range given to you by OCL? I read somewhere that if its not (e.g. you route a 192.168.x.x) that it wont work, probably because the lightspeed device wont have the correct routing for you. If that is the case then it would seem to me that you would need to continue proxy-ing request but onto a direct connection instead to an upstream server.
browolf Posted February 26, 2014 Author Posted February 26, 2014 (edited) Are your guest wireless/pupil network are on the range given to you by OCL? I read somewhere that if its not (e.g. you route a 192.168.x.x) that it wont work, probably because the lightspeed device wont have the correct routing for you. If that is the case then it would seem to me that you would need to continue proxy-ing request but onto a direct connection instead to an upstream server. yes we have our own internal ip ranges so will need to continue using our proxies. the problem I'm having is getting "proxy-ing request but onto a direct connection" to work. edit: seems guest wireless is squid v2.7stable3; not as previously reported. Edited February 26, 2014 by browolf
Arcath Posted February 26, 2014 Posted February 26, 2014 We run a fake version of "proxy.lancsngfl.ac.uk" in our office that proxies requests to direct, I will look at the config on that when Im back there this afternoon.
browolf Posted February 26, 2014 Author Posted February 26, 2014 it occurs to me after reading the other thread that lightspeed might not be enabled on our curriculum connections. Seeking clarification at the moment.
ChrisH Posted February 26, 2014 Posted February 26, 2014 Should only be on the admin, the details of your date should be on the portal.
browolf Posted February 26, 2014 Author Posted February 26, 2014 You must be in the first phase then. yes we are
maxrebo Posted March 10, 2014 Posted March 10, 2014 anyone got local proxy (ISa server) working with lightspeed?? - currently trying to change settings - I presume its the web chaning part that we have to remove? (or change?) anyone got advice on what to change?
LukeC Posted March 10, 2014 Posted March 10, 2014 Lightspeed is working with our ISA 2006 box, I changed the last default rule in the network config to retrieve the requests directly from specified destination.
maxrebo Posted March 10, 2014 Posted March 10, 2014 thanks for the reply, just to confirm - that's in "web chaning" \ default rule \ Action \ process requests by " retrieving them directly from the specified destination"
browolf Posted March 11, 2014 Author Posted March 11, 2014 configuration, networks, web chaining, create a new rule called always_direct action - retrieving them directly from specified destination to - external 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now