Thanks a lot guys, I ended up going back to using FileZilla with my LAN Squid
as HTTP proxy and allowing CONNECT requests to unregistered port only for a
list of known FTP/SFTP destinations; probably not ideal from a security
standpoint but it's the easiest way to manage my users requests.
Thanks
Hi,
> I'm sorry Jascha but the suggestions you got in your thead went kind of over
> my head, can I ask you if and how you "do allow the front-end Squid to
> re-FTP the traffic to the appropriate server then intercept it independently
> into the backend with its own ftp_port accepting the "native
On 28/02/18 23:58, Grey wrote:
> Thanks for the replies guys!
> I'm sorry Jascha but the suggestions you got in your thead went kind of over
> my head, can I ask you if and how you "do allow the front-end Squid to
> re-FTP the traffic to the appropriate server then intercept it independently
> into
Thanks for the replies guys!
I'm sorry Jascha but the suggestions you got in your thead went kind of over
my head, can I ask you if and how you "do allow the front-end Squid to
re-FTP the traffic to the appropriate server then intercept it independently
into the backend with its own ftp_port accept
On 28/02/18 21:30, Grey wrote:
>
> At this point, I'd like to know if what I'm trying to do is possible at all,
> beacuse I'm starting to think there's something major I've totally
> overlooked.
The most obvious thing is that the port 3128 is an *HTTP* port, so when
the Browser is using that por
Hi,
> I'm setting up a new infrastructure for my web proxy and I'm having a
> problem with FTP access to the internet; I'm running Squid 3.5 on Debian 9
> machines by the way.
>
> I used to have a single Squid machine talking freely to the internet from
> inside the LAN, with clients connecting on
