Re: [squid-users] Problems connecting to ports !80

Hi,

        please do not top-post, it makes reading the thread much harder.

Daniel Ruiz wrote:
> Sorry. It continues without working. :-(
>
> On 11/05/06, Daniel Ruiz <daniel.ruiz.lopez@gmail.com> wrote:
>> I have disabled the firewall of fedora and I have stopped the service
>> iptables. I don't know whats avc.
>>
>> Thanks
>>
>> On 11/05/06, Mark Elsen <mark.elsen@gmail.com> wrote:
>> > > Hi,
>> > >
>> > > I have just installed squid 2.5 stable running over Fedora Core 5 and
>> > > I have made a minimmum configuration (I have allowed the IP addresses
>> > > of my Intranet).
>> > >
>> > > It works correctly. The problem is when I want to connect to another
>> > > port different to 80, for example the 2004 or 8080.
>> > >
>> > > I have added this line "acl Safe_ports port 2004" between the
>> > > Safe_ports but it continues without working.
>> > >
>> > > I don't know if the problem is caused by squid or by any firewall.
>> > >
>> > > The message error in the client is the following:
>> > >
>> > > ************************************
>> > >
>> > >
>> > > The following error was encountered:
>> > > Connection to Failed
>> > >
>> > > The system returned: (13) Permission denied
>> > >
>> > >
>> > > The remote host or network may be down. Please try the request
>> again.
>> > >
>> > > Your cache administrator is root.
>> > > ________________________________
>> > > Generated Thu, (squid/2.5.STABLE13)
>> > >
>> **********************************************************************************************
>>
>> > >
>> > > I have looked the /var/log/messages and I can find lines like this:
>> > >
>> > > *****
>> > > May 11 10:39:22 pc36 kernel: audit( 1147336762.851:321): avc: denied
>> > > { name_connect } for pid=10074 comm="squid" dest=2004
>> > > scontext=root:system_r:squid_t:s0
>> tcontext=system_u:object_r:port_t:s0
>> > > tclass=tcp_socket
>> > > ******
>> > >
>> > > Could you help me please?
>> > >
>> >
>> > What is 'avc' ?
>> >
>> > Seems that you are running a local firewall or have enabled Linux
>> > firewalling ?

OK, you appear to have SELinux enabled - you'll either need to disable
it (and reboot) or resolve the policy issue (I can't help on that one).

HTH,

                                Neil.

-- 
Neil Hillard                    hillardn@whl.co.uk
Westland Helicopters Ltd.       http://www.whl.co.uk/
Disclaimer: This message does not necessarily reflect the
            views of Westland Helicopters Ltd.